<p>It depends on the read layout they used, but typically when I hear anyone talk about removing adapters in paired-end sequencing, it's the occurrences of adapter sequences at the <em>ends</em> of each read from the <em>complementary strand's</em> adapter.  For example see the figures on <a href="https://www.idtdna.com/pages/education/decoded/article/16s-rrna-indexed-primers-amplify-phylogenic-markers-for-microbiome-sequencing-analysis" rel="nofollow noreferrer">this IDT page about 16S sequencing</a>.  If a given sequence is short enough/number of sequencing cycles high enough, you'll end up seeing &quot;past the ends&quot; on each read.</p>
<p>For example, with a reverse read reverse-complemented and aligned with a forward read, you could maybe see something like this off the sequencer:</p>
<pre><code>                       |--&gt;
Forward:               BarcodefwdAmpliconBarcoderevAdapterrev...
Reverse:  ...AdapterfwdBarcodefwdAmpliconBarcoderev
                                               &lt;--|
</code></pre>
<p>And then if the company already removed barcodes and primers at the start of the reads, maybe they gave you:</p>
<pre><code>                                 |--&gt;
Forward:                         AmpliconBarcoderevAdapterrev...
Reverse:  ...AdapterfwdBarcodefwdAmplicon
                                     &lt;--|
</code></pre>
<p>So the material you'd want to trim is on the ends, and reverse-complemented.  How much you see depends on the lengths involved so maybe you'll see partial adapters or none at all, and there may be sequencing error, too.  See <a href="https://cutadapt.readthedocs.io/en/stable/guide.html#regular-3-adapters" rel="nofollow noreferrer">cutadapt's documentation about trimming 3' adapters</a> and <a href="https://cutadapt.readthedocs.io/en/stable/guide.html#trimming-paired-end-reads" rel="nofollow noreferrer">paired-end reads</a> for more on that.</p>

CC BY-SA 4.0
2021-12-10T16:53:55.427Z
2021-12-10T16:53:55.427Z
Jesse
<p>I have recently received some metagenomic data from 16S rrna sequencing. The sequencing company claim to have removed primers, however not adapter sequences. Please note that the files have been demultiplexed.</p>
<p>In the platform, we have forward and reverse strand fastq files. For each fastq file, there is information regarding the adapter used, for each strand.</p>
<p>However, when I run the following command:
<code>cat myFastQ_forward.fastq | grep 'adapter_forward'</code>, it returns nothing. My question is, shouldn't the adapters be identified successfully simply by looking for an exact match in the fastq files? If not, why?</p>
<p>Thanks,</p>

<linux><metagenome><trimming><cutadapt><16rrna>
Searching for adapter sequences in FASTQ files - metgenomics
# Searching for adapter sequences in FASTQ files - metgenomics

(Asked by: username_0 on 2021-12-09)

I have recently received some metagenomic data from 16S rrna sequencing. The sequencing company claim to have removed primers, however not adapter sequences. Please note that the files have been demultiplexed.

In the platform, we have forward and reverse strand fastq files. For each fastq file, there is information regarding the adapter used, for each strand.

However, when I run the following command:
`cat myFastQ_forward.fastq | grep 'adapter_forward'`, it returns nothing. My question is, shouldn't the adapters be identified successfully simply by looking for an exact match in the fastq files? If not, why?

Thanks,

**Tags:** linux, metagenome, trimming, cutadapt, 16rrna

---

## 1 answers

### Answer by username_1 on 2021-12-10. Score: 0 | Accepted answer

It depends on the read layout they used, but typically when I hear anyone talk about removing adapters in paired-end sequencing, it's the occurrences of adapter sequences at the ends of each read from the complementary strand's adapter.  For example see the figures on this IDT page about 16S sequencing.  If a given sequence is short enough/number of sequencing cycles high enough, you'll end up seeing "past the ends" on each read.
For example, with a reverse read reverse-complemented and aligned with a forward read, you could maybe see something like this off the sequencer:
                       |-->
Forward:               BarcodefwdAmpliconBarcoderevAdapterrev...
Reverse:  ...AdapterfwdBarcodefwdAmpliconBarcoderev
                                               <--|

And then if the company already removed barcodes and primers at the start of the reads, maybe they gave you:
                                 |-->
Forward:                         AmpliconBarcoderevAdapterrev...
Reverse:  ...AdapterfwdBarcodefwdAmplicon
                                     <--|

So the material you'd want to trim is on the ends, and reverse-complemented.  How much you see depends on the lengths involved so maybe you'll see partial adapters or none at all, and there may be sequencing error, too.  See cutadapt's documentation about trimming 3' adapters and paired-end reads for more on that.


---

