Skip to content
This repository has been archived by the owner on Aug 29, 2023. It is now read-only.

Add support for CRAMs #31

Open
mbookman opened this issue Feb 23, 2018 · 6 comments
Open

Add support for CRAMs #31

mbookman opened this issue Feb 23, 2018 · 6 comments

Comments

@mbookman
Copy link

mbookman commented Feb 23, 2018

IGV.js does not support CRAMs directly, but does support htsget.
It would be great if the htsget server could support CRAMs.
I know this is listed in the README:

CRAM support will be added in the very near future.

but wanted to make the explicit request.

@dglazer
Copy link
Member

dglazer commented Mar 6, 2018

Do we know if htsget support for CRAM will automatically make it work for IGV? IIUC, htsget doesn't do any format conversion, so IGV would still need to have CRAM-aware code, even if it doesn't need to read the files directly.

@mbookman
Copy link
Author

mbookman commented Mar 6, 2018

No, you are correct. IGV.js would still need to be CRAM aware.

Will follow-up with Jim to see if he has plans to make revisit igvteam/igv.js#247 or if having server-side conversion such as https://github.com/igvteam/igv.js-flask will be the solution for the foreseeable future.

Thanks for pointing this out.

@kemp-google
Copy link

Just to add we have a pull request that adds it we just haven't merged it yet

#19

@mbookman
Copy link
Author

mbookman commented Mar 6, 2018

Thanks. BTW, on igvteam/igv.js#247, Jim has indicated that having server-side is the plan until someone writes a CRAM decoder for JavaScript.

@kemp-google
Copy link

A note to myself to update

https://github.com/samtools/hts-specs/blob/master/htsget_interop.html

when we merge this

@brainstorm
Copy link

AFAIK IGV.js does support CRAM at the moment of writing this:

https://igv.org/web/release/2.3.3/examples/cram.html

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants