dear wham's team,
when i use whamg to call SV for pig, i found INFO: SBZ0002.bam had **14838 reads** that were not processed appeared in the error log, I tried to locate the source of this error
Tried:
- lowering the
-m parameter of wham, which corresponds to the MAPQ field of the bam file (compare quality), and the new error log shows **14838 reads** that were not processed, which is not much lower compared to the 14840 reads in the old error log
samtools flagstat checks for unmapped reads or corrupted reads, the output is 581496 reads.
samtools view -@ 30 -c -f 4 checks the number of unmapped reads and the output is 581496 reads.
How can I locate which settings within wham the unmatched reads are due to? Could you please provide some suggestions?
Much appreciated!
Celeste