--max-reads-per-alignment-start
is helpful because the genome has a few hotspots of extremely high coverage, due to mapping error for the most part, where to avoid spending an inordinate amount of compute on these few regions we truncated the coverage. For example, a 100x exome may have a few thousand bp with 10,000x coverage.
However, this behavior should be turned off, by setting --max-reads-per-alignment-start 0 , when the coverage is uniformly high and one wants to use that depth to discover low-AF variants.
1 comment
Hi, I will call vcf in the deep seqeuncing data ( 10,000x coverage ) with Mutect2. Should I set --max-reads-per-alignment-start 0 ?
Please sign in to leave a comment.