Hi QIIME2 team,
I have a persistent error when I try to import single-end using SingleEndFastqManifestPhred3.
qiime tools import
init.py:962: UserWarning: Duplicate key in file "/home/p277936/.config/matplotlib/matplotlibrc", line #17
There was a problem importing manifest.txt:
/local/1498484/q2-SingleLanePerSampleSingleEndFastqDirFmt-_1v7m77v/CH3E_50_L001_R1_001.fastq.gz is not a(n) FastqGzFormat file:
Missing sequence for record beginning on line 5
Manifest file: NOTE: they dont even are named as in the error appears
how fastqfile looks like
Could someone help explain what is happening?
If you requiired mor details please et me know
Thanks in advance!!
An off-topic reply has been split into a new topic:
How to use/define new source formats?
Please keep replies on-topic in the future.
I will try!
Let’s break down the error message: in the file for the forwards reads of sample
CH3E, the fastq record beginning on line 5 is missing sequence data.
Is there screenshot you provided for sample
CH3E? If not, can you send along a screenshot for that sample?
They look right to me - you specified the sample ID is
CH3E, and that was is what is reflected in the filename during import (
CH3E_50_L001_R1_001.fastq.gz). The first part of the filename is the sample ID. The rest is described here:
The underscore-separated fields in this file name are the sample identifier, the barcode sequence or a barcode identifier, the lane number, the read number, and the set number.
Basically, everything besides the sample ID and the read direction don’t really serve a purpose at this stage (and on) in an analysis.
Hope that helps, looking forward to your reply!
Thanks for your reply!
Here the screenshot.
I see some empty sequences. For trimming the barcodes and demultiplexing I used the -cutadapt command maybe it is causing the problem?
Looking forward to your reply
Check out this post for a workaround!
With that little bit of data you provided, I was able to reproduce the error. Not only that, but I was able to see ( ) exactly what the issue is. Running the same command you provided above, but instead of using q2-cutadapt we go through cutadapt directly, I get some reads out of cutadapt that look like this:
Yowzah! So, hopefully that QIIME 2 error makes a bit more sense now --- it was complaining about records that had no sequence as…
Let us know if you need help with any of that!
This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.