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

Return read counts per chromosome #512

Closed
AndreasHeger opened this issue Jul 21, 2017 · 4 comments
Closed

Return read counts per chromosome #512

AndreasHeger opened this issue Jul 21, 2017 · 4 comments

Comments

@AndreasHeger
Copy link
Contributor

Similar to idxstats, return for each chromosome:

  1. Total read count
  2. Mapped read count
  3. Unmapped read count (e.g. where one of a pair is mapped and the other is not)
@bioinformed
Copy link
Member

bioinformed commented Jul 24, 2017

I agree this would be useful functionality, but perhaps better in in an application and not the core library. What will we do when users request counts based on BED file masking, on/near/off-target counts, stratification by mapping quality, etc? That said, I don't have a problem if the application is part of pysam -- just that we don't attempt to build all of this functionality into the AlignmentFile object.

@AndreasHeger
Copy link
Contributor Author

Thanks. The gist of this feature is simply to expose the data that is contained in the BAM index anyways, i.e. there is not any algorithmic component.

@bioinformed
Copy link
Member

Ah-- I thought you meant to build a counter function that generated data similar to idxstats. It all that is being proposed is an API to expose idxstats then I withdraw all objections.

@AndreasHeger
Copy link
Contributor Author

Note to self: add total

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