Hello! I have used QIIME2 many times and never run into this error, despite having used Paired End Phred33V2 data types every time. I am trying to import Paired End Phred33V2 forward and reverse reads into a demux.qza file using a manifest. The manifest is as follows ( | indicates the presence of a tab):
I am using this script to import the data, as I have many times in the past (this script is in fact copied from my scripts with only the file names changed):
qiime tools import
–input-format PairedEndFastqManifestPhred33V2 \
I am in the directory with the manifest. I am receiving this error each time I attempt to import the data:
There was a problem importing /home/qiime2/Desktop/16its/16its-manifest.txt:
/home/qiime2/Desktop/16its/16its-manifest.txt is not a(n) PairedEndFastqManifestPhred33V2 file:
Filepath on line 2 and column “reverse-absolute-filepath” (sample “7.11.16”) has already been registered on line 2 and column “forward-absolute-filepath” (sample “7.11.16”).
I am quite confused with this error message. First, I am quite sure that the data is in the correct format for an "–input-format PairedEndFastqManifestPhred33V2 " argument, as I am using data from the same sequencing company I always use. Second, I am confused why QIIME2 has an issue with me importing forward and reverse reads under the same name, as that is the whole point of using a Paired End Fastq format. Why is QIIME2 telling me that the name “7.11.16” has already been registered when only the forward read for that sample has been read? As you can see from the manifest, 7.11.16 is not the first sample in the manifest, so if this was an error with the format of the manifest why was the error not returned on the first sample?
I tried to see if perhaps they sent data in Phred64V2 format, but that did not work and returned the same error message.
I also tried using a .tsv format for the manifest, but that also returned the same error message.
I am using QIIME2 2019.4 on a Windows 10 machine inside a VM session, as I usually do. I am using this version because the classifiers I have were trained using 2019.4 and the computational demand of training a new classifier on a more recent version of QIIME2 is not possible from my laptop due to work from home restrictions.
Thank you all for your consideration and time assisting me with this error, have a pleasant day and stay safe!