Skip to content

Fix denominator in output stats to all mapped reads only, not all in BAM#11

Merged
apeltzer merged 1 commit intoapeltzer:masterfrom
jfy133:master
Sep 27, 2020
Merged

Fix denominator in output stats to all mapped reads only, not all in BAM#11
apeltzer merged 1 commit intoapeltzer:masterfrom
jfy133:master

Conversation

@jfy133
Copy link
Copy Markdown
Contributor

@jfy133 jfy133 commented Sep 25, 2020

@TCLamnidis and I realised recently that DeDup incorrectly reports dedupping stats when unmapped reads are included in the BAM file. In EAGER1, unmapped reads were removed by default, but eager2 has a different behaviour.

By leaving in unmapped reads, and using 'totals reads' in the BAM file, this makes an artificially large denominator that makes cluster factors/duplication rates much smaller than they actually are.

As de-dupping is performed on coordinates on the reference genome, dedupping only effects mapped reads therefore all stats should be based on that value.

@apeltzer
Copy link
Copy Markdown
Owner

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

Successfully merging this pull request may close these issues.

2 participants