# Kneaddata adds "#0/1" to barcode in the header

**URL:** https://forum.biobakery.org/t/kneaddata-adds-0-1-to-barcode-in-the-header/3538
**Category:** KneadData
**Created:** [May 4, 2022, 7:14pm UTC](https://forum.biobakery.org/t/kneaddata-adds-0-1-to-barcode-in-the-header/3538 "2022-05-04T19:14:44Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![akhst7](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.biobakery.org/akhst7/32/1432_2.png) [@akhst7](https://forum.biobakery.org/u/akhst7)
#### Post date: [May 4, 2022, 7:14pm UTC](https://forum.biobakery.org/t/kneaddata-adds-0-1-to-barcode-in-the-header/3538/1 "2022-05-04T19:14:44Z")

</div>

I run keaddata to remove mouse genome from 16S fastq PE reads from mouse lung as follows;

`kneaddata --input1 trimmed_255-001_S1_L001_R1_001.fastq --input2 trimmed_255-001_S1_L001_R2_001.fastq -db /Volumes/Aura/bowtie_GRCm39_DB --output kneaddata_output -t 12 --bypass-trim --bypass-trf`

Interestingly, there was no contaminating reads that were removed. Anyway, I checked the integrity of \_unmatched fastqs and noticed “#0/1” was added to the end of barcodes in the header;

```auto
@M02079:179:000000000-JKTGJ:1:1101:16873:1834.1:N:0:ATCACG#0/1
GCAATACGGGAGTGGCAAGCGTTATCCGGAATTATTGGGCGTAAAGCGTCCGCAGGCGGCTTTTCAAGTCTGCTGTTAAAACGTGGAGCTTAACTCCATCATGGCAGTGGAAACTGAAAGGCTTGAGTATGGTAGGGGCAGAGGGAATTCCCGGTGTAGCGGTGAAATGCGTAGATATCGGGAAGAACACCAGTGGCGAAGGCGCTCTGCTGGGCCATTACTGACGCTCATGGACGAAAGCCAGGGGAGC
+
111>>DFAADA1EFEAFFAF0EFEHHH0A0EBGFGHHFHFGGGGHHHGGGGGCEGGGECGGGHHFGEGGHHHHHHHHEFG>GGHGG?GGHHGFHGHFHHHHHHGHHCHHGF1GGHFGGHFEFHHGCFHFDGBGHEFGFC-CAGGGGHGHGGGGGGGGHHFGGGGGHFGHGFGBGEFFFFE@A99EFFFFGBE?FFFE?@@?FF<=@FFFFFFFBFFBFFFFFF/BB-BBAFFF/B@-9AAF-9AE--A-B

```

Is this a bug or am I doing something wrong ?  
[readItAndKeep.txt](https://forum.biobakery.org/uploads/short-url/lucaoVmBg9pegi91NfL0eVxq908.txt) (674 Bytes)