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

bamCoverage taking four nucleotides instead of three when --MNase is used #1118

Open
feraltp opened this issue Jan 27, 2022 · 0 comments
Open

Comments

@feraltp
Copy link

feraltp commented Jan 27, 2022

Hello,

I think there may be an error in bamCoverage when using the --MNase option. It seems that four nucleotides are reported (one left to the center, the center, and two right two the center) when I would expect three for odd fragment sizes; when the fragment sizes are even, the two nucleotides at the center are reported as expected. I think it would be good to point out in the documentation on the website that two or three nucleotides are considered (in reality two or four) depending on the fragment size parity.

I attach here the small bam file that has even and odd fragment sizes together with the bedgraph produced by bamCoverage (the issue is present also for the bigwigs).

BamBedgraph.zip

The deeptools version that I used is not the latest but I didn't see there was any change reported on CHANGES.txt for that particular thing.

deeptools --version
deeptools 3.4.1

python --version
Python 3.9.5

This is the command that I used (the original one had more parameters but I don't think they are interfering with the problem):
bamCoverage --MNase -b AlignmentSimulation.bam -o mnase_AlignmentSimulation.bedgraph -bs 1 -of bedgraph

Here is just one of the examples in IGV. The fragment is 449 bps long and the middle part is four bps long:

IGVScreenshot_oddLength

Thank you,
Luis

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

1 participant