Closed keiranmraine closed 4 years ago
Okay, so the read selection code needs to test the qscore
when selecting the read to use. In both cases above the score is good in one read and poor in the other. Selecting the read with the highest qscore will fix the edge case.
To be closed with #36
Will be released once #37 changes are approved.
PR and test example to follow, but here to allow head start on confirming I've understood this correctly @davidrajones
The following block has a problem:
https://github.com/cancerit/cgpCaVEManPostProcessing/blob/c520edd24a75a7d0c530e54129d52be43e2dfc0e/lib/Sanger/CGP/CavemanPostProcessor.pm#L308-L320
In the first block, where it tests for overlapping reads, it only records a result if both reads disagree:
https://github.com/cancerit/cgpCaVEManPostProcessing/blob/c520edd24a75a7d0c530e54129d52be43e2dfc0e/lib/Sanger/CGP/CavemanPostProcessor.pm#L309-L310
But it assigns the count only to the +ve strand:
https://github.com/cancerit/cgpCaVEManPostProcessing/blob/c520edd24a75a7d0c530e54129d52be43e2dfc0e/lib/Sanger/CGP/CavemanPostProcessor.pm#L311-L312
No counts are incremented if the reads agree which results in the process failing.
I think this should be as follows as the subsequent section handles the balancing of +/- strand:
Example data that triggered the problem: