Answers.Body: <p>Insertions and deletions are the dominant error mode of long read sequencing, including nanopore sequencing. What you see is not unexpected. Things may have improved by now if you would download the raw fast5 data and repeat the basecalling. There is no need to <code>gunzip</code> the fastq.gz prior to alignment. Your commands for alignment look alright, except that (if you are using a recent version of samtools) you don't really need samtools view and can pipe directly to samtools sort, using -o to specify the output format:</p>
  
  <pre><code>minimap2 -ax map-ont -t 20 &lt;index&gt; &lt;fastq&gt; | samtools sort -@5 -o alignment.bam 
  </code></pre>
  
  <p>In a recent version of igv you can right-click the alignment and chose a "Quick consensus mode" (or something like that), which will make your alignments at least a bit prettier. Note how the consensus sequence (top of the graph) is quite clean - while individual reads may be noisy this is mostly randomly distributed and as such ironed out in consensus.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-02-08T07:10:47.560Z
Answers.LastActivityDate: 2019-02-08T07:10:47.560Z
Answers.UserDisplayName: Wouter De Coster
Body: <p>I'm a starting my analysis on nanopore whole genome sequencing. I start my analysis from this popular <a href="https://github.com/nanopore-wgs-consortium/NA12878" rel="nofollow noreferrer">Github</a>.</p>
  
  <p>The sample I downloaded was WGS for NA12878, so I would assume it's alignment to GRCh38 shouldn't be that bad.</p>
  
  <p>But ... I'm getting lot's of insertions...</p>
  
  <p><a href="https://i.sstatic.net/63m8T.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/63m8T.png" alt="enter image description here"></a></p>
  
  <p>I'm not sure it was caused by the sequencing platform, the MiniMap aligner or my bugs.</p>
  
  <p>I supply all my commands, starting from sample download.</p>
  
  <pre><code>wget https://s3.amazonaws.com/nanopore-human-wgs/rel5-guppy-0.3.0-chunk10k.fastq.gz
  gunzip rel5-guppy-0.3.0-chunk10k.fastq.gz
  wget http://ftp.1000genomes.ebi.ac.uk/vol1/ftp/technical/reference/GRCh38_reference_genome/GRCh38_full_analysis_set_plus_decoy_hla.fa
  minimap2 -d GRCh38_full_analysis_set_plus_decoy_hla.fa.index GRCh38_full_analysis_set_plus_decoy_hla.fa
  minimap2 -ax map-ont -t 20 GRCh38_full_analysis_set_plus_decoy_hla.fa.index rel5-guppy-0.3.0-chunk10k.fastq | samtools view -bS - | samtools sort -@ 5 &gt; rel5-guppy-0.3.0-chunk10k.bam 
  samtools index rel5-guppy-0.3.0-chunk10k.bam
  </code></pre>
  
Tags: <phylogenetics><ngs><nanopore><errors>
Title: Why do I get so many insertions from Minimap2 on my Nanopore WGS?
ThreadText: # Why do I get so many insertions from Minimap2 on my Nanopore WGS?
  
  (Asked by: username_0 on 2019-02-08)
  
  I'm a starting my analysis on nanopore whole genome sequencing. I start my analysis from this popular [Github](https://github.com/nanopore-wgs-consortium/NA12878).
  
  The sample I downloaded was WGS for NA12878, so I would assume it's alignment to GRCh38 shouldn't be that bad.
  
  But ... I'm getting lot's of insertions...
  
  [![enter image description here](https://i.sstatic.net/63m8T.png)](https://i.sstatic.net/63m8T.png)
  
  I'm not sure it was caused by the sequencing platform, the MiniMap aligner or my bugs.
  
  I supply all my commands, starting from sample download.
  
  ```
  wget https://s3.amazonaws.com/nanopore-human-wgs/rel5-guppy-0.3.0-chunk10k.fastq.gz
  gunzip rel5-guppy-0.3.0-chunk10k.fastq.gz
  wget http://ftp.1000genomes.ebi.ac.uk/vol1/ftp/technical/reference/GRCh38_reference_genome/GRCh38_full_analysis_set_plus_decoy_hla.fa
  minimap2 -d GRCh38_full_analysis_set_plus_decoy_hla.fa.index GRCh38_full_analysis_set_plus_decoy_hla.fa
  minimap2 -ax map-ont -t 20 GRCh38_full_analysis_set_plus_decoy_hla.fa.index rel5-guppy-0.3.0-chunk10k.fastq | samtools view -bS - | samtools sort -@ 5 > rel5-guppy-0.3.0-chunk10k.bam 
  samtools index rel5-guppy-0.3.0-chunk10k.bam
  
  ```
  
  **Tags:** phylogenetics, ngs, nanopore, errors
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2019-02-08. Score: 8 | Accepted answer
  
  Insertions and deletions are the dominant error mode of long read sequencing, including nanopore sequencing. What you see is not unexpected. Things may have improved by now if you would download the raw fast5 data and repeat the basecalling. There is no need to `gunzip` the fastq.gz prior to alignment. Your commands for alignment look alright, except that (if you are using a recent version of samtools) you don't really need samtools view and can pipe directly to samtools sort, using -o to specify the output format:
  
  ```
  minimap2 -ax map-ont -t 20 <index> <fastq> | samtools sort -@5 -o alignment.bam 
  
  ```
  
  In a recent version of igv you can right-click the alignment and chose a "Quick consensus mode" (or something like that), which will make your alignments at least a bit prettier. Note how the consensus sequence (top of the graph) is quite clean - while individual reads may be noisy this is mostly randomly distributed and as such ironed out in consensus.
  
  
  ---
  
  