Skip to content
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

Implement bam-readcount CRAM support #942

Open
jasonwalker80 opened this issue Sep 1, 2020 · 3 comments
Open

Implement bam-readcount CRAM support #942

jasonwalker80 opened this issue Sep 1, 2020 · 3 comments
Assignees
Milestone

Comments

@jasonwalker80
Copy link
Member

Add support to all relevant CWL pipelines and subworkflows to use CRAM as an input format. This uses a new version of bam-readcount that natively supports CRAM.

@malachig
Copy link
Collaborator

malachig commented Sep 1, 2020

I see no evidence of any work being done on bam-readcount itself:
https://github.com/genome/bam-readcount

If this is being tracked elsewhere, why?

@tmooney
Copy link
Member

tmooney commented Sep 1, 2020

There is a branch on a fork where work has been taking place: https://github.com/seqfu/bam-readcount/tree/samtools-1.10, but it hasn't been pushed back to the main repository as of yet.

If I were to speculate as to why it's not tracked on the repo, it's related to the fact that this has been a hackathon-related topic and so worked on in bursts primarily using the more realtime communications of Slack (in the #bam-readcount channel). A lot of our issue-tracking has been coordinated around the hackathons as seen in this issue, so even things that reach beyond the analysis-workflows have mostly been coordinated via boards like here: https://github.com/genome/analysis-workflows/projects

@chrisamiller
Copy link
Collaborator

bam readcount 1.0.0 has full cram support. All that is needed is to upgrade the docker container in the relevant steps at this point

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

No branches or pull requests

6 participants