Re-implements FASTQ extraction to remove problematic reads
Related issues
Lately, I have been having a lot of issues with the following:
Non-ASCII encoded characters
ASCII control characters
Un-equal seq and quality strings.
This implementation now scans the entire FASTQ (SE and PE) and removes problems reads. If the headers don't match up in PE data then it is automatically switched to SE. I hope this will solve some of the instability I see in the pipeline which typically traces back to one of these problems.
What does it do?
Related issues
Lately, I have been having a lot of issues with the following:
This implementation now scans the entire FASTQ (SE and PE) and removes problems reads. If the headers don't match up in PE data then it is automatically switched to SE. I hope this will solve some of the instability I see in the pipeline which typically traces back to one of these problems.