-
Notifications
You must be signed in to change notification settings - Fork 27
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
CRAM support - why not? #56
Comments
Thanks for your note. There hasn't been strong demand for CRAM functionality. Rhtslib is up to htslib 1.15, and the latter has moved to 1.18. Resources in Bioconductor core are very tight and it has not been clear whether Rsamtools should be upgraded to handle CRAM, or another htslib-dependent package should be introduced. If you see a way to modifying Rsamtools to deal with CRAM in a way that is useful to you we would surely work with a PR. |
FWIW some work was done by @mtmorgan last year to support CRAM, see the |
UPDATE: The latest Rhtslib (2.99.2) now includes htslib 1.18 (was 1.15). See https://github.com/Bioconductor/Rhtslib/blob/devel/DESCRIPTION. I don't know how this update will impact CRAM support in Rsamtools though. |
@pd3 please have a look at the cram branch noted in previous comments supply information on the use case and errors encountered thanks |
As noted some time ago, our core has not encountered significant demand for CRAM support. It would be logical to add such to Rsamtools, but efforts to do this have not come to closure. I followed instructions at http://www.htslib.org/workflow/cram.html to make a fresh example, but ran into errors of this nature:
That crops up while exploring a role for pysam in providing CRAM support. I'd really like to see some community input on use cases and good example files to make a case for a solution, which I suspect could involve reticulate/basilisk with pysam. |
It appears CRAM is not supported by Rsamtools. I wonder why is that? Samtools support CRAM natively, so I would naively expect this should be a trivial task, no?
This issue came up from other programs that rely on Rsamtools, please see here vplagnol/ExomeDepth#17
The text was updated successfully, but these errors were encountered: