search for: bitwhich

I have defined boolean methods for bit and bitwhich objects, for example |.bit <- function(e1,e2) and |.bitwhich <- function(e1,e2) Both methods coerce their arguments to the respective class, however if I do something like bit_obj | bitwhich_obj then I get a warning Warning message: Incompatible methods ("|.bit", "|.bitwh...

...e (?ffdf) - store 4-level factor like A,T,G,C with 2bit instead of 32bit (?vmode) - fast chunked iteration (?chunk) - run linear model on large dataset using biglm (?chunk.ffdf) - handle boolean selections by factor 32 faster and less RAM consuming (?bit) - handle very skewed selections very fast (?bitwhich) - parallel access to large dataset just by sending ff's small metadata from master to slaves (e.g. with snowfall) ff is hosted on r-forge now and you find some presentations on ff at http://ff.r-forge.r-project.org/ Hope you find this useful. We appreciate any feedback. Jens & Daniel...

...e (?ffdf) - store 4-level factor like A,T,G,C with 2bit instead of 32bit (?vmode) - fast chunked iteration (?chunk) - run linear model on large dataset using biglm (?chunk.ffdf) - handle boolean selections by factor 32 faster and less RAM consuming (?bit) - handle very skewed selections very fast (?bitwhich) - parallel access to large dataset just by sending ff's small metadata from master to slaves (e.g. with snowfall) ff is hosted on r-forge now and you find some presentations on ff at http://ff.r-forge.r-project.org/ Hope you find this useful. We appreciate any feedback. Jens & Daniel...

Circa 80 CRAN and core-R packages have duplicate export entries in their NAMESPACE files. E.g., bit 1.1.9 : c("as.bit", "as.bitwhich", "as.which", "physical", "virtual") forecast 4.1 : "forecast.lm" graphics 2.15.3 : "barplot" mcmc 0.9.1 : "morph" RCurl 1.95.3 : "curlOptions" utils 2.15.3 : "RweaveLatexOptions" Would it be helpful...

...ssing a line that should have been there, due to a cut/paste error. Terry T. On 03/13/2013 06:00 AM, r-devel-request at r-project.org wrote: > Circa 80 CRAN and core-R packages have duplicate export entries in their NAMESPACE files. E.g., > bit 1.1.9 : c("as.bit", "as.bitwhich", "as.which", "physical", "virtual") > forecast 4.1 : "forecast.lm" > graphics 2.15.3 : "barplot" > mcmc 0.9.1 : "morph" > RCurl 1.95.3 : "curlOptions" > utils 2.15.3 : "RweaveLatexOptions&...