If you don't have NAs in your bits, you might be able to use the raw
vector type. A raw value is one byte (8 bits), doesn't support NAs and
supports bit operations on all the bits at once:
, |, !, xor
You'd probably want to wrap it into a class that allows a more
BitSet-like view of it
One way to deal with this is to install R itself with mpicc. Then all
packages are installed with mpicc and get the required MPI libraries and
includes by default. I have done this with R-2.13.0 on an Opteron
cluster running CentOS-5 a while ago and so far it has worked out great.
I crosspost
Hi!
I thought having a NAMESPACE file in an R package was enough to pass the
correct 'domain' argument to gettext(), but it can't get this to work
with a Rcommander plugin I'm developing[1]. Is that a know bug? Or is
this related to the fact that Rcmdr does some black magic when loading
plugins?
Thanks! This is a possible solution, but I would argue not a preferable
solution. I'd advocate a mechanism that provides transparent support for MPI,
analogous to the way that R 2.13.0 and upwards provides transparent support for
OpenMP. Expressing a personal opinion, I would stress the
If you don't have NAs in your bits, you might be able to use the raw
vector type. A raw value is one byte (8 bits), doesn't support NAs and
supports bit operations on all the bits at once:
, |, !, xor
You'd probably want to wrap it into a class that allows a more
BitSet-like view of it though.
Hi All,
Apologies if this is a very naive question. Is there a way to see the
particular Rd file being processed right before a warning/error
occurs? As far as I can tell, all my .Rd files use have names and
titles and they are unique between Rd files (sometimes in a file I use
something like
On 11-10-12 3:24 AM, Joshua Wiley wrote:
Hi All,
Apologies if this is a very naive question. Is there a way to see the
particular Rd file being processed right before a warning/error
occurs? As far as I can tell, all my .Rd files use have names and
titles and they are unique between Rd files
R CMD check is R code: you can run the R code for yourself using R's
debugging facilities. In this case start with 'R CMD Rd2pdf pkg-name'
(which should give the same error, as that is what R CMD check calls),
then run that R code directly (there are comments in the code in
R-devel about how
Using R 2.13.1, I am now getting the following NOTE when I run R CMD
check on my HistData
package
* checking for unstated dependencies in examples ... NOTE
'library' or 'require' calls not declared from:
gplots sp
Under R 2.12.x, I didn't get these notes.
I have ~ 25 .Rd files in this
Thanks to Drs. Murdoch and Ripley for your fast and helpful replies.
I did not realize that R CMD check was R code, so that was incredibly
useful.
I spent the morning working on debugging this, and I think I must have
messed up setting up the Windows tool chain, because I get the error
even when
Hi, Josh:
Have you had a recent version that passed R CMD check? If yes,
I suggest you save your recent changes then revert to that earlier
version and add your recent changes back in again one at a time. I've
done that many times. (It's also a major reason I make changes as small
Good luck in tracking down the problem. I won't give
any help there.
I've seen this sort of error message (or worse) when using
system.file() and the desired file didn't exist. If that
is the problem, add the newish argument mustWork=TRUE to
the call to system.file so you get an error message
These are small enough problems with R devel branch yesterday I thought I'll
just post here and hope somebody will fix them soon (or may have already been
fixed today), rather than filing at the bugzilla.
- R CMD check --use-valgrind --use-gct mypackage gives:
--
If you want to hide some code from accidental or casual sight then I have had
some success with adding something like this to the .R file for a package (the
petals function in TeachingDemos in this case):
.onAttach - function(...) {
petals - petals
attr(petals,'source') - Don't Cheat!
On 12/10/2011 3:57 PM, Greg Snow wrote:
If you want to hide some code from accidental or casual sight then I have had
some success with adding something like this to the .R file for a package (the
petals function in TeachingDemos in this case):
.onAttach- function(...) {
petals- petals
You have this in Jevons.Rd:
# show as balloonplots
if (require(gplots)) {
and this in Snow.Rd:
%\dontrun{
library(sp)
It will certainly be helpful if R CMD check can provide more
informative messages (in this case, e.g, point out the Rd files).
Regards,
Yihui
--
Yihui Xie
Hi Spencer,
Yes, I have versions that pass, but it is not package specific (i.e.,
I can download other package sources from CRAN and if I run R CMD
check on them, I get the same error). When I run R CMD check using R
2.13.1 or R 2.13.2 it is fine. Using either:
compiled from source:
R Under
17 matches
Mail list logo