bam-readcount -d option is not working
Hi! I am analyzing bam files with more than 300,000 reads per site... But the maximum depth that the bam-readcount output reports is 8000. I saw a post from 2013 where the same problem was fixed. But i think the patch is not working in new versions.
• 1,973 views
•
link
updated
by
Devon Ryan
•
written
by
caritogandini •
•
written
by
caritogandini •
0 answers
No answers yet.
Log in to answer this question.
More posts like this
-
Why does bcftools call from different max-depth (-d) value in mpileup give inconstant GT values?
written by magnolia •
-
How to filter SNPs with excess heterozygosity from a large vcf
written by Bagelbart •
-
Finding number of reads and base calls at ~10,000 non-SNPs using BAM file?
written by devenvyas
-
GC Bias in Sequence Capture - Analysis & Quantification
written by jnowacki
-
Variant Calling (Samtools Mpileup): Error
written by venuraherath •
-
Copy number variation detection
written by v27 •
-
How to measure NGS depth coverage bias
written by Anand Rao
-
bam-readcount empty output
written by alexander.charney •
-
Samtools mpileup -g and -u flags throwing errors for a specific bam file
written by top1214 •
-
current release of bam-readcount version
written by bioguy24
This has been a known bug since at least 2015. The only current fix is to specify a region. Alternatively, fix the actual source code.
how i fix the actual source code?
You'd need to find where this is implemented and change it.