Hi Nathan,
You're right, there was a remaining issue. It should be fixed in
IRanges 2.13.26. Make sure to also get S4Vectors 0.17.32 (IRanges
2.13.26 requires it).
The 2 updated packages should become available via biocLite() in
about 24 hours but you can get them now directly from
git.bioconduc
Hi Herve,
The updates have indeed solved those issues for that sample -- However,
when you try to apply a more complicated function, I am getting the same
error. Here's a reproducible example of the error again, this time using
the latest GenomicRanges and IRanges packages:
library(GenomicRa
Hi Herve,
Never mind, I see now I am still a day old, looks like I was looking at
your sessionInfo paste and thought it was mine, whoops. I'll give it
another try tomorrow with the new versions.
other attached packages:
[1] GenomicRanges_1.31.18 GenomeInfoDb_1.15.5 IRanges_2.13.24
[4] S4Vecto
According to my `sessionInfo` (see below), those are the versions I had
been using:
other attached packages:
[1] GenomicRanges_1.31.19 GenomeInfoDb_1.15.5 IRanges_2.13.25
[4] S4Vectors_0.17.31 BiocGenerics_0.25.3
And I had pulled them from biocLite...what's going on?
-Nathan
On 02/10/2
Hi Nathan,
I can't reproduce this with the latest versions of S4Vectors (0.17.31),
IRanges (2.13.25), and GenomicRanges (1.31.19). Note that these versions
will only become available via biocLite() tomorrow but you can get them
directly from git.bioconductor.org.
With these versions, as.list, la
