-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
expressed_regions() is not working with the new IDIES and AWS bigWig file locations #23
Comments
A quick check on an older version of BioC (3.11) and rtracklayer (1.50.0) appears to work:
|
I'll need to setup a newer version of BioC with recount to further test the later versions, but I'm guessing this is an openssl<->rtracklayer interaction issue |
Awesome, thanks for this info Chris! I'll create an issue for https://github.com/lawremi/rtracklayer |
I just wrote lawremi/rtracklayer#83. Let's see where that leads. Thanks again Chris! |
…lks/snaptron#17. Also #23. I tried insulating recount from these tests, so they'll be reported as warnings instead of errors on the BioC build machines for now.
…lks/snaptron#17. Also #23. I tried insulating recount from these tests, so they'll be reported as warnings instead of errors on the BioC build machines for now.
Note that I posted an update to lawremi/rtracklayer#83 (comment) today and updated the |
Hi,
Currently in BioC release (3.16) and devel (3.17),
recount
is failing. That's because neither the new IDIES location nor AWS are allowing us to read the BigWig files from the web. I manually edited a local clone ofrecount
to try with the IDIES location.You can test this on AWS (through duffel) with:
from
recount/tests/testthat/test-data.R
Line 112 in 7301c5f
This is the type of warning we get:
I'm not sure what to do @nellore @ChristopherWilks.
I can try to provide a smaller test, digging into
.loadCoverageBigWig()
https://github.com/lcolladotor/derfinder/blob/5c1cbd412c5787bf2d2d778977e38dd6ae64976d/R/loadCoverage.R#L384 and well, ultimatelyrtracklayer
.Best,
Leo
The text was updated successfully, but these errors were encountered: