# Error during demultiplexing using 2019 versions

**URL:** https://forum.qiime2.org/t/error-during-demultiplexing-using-2019-versions/12597
**Category:** Technical Support
**Created:** [November 22, 2019, 5:57pm UTC](https://forum.qiime2.org/t/error-during-demultiplexing-using-2019-versions/12597 "2019-11-22T17:57:00Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![linneakh](https://forum.qiime2.org/user_avatar/forum.qiime2.org/linneakh/32/87_2.png) [@linneakh](https://forum.qiime2.org/u/linneakh)
#### Post date: [November 22, 2019, 5:57pm UTC](https://forum.qiime2.org/t/error-during-demultiplexing-using-2019-versions/12597/1 "2019-11-22T17:57:00Z")

</div>

I am re-analyzing a dataset that I've previously, and successfully, analyzed using a 2018 version of qiime2, this time using versions 2019.4, and 2019.10. Here is my command:

qiime demux emp-paired   
--m-barcodes-file sample\_metadata.txt   
--m-barcodes-column BarcodeSequence   
--i-seqs emp-paired-end-sequences.qza   
--o-per-sample-sequences demux.qza   
--o-error-correction-details demux-details.qza   
--verbose

This time, I keep getting the following error:

ValueError: No sequences were mapped to samples. Check that your barcodes are in the correct orientation (see the rev\_comp\_barcodes and/or rev\_comp\_mapping\_barcodes options).

These are golay barcodes that should be in the forward primer with no need to do the reverse complement. Does anyone have any idea of why this isn't working this time? Are there any changes that occurred between 2018 and 2019 that I am missing?

Best,

Linnea

---

<div class="post-metadata">

### Author: ![thermokarst](https://forum.qiime2.org/letter_avatar_proxy/v4/letter/t/8e7dd6/32.png) [@thermokarst](https://forum.qiime2.org/u/thermokarst)
#### Post date: [November 22, 2019, 6:09pm UTC](https://forum.qiime2.org/t/error-during-demultiplexing-using-2019-versions/12597/2 "2019-11-22T18:09:41Z")

</div>



---

<div class="post-metadata">

### Author: ![thermokarst](https://forum.qiime2.org/letter_avatar_proxy/v4/letter/t/8e7dd6/32.png) [@thermokarst](https://forum.qiime2.org/u/thermokarst)
#### Post date: [November 22, 2019, 6:13pm UTC](https://forum.qiime2.org/t/error-during-demultiplexing-using-2019-versions/12597/3 "2019-11-22T18:13:50Z")

</div>

> [@linneakh](#):
>
> Are there any changes that occurred between 2018 and 2019 that I am missing?

Yep! We added automatic Golay barcode error correction earlier this year. In order for EC to work you have to:

a) ensure your barcode sequences are in 5'-3' orientation  
b) ensure your barcode mapping is in 5'-3' orientation

There are two flags to control that behavior, `rev-comp-barcodes` and `rev-comp-mapping-barcodes`, respectively. You can also completely disable EC by using the `golay-error-correction` flag.

> [@linneakh](#):
>
> These are golay barcodes that should be in the forward primer with no need to do the reverse complement

Are the barcode sequences in the same orientation as the barcode mapping? It sounds like if they are, then your barcode sequences themselves are in the wrong orientation, and you will need to RC both barcode sequences and the barcode mapping.

---

<div class="post-metadata">

### Author: ![thermokarst](https://forum.qiime2.org/letter_avatar_proxy/v4/letter/t/8e7dd6/32.png) [@thermokarst](https://forum.qiime2.org/u/thermokarst)
#### Post date: [November 22, 2019, 6:13pm UTC](https://forum.qiime2.org/t/error-during-demultiplexing-using-2019-versions/12597/4 "2019-11-22T18:13:54Z")

</div>



---

<div class="post-metadata">

### Author: ![linneakh](https://forum.qiime2.org/user_avatar/forum.qiime2.org/linneakh/32/87_2.png) [@linneakh](https://forum.qiime2.org/u/linneakh)
#### Post date: [November 22, 2019, 8:37pm UTC](https://forum.qiime2.org/t/error-during-demultiplexing-using-2019-versions/12597/5 "2019-11-22T20:37:03Z")

</div>

Thank you! Doing RC on both barcode sequences and barcode mapping solved this issue.
