-
Notifications
You must be signed in to change notification settings - Fork 6
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
It will be very useful to add an option "--rpm" to allow users to calculate the Reads per million mapped reads #7
Comments
Is this related to #6, and specifically, are you interested in read counts (counting the number of reads mapped) in both issues rather than nucleotide coverage? |
Hi telatin, these are two independent issues. Both of them are preferred with read counts (per base is covered by how many reads). For example, if 3,000,000 reads were sequenced in total, chr1:123-123 covered by 3,00 reads, the RPM for this base will be 100. Best, |
Ok, consider that |
Oh, I must misunderstand the read counts and nucleotide coverage. Both of these #6 and #7 are preferred with nucleotide coverage. See the same example above, if 3,000,000 reads were sequenced in total, chr1:123-123 covered by 300 reads, then the nucleotide coverage and RPM for this base (chr1:123-123) will be 300 and 100. Best, |
No description provided.
The text was updated successfully, but these errors were encountered: