Closed jksr closed 3 years ago
Can you explain why this is necessary? If trimming is interrupted, it means some issue needs user attention?
occasionally, I come into this error when the snakemake proceeds to the rule "summary"
Traceback (most recent call last): ...... raise KeyError(key) from err KeyError: 'in_reads'
which means cutadapt step has problem but somehow not detected. probably it still returns 0. No idea what happened, but rerun this step usually fix it.
No. if something wrong happens but returns 0, this step will not fix it... you can discard this change
I will write a checking step and create a pull request later.
OK, thanks! Close for now.
If trimming is interrupted for any reason, the error message will be written to .trimmed.stats.tsv, which will fool the snakemake to proceed with all downstreaming rules. Added a buffer step to make it more robust.
Same modification should be done for mct and m3c accordingly.