You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've found this issue when running a fork under #16, which assumes the mates of reads are labelled. I think it's still an issue otherwise but not very severe - the kneaddata_bowtie2_discordant_pairs would, I guess, not match SRR3132037.1.11length=142 and SRR3132037.1.21length=142, as a consequence put them in a wrong file and the --strict option there wouldn't work correctly.
I have a workaround for the issue on my end, but if you like I am happy to fix it in the codebase. I see that utilities.get_reformatted_identifiers does some reformatting. I would change it to remove the description, and also format the quality line to just "+".
The text was updated successfully, but these errors were encountered:
wbazant
added a commit
to VEuPathDB/humann-nextflow
that referenced
this issue
Feb 23, 2021
I have a file with reads formatted like:
It's not a bad file according to https://en.wikipedia.org/wiki/FASTQ_format, and it's a default format from fastq-dump.
It's reformatted as such:
I've found this issue when running a fork under #16, which assumes the mates of reads are labelled. I think it's still an issue otherwise but not very severe - the
kneaddata_bowtie2_discordant_pairs
would, I guess, not matchSRR3132037.1.11length=142
andSRR3132037.1.21length=142
, as a consequence put them in a wrong file and the --strict option there wouldn't work correctly.I have a workaround for the issue on my end, but if you like I am happy to fix it in the codebase. I see that
utilities.get_reformatted_identifiers
does some reformatting. I would change it to remove the description, and also format the quality line to just "+".The text was updated successfully, but these errors were encountered: