Closed hanrong498 closed 5 months ago
Dear Hanrong,
thank you very much for sharing your insight. You're points look valid to me. Although I wasn't able to reproduce #898 concerning the low mapping rates, neither on our nor on the user's test data, I can take another look, considering your suggestion.
Best wishes,
Katarzyna
The fix is now available in snakePipes 2.8.0, 2.8.1.
Hi!
I think I might have found a small bug in the WGBS QC Report.
The
Mapping rate
session reports a mapping rate different to theGeneral Statistics
fromMultiQC
.WGBS QC report:![Screenshot 2023-10-20 at 16 54 07](https://github.com/maxplanck-ie/snakepipes/assets/72998255/c7bb8df5-220f-4555-b9bb-2dac2e22efd6)
MultiQC:![Screenshot 2023-10-20 at 17 08 49](https://github.com/maxplanck-ie/snakepipes/assets/72998255/0ac59405-c923-428f-83d2-c9b51db36071)
=========================================
I took a look at the
.flagstat
file:From the code provided to calculate the mapping rate in WGBS pipeline, it seems that it actually extract the information on the 5th line, which corresponds to
68380322 + 21154712 duplicates
rather than the mapped reads.Similarly, the PCR duplication rate is extracting the information in the 4th line, which corresponds to
0 + 0 supplementary
This is potentially the cause of the issue #898, where the mapping rate is reported to be very low.
Best, Hanrong