I have also used a similar command for a separate mapping file and sequences, and received a separate error: Plugin error from demux:
Unable to allocate array with shape (91548818, 6) and data type object
Debug info has been saved to /tmp/qiime2-q2cli-err-72w7xt_t.log
I have checked in the forum and apparently this is an issue with memory space, but can confirm that memory is not an issue with my computer. If it helps, here is my mapping file with the 2nd error: 54434_mapping_file.txt (21.5 KB)
What do these error messages mean particularly? What are the solutions to them with my mapping files (or not)? Thank you and I appreciate any help!
Hi @thermokarst. Thank you for your response. I have checked the barcodes fastq and if I understood it correctly, it seems to have the same format which you stated. Here are the first few lines:
Okay. I have just compared this barcode fastq to others that worked. Having â@â all the way is most likely the root of the problem. If that is the case, is there a way to demultiplex whilst disregarding quality score on the 4th line? Many thanks!
However, I am still getting the same error about description fields in the sequence but not barcode header lines. How do I rectify this to do the demux successfully?
Hello. When using the command âdemux emp-pairedâ, I received the error about sequence header lines containing âdescription fieldsâ but not barcode header lines.
The first few lines of my forward sequence file is: @DGZN8DQ1:549:H7C23BCXX:2:1101:1087:1870 1:N:0:CGTCGTATGAAT
If not mistaken, the main reason for this error is probably the 1st line of the barcode missing â1:N:0:CGTCGTATGAATâ. If this is correct, how do I make the barcode headers have corresponding description fields to the sequence headers? Cheers!
Hi @YinXun - please do not repost the same question across multiple topics - this is called cross-posting, and is a violation of our Code of Conduct. I have merged the new post back into the existing topic, for continuity.
Hi @YinXun - the message I sent above still applies â your barcodes arenât formatted correctly, specifically the ID headers donât match the forward read headers. Specifically it sounds like there is a description field in your reads, but not in your barcodes:
Thank you for your help again! I will be adding the â1:N:0:CGTCGTATGAATâ with the corresponding barcodes to each samples, which should solve the problem.
I apologise for my lack of patience and regard for the Code of Conduct.