The largest source of failure in the workflow stems from CutAdapt's stringent requirement that fastq files have no mismatched reads.
Example Error
cutadapt: error: Reads are improperly paired. Read name 'NS500257:75:HLN25BGX5:1:11101:10293:1043 1:N:0:2' in file 1 does not match 'NS500257:76:HTH2NBGX5:2:11101:24171:1047 2:N:0:1' in file 2.
It would be nice to allow the user an option that would fix this issue within the workflow so the user isn't responsible for coming up with their own preprocessing fix prior to running the workflow.
One possible solution, although I'll need to make an appropriate Docker container for it.
The largest source of failure in the workflow stems from CutAdapt's stringent requirement that fastq files have no mismatched reads.
Example Error
It would be nice to allow the user an option that would fix this issue within the workflow so the user isn't responsible for coming up with their own preprocessing fix prior to running the workflow.
One possible solution, although I'll need to make an appropriate Docker container for it.