seen QuasR (and/or gmapR, Rsubread, etc.)? one can run BowTie, gsnap, etc.
from R
this certainly makes it easier for me to remember how I did some ChIP-seq
or BS-seq or RNA-seq processing a year ago, when it turns out I need to add
a sample or samples and carry on with an existing analysis pipeli
There are utilities ( e.g. dotkit, and modules) which facilitate version
management, basically creating on the fly PATH and env setups, if you are
comfortable keeping all that around.
David
-Original Message-
From: bioconductor-boun...@r-project.org
[mailto:bioconductor-boun...@r-proj
*Summary:
*
During package loading the library function calls file.info to determine if
a file is a directory. This uselessly invokes getpwuid and getgrgid which
can be expensive if the user/group database are held on a network.
Note that file_test ALSO uses file.info for the same purpose
Sugg
Hi R-devel,
When using lapply upon data.frame, I notice lapply coerces data.frame to list
before calling internal lapply function.
R> lapply
function (X, FUN, ...)
{
FUN <- match.fun(FUN)
if (!is.vector(X) || is.object(X))
X <- as.list(X)
.Internal(lapply(X, FUN))
}
df <-
Thanks David, I've looked into them both a bit, and I don't think the provide
an approach for R (or Perl, for that matter) library management, which is the
wicket I'm trying to get less sticky now.
They could be useful to manage the various installations of version of R and
analysis files (we'r
Thanks.
This is in the netlib loess code: the size is used in Fortran (and an
INTEGER) so we cannot increase it. I've added a test and thrown an
error if the dimension is too large.
On 01/03/2013 11:27, Hiroyuki Kawakatsu wrote:
Hi,
I am segfaulting when using predict.loess() (checked wit
The message below came to me from the Getting Open Source Logic INto
Government list. I'm passing it on to the devel list as the infoworld
article may have some ideas of relevance to the R project, mainly
concerning build and test issues and tracking changes in the code base.
While the LibreOff
Hi!
In RKWard we use R_tryEval() at a number places to run R commands. In order to
make sure that any generated warnings become visible close to the problem, we
were following up (most of) these calls with Rf_PrintWarnings().
Rf_PrintWarnings() was never available in the headers (as far as I kn
