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

deepconsensus-0.2.0 complains that subreads_to_ccs.bam is not indexed #16

Closed
jelber2 opened this issue Jan 19, 2022 · 2 comments
Closed

Comments

@jelber2
Copy link

jelber2 commented Jan 19, 2022

Following the tutorial,

/data/subreads_to_ccs.bam
, deepconsensus-0.2.0 complains that it cannot find the index for subreads_to_ccs.bam . Sorting with samtools sort and then samtools index fixes the warning, but is it necessary?

@MariaNattestad
Copy link
Collaborator

Sorry we didn't answer this issue sooner. No, you do not need to sort and index any bam files, and in fact I would not recommend it because DeepConsensus assumes that the inputs are in the original order that ccs and actc output. Changing that order by sorting might cause some data to be skipped during processing. We'll take a look and see if it's possible to turn off that warning, which I'm guessing is from pysam that we use for parsing the bam files.

@jelber2
Copy link
Author

jelber2 commented Jan 24, 2022

Ok thank you! I have not noticed anything with data being skipped, but maybe I was not looking carefully enough.

@jelber2 jelber2 closed this as completed Jan 24, 2022
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

2 participants