Hi Matthew,
Hope you’re well. There is a question similar to this but the issue is already closed (New to Qiime2 Mismatched sequence ids:).
I am a new user of qiime2, and I’m having some problems with IONTORRENT sequence analysis.
Plugin error from demux:
Mismatched sequence ids: HWI-EAS440_0386: 1: 23: 17547: 1423 # 0 and YIKQF: 00004: 00005
Debug info has been saved to /tmp/qiime2-q2cli-err-cfeopbh4.log
In the link that I attached, I could see that the mappingfile must have the same number of lines as the sequence file. My mapping file only has 20 lines corresponding to the 20 barcodes. Is that the error?
Many thanks!!
Hi @PatoUru -
I moved this question out of your DM to me and into the public-facing portion of the forum - we are unable to provide private support at this time.
This is not quite correct - the sequence file needs to have the same number of lines as the barcodes file, not the metadata (mapping) file. The metadata file will have one line for each sample.
Nope - the problem is that your sequences and barcodes files aren't in the same order. Taking a step back - what files do you have from the sequencing instrument? I don't think I have ever seen EMP-formatted data off of an iontorrent instrument before.
Hi Matthew,
Finally, I found a qiime1 script, and I was able to extract the barcodes list from the multiplexed sequence file. I imported the data in qiime2 and then I started with denoising, but ... 12 hours ago I was analyzing the sequences and it was not over. Do you think maybe there is something wrong?
Can you provide some details about what the original data itself looks like? Is it multiplexed? If so, are the barcodes in the reads? Are they in the headers?
Thanks for your quick response!! I have the sequences.fastq file that contains 20 samples. The sequences are multiplexed, and it has the barcode (10bp) at the beginning of the sequence.
In bold is the barcode:
Thanks for the info @PatoUru! Good news, I think we can use an easier import/demux workflow that doesn't require you to run QIIME 1 scipts. Your data appears to be a good candidate for q2-cutadapt:
You can import and demux using cutadapt, which will be able to search your original reads for your barcodes. Please give that a shot and let us know how it goes!