<p>From the link you posted it looks as though they used <a href="https://github.com/CGATOxford/UMI-tools" rel="nofollow noreferrer">UMI tools</a> as per the section which says
<em>'were removed and added to the name of the read as a unique molecular identifier (UMI) using UMI tools'</em>.  The link above has instructions for installation and use.
From this I would guess that this data has Unique Molecular Identifiers (UMIs) for each read.<br>
Looking up the protocol for the nextflex kit used <a href="http://www.biooscientific.com/portals/0/manuals/ngs/5132-05-nextflex-small-rna-seq-v3.pdf?utm_source=copy+of+citation+dist+melanoma&amp;utm_campaign=small+rna+v3+launch+dist&amp;utm_medium=email" rel="nofollow noreferrer">(See Link)</a> confirms this:</p>

<blockquote>
  <p><strong>Data Analysis</strong>
  The 3' and 5' adapters included in this kit both contain 4 random bases that will appear immediately 5' and 3' to the insert in sequencing data. The presence of these random bases should be considered when choosing an alignment strategy. When using “end-to-end” alignment, we
  recommend processing data in the following manner: 
  1. Clip the 3' adapter sequence (TGGAATTCTCGGGTGCCAAGG).
  2. Trim the first and last 4 bases from the adapter-clipped reads.
  3. Perform alignments as normal. </p>
</blockquote>

<p>It seems that N4 is a 4 base random barcode at both the 5'&amp; 3' end of the read - these are cut from the read and this metadata is added to the read name so that every read can be uniquely identified.</p>

<p><em>Edit:</em></p>

<p>You can install UMI tools via:</p>

<p><code>conda install -c bioconda -c conda-forge umi_tools</code></p>

<p>or</p>

<p><code>pip install umi_tools</code></p>

<p>Usage instructions can be found at:</p>

<p><a href="https://umi-tools.readthedocs.io/en/latest/reference/extract.html" rel="nofollow noreferrer">https://umi-tools.readthedocs.io/en/latest/reference/extract.html</a></p>

<blockquote>
  <p>Usage:
  For single ended reads, the following reads from stdin and outputs to stdout:</p>
  
  <p>umi_tools extract --extract-method=string --bc-pattern=[PATTERN] -L extract.log [OPTIONS]</p>
  
  <p>For paired end reads, the following reads end one from stdin and end two from FASTQIN and outputs end one to stdin and end two to FASTQOUT:</p>
  
  <p>umi_tools extract --extract-method=string --bc-pattern=[PATTERN] --bc-pattern2=[PATTERN] --read2-in=[FASTQIN] --read2-out=[FASTQOUT] -L extract.log [OPTIONS]</p>
</blockquote>

CC BY-SA 4.0
2019-08-04T19:51:22.207Z
Dear@Graeme, let me ask that how can I find [PATTERN] for GSM3139597?
Mohammad
CC BY-SA 4.0
2019-07-22T12:27:36.743Z
2019-07-24T08:51:36.667Z
2019-07-24T08:51:36.667Z
Graeme
<p>I have to analyse <a href="https://www.ncbi.nlm.nih.gov/geo/query/acc.cgi?acc=GSE114327" rel="nofollow noreferrer">GSE114327</a>. For that, I use GSE instruction based on <a href="https://www.ncbi.nlm.nih.gov/geo/query/acc.cgi?acc=GSM3139597" rel="nofollow noreferrer">GSM3139597</a>.</p>

<p>In that data processing section has written:</p>

<blockquote>
  <p>FASTQ reads were subjected to adapter removal (cutadapt) per manufacturer's instructions (NEXTflex Small RNA Sequencing Kit v3).</p>
</blockquote>

<p>So, I use <code>cutadapt</code> for trimming. Then </p>

<blockquote>
  <p>The degenerate sequences (N4) at the 5' and 3' end of the reads were removed</p>
</blockquote>

<p>based on the instruction. But I don’t understand that sentence and I don’t know how I can remove degenerate sequence (N4) at the 5' and 3' of the reads.</p>

<fastq><data-preprocessing>
How to remove degenerate sequence (N4) at the 5' and 3' of the reads?
# How to remove degenerate sequence (N4) at the 5' and 3' of the reads?

(Asked by: username_0 on 2019-07-21)

I have to analyse [GSE114327](https://www.ncbi.nlm.nih.gov/geo/query/acc.cgi?acc=GSE114327). For that, I use GSE instruction based on [GSM3139597](https://www.ncbi.nlm.nih.gov/geo/query/acc.cgi?acc=GSM3139597).

In that data processing section has written:

> FASTQ reads were subjected to adapter removal (cutadapt) per manufacturer's instructions (NEXTflex Small RNA Sequencing Kit v3).

So, I use `cutadapt` for trimming. Then

> The degenerate sequences (N4) at the 5' and 3' end of the reads were removed

based on the instruction. But I don’t understand that sentence and I don’t know how I can remove degenerate sequence (N4) at the 5' and 3' of the reads.

**Tags:** fastq, data-preprocessing

---

## 1 answers

### Answer by username_1 on 2019-07-22. Score: 3

From the link you posted it looks as though they used [UMI tools](https://github.com/CGATOxford/UMI-tools) as per the section which says
*'were removed and added to the name of the read as a unique molecular identifier (UMI) using UMI tools'*. The link above has instructions for installation and use.
From this I would guess that this data has Unique Molecular Identifiers (UMIs) for each read.  
Looking up the protocol for the nextflex kit used [(See Link)](http://www.biooscientific.com/portals/0/manuals/ngs/5132-05-nextflex-small-rna-seq-v3.pdf?utm_source=copy+of+citation+dist+melanoma&utm_campaign=small+rna+v3+launch+dist&utm_medium=email) confirms this:

> **Data Analysis**
> The 3' and 5' adapters included in this kit both contain 4 random bases that will appear immediately 5' and 3' to the insert in sequencing data. The presence of these random bases should be considered when choosing an alignment strategy. When using “end-to-end” alignment, we
> recommend processing data in the following manner:
> 1. Clip the 3' adapter sequence (TGGAATTCTCGGGTGCCAAGG).
> 2. Trim the first and last 4 bases from the adapter-clipped reads.
> 3. Perform alignments as normal.

It seems that N4 is a 4 base random barcode at both the 5'& 3' end of the read - these are cut from the read and this metadata is added to the read name so that every read can be uniquely identified.

*Edit:*

You can install UMI tools via:

`conda install -c bioconda -c conda-forge umi_tools`

or

`pip install umi_tools`

Usage instructions can be found at:

<https://umi-tools.readthedocs.io/en/latest/reference/extract.html>

> Usage:
> For single ended reads, the following reads from stdin and outputs to stdout:
>
> umi\_tools extract --extract-method=string --bc-pattern=[PATTERN] -L extract.log [OPTIONS]
>
> For paired end reads, the following reads end one from stdin and end two from FASTQIN and outputs end one to stdin and end two to FASTQOUT:
>
> umi\_tools extract --extract-method=string --bc-pattern=[PATTERN] --bc-pattern2=[PATTERN] --read2-in=[FASTQIN] --read2-out=[FASTQOUT] -L extract.log [OPTIONS]

> **Comments:**
> **username_0**: Dear@Graeme, let me ask that how can I find [PATTERN] for GSM3139597?  

---

