Differences

This shows you the differences between two versions of the page.

--- minion_sequencing_from_start_to_finish [2017/11/09 10:55] – 129.173.88.84
+++ minion_sequencing_from_start_to_finish [2021/09/06 10:43] (current) – 134.190.232.139
@@ Line 1: / Line 1: @@
 ====== MINION SEQUENCING ======
 {{ :minionheart.jpg?400 |}}
+Documentation by Sarah Shah and Jon Jerlström Hultqvist
 This is a general protocol for monitoring and dealing with a MinION sequencing run.
-**Programs used**: albacore ([[https://github.com/dvera/albacore]]), Porechop ([[https://github.com/rrwick/Porechop]]), ABruijn ([[https://github.com/fenderglass/ABruijn]]), Canu ([[http://canu.readthedocs.io/en/latest/quick-start.html]]), smartdenovo ([[https://github.com/ruanjue/smartdenovo]]), miniasm ([[https://github.com/lh3/miniasm]]), NanoPlot ([[https://github.com/wdecoster/NanoPlot]])
+**Programs used**: albacore ([[https://github.com/dvera/albacore]]), Porechop ([[https://github.com/rrwick/Porechop]]), NanoPlot ([[https://github.com/wdecoster/NanoPlot]])
 Make sure there is enough disk space for the sequencing data to be stored.
@@ Line 9: / Line 12: @@
 Once you've loaded your flow cell and hit execute, keep an eye on the MinKNOW interface. Things you need to look out for:
   * The muxing steps show similar pore availability as when the flow cell was QCed.
-  * The active pore to in-strand pore ratio should preferably be 1:1.
+  * The active pore to in-strand pore ratio should preferably be >0.8.
   * The fragment distribution shows sizes you'd expect to see (if your DNA was fragmented to 8kb, you should see most of your "reads" in this range and some below this size).
   * The biggest amount of data is produced during the first 12 hours. If there isn't much more data generated after that, you might want to RESTART the run. If that doesn't produce more data, STOP the run before it goes to completion (a run is usually completed in 48 hours) and wash the flow cell and store it for later use.
 <code>
-Number of "events" x 1.8 = Number of basepairs
+Number of "events R9.4 flowcell (FLO-MIN106)" x 1.8 = Number of basepairs
+Number of "events R9.5 flowcell (FLO-MIN107)" x 1.5 = Number of basepairs
 </code>
@@ Line 40: / Line 44: @@
 </code>
-The "read_fast5_basecaller.py" line should be repeated for each input folder.
+The "read_fast5_basecaller.py" line should be repeated for each input folder. Add the ** - - barcoding** to demultiplexing barcoded samples.
+If a 1D^2 library has been sequenced (requires the FLO-MIN107 flow cell and the SQK-LSK308 script) has been we should invoke the "full_1dsq_basecaller.py" script to get higher identity "squared reads". To perform squared read-pairing, albacore first performs a regular basecalling and then tries to match matching palindromic reads and infer their consensus. This is at the time of writing (Albacore 2.1.3) a computationally expensive process (6x more intensive than a regular Albacore basecalling). If 1D^2 reads are not desired is also possible to basecall the reads using the standard "read_fast5_basecaller.py" with the kit --SQK-LSK108 flag.
+<code>
+#!/bin/bash
+#$ -S /bin/bash
+. /etc/profile
+#$ -cwd
+#$ -pe threaded 20
+source /scratch2/software/Python-3.6.0/set-path
+full_1dsq_basecaller.py full_1dsq_basecaller.py --input /scratch2/jon/MinION/BMAN/data_2/reads --worker_threads 20 --save_path /scratch2/jon/MinION/BMAN/albacore_basecall_2 --flowcell FLO-MIN107 --kit SQK-LSK308 --recursive --files_per_batch_folder 0 --output_format fastq --reads_per_fastq_batch 9999999999999
+</code>
 After basecalling is done, merge the "pass" fastq files together. This will be the input for the next step.
@@ Line 93: / Line 113: @@
 </code>
+If your fragments sizes are correct and you have a good reads distribution and N50, you're good continue to **[[assembling_long_read_data|ASSEMBLING LONG READ DATA]]**.