Dear colleagues,
One of my students is currently working on a package that we plan to
submit to Bioconductor. I want him to adhere to the Bioconductor coding
standards which I thought were available at
http://wiki.fhcrc.org/bioc/Coding_Standards. However, it turned out that
the site is down
On 26 March 2013 09:26, Ulrich Bodenhofer bodenho...@bioinf.jku.at wrote:
Dear colleagues,
One of my students is currently working on a package that we plan to submit
to Bioconductor. I want him to adhere to the Bioconductor coding standards
which I thought were available at
On 03/26/2013 12:18 PM, Laurent Gatto wrote:
On 26 March 2013 09:26, Ulrich Bodenhofer bodenho...@bioinf.jku.at wrote:
Dear colleagues,
One of my students is currently working on a package that we plan to submit
to Bioconductor. I want him to adhere to the Bioconductor coding standards
which I
On Tue, Mar 26, 2013 at 7:27 AM, Ulrich Bodenhofer bodenho...@bioinf.jku.at
wrote:
On 03/26/2013 12:18 PM, Laurent Gatto wrote:
On 26 March 2013 09:26, Ulrich Bodenhofer bodenho...@bioinf.jku.at
wrote:
Dear colleagues,
One of my students is currently working on a package that we plan to
Hi everybody.
I am experiencing problems with rGADEM. Say I have the following script,
which I have written trying to replicate the error:
library(FDb.InfiniumMethylation.hg19)
library(BSgenome.Hsapiens.UCSC.hg19)
library(rGADEM)
annot - get450k()
rois - keepSeqlevels(annot[1:10],
hi Gustavo,
just in case it helps, here is a one-minute crash course on valgrind. a
way that helped me in the past to learn interpreting valgrind output was
to make a toy example with memory leaks and then see how valgrind was
detecting them. code the following C program under the name
Hi,
Attached is the input file that I used to run EdgeR for my data set.
Ideally the input file should be able to run through the following R-script:
*library(cluster)*
*library(gplots)*
*library(Biobase)*
*library(ctc)*
*library(ape)*
*data = read.table(diffExpr.P0.0011_C1.matrix, header=T,
Package developers --
Each Bioconductor release is accompanied by release notes that mention
new packages and other significant project developments. For the
forthcoming release we would also like to include release notes for
individual packages, so that users have an easy way to survey changes
I posted this in openbabel-devel but didn't get much help, so hopefully
someone here can help. I don't think its too openbabel specific.
I would like to make use of open babel from within the R language.
Initially I just need to do some format conversions, but may expand the
usage to other
On 25 March 2013 at 12:50, Kevin Horan wrote:
| I posted this in openbabel-devel but didn't get much help, so hopefully
| someone here can help. I don't think its too openbabel specific.
|
| I would like to make use of open babel from within the R language.
| Initially I just need to do some
MM == Martin Maechler maech...@stat.math.ethz.ch
on Tue, 19 Mar 2013 17:16:42 +0100 writes:
RG == Renaud Gaujoux ren...@mancala.cbio.uct.ac.za
on Sun, 17 Mar 2013 10:38:44 +0200 writes:
RG Late report is better than never isn't it? :)
Well,... you forgot to show the error
Hi,
I used to use currentTime() (from /src/main/datetime.c) to time various
sections of data.table C code in wall clock time in sub-second accuracy
(type double), consistently across platforms. The consistency across
platforms is a really nice feature of currentTime(). But currentTime()
Would it make sense for as.Date.POSIXct to not assume tz=UTC if the
POSIXct object has a valid tzone attribute? Current behavior may be
confusing in certain cases, for example:
(d - structure(1090450800, tzone=Europe/Berlin,
+ class=c(POSIXct,POSIXt)))
[1] 2004-07-22 01:00:00 CEST
as.Date(d)
It turns out the reason for this is pretty simple:
sys.source does:
for (i in exprs) eval(i, envir)
where source basically does
n - length(exprs)
for (i in seq_len(n)) eval(expr[i], envir)
so the problem is presumably related to the way that for strips attributes.
Hadley
On Tue, Mar 19, 2013
On 13-03-26 6:45 PM, Hadley Wickham wrote:
It turns out the reason for this is pretty simple:
sys.source does:
for (i in exprs) eval(i, envir)
where source basically does
n - length(exprs)
for (i in seq_len(n)) eval(expr[i], envir)
so the problem is presumably related to the way that for
The help page for mean still says there is a method for data.frame although
this has been deprecated for several versions and in R 3.0.0 beta I get:
mean(data.frame(x=rnorm(10), y=rnorm(10)) )
[1] NA
Warning message:
In mean.default(data.frame(x = rnorm(10), y = rnorm(10))) :
argument is
Sounds good for me.
Thanks.
2013/3/27 Duncan Murdoch murdoch.dun...@gmail.com
On 13-03-26 6:45 PM, Hadley Wickham wrote:
It turns out the reason for this is pretty simple:
sys.source does:
for (i in exprs) eval(i, envir)
where source basically does
n - length(exprs)
for (i in
17 matches
Mail list logo
