Version for device: MinION
Overview of the protocol
This kit is available on the Legacy page of the store. We are in the process of gathering data to support the upgrade of this protocol to our latest chemistry. Further information regarding protocol upgrades will be provided on the Community as soon as they are available over the next few months. For further information on please see the product update page.
This protocol is based on the No part gets left behind: Tiled nanopore sequencing of whole ASFV genomes stitched together using Lilo by Amanda Warr et al., 2021.
These kits are recommended for users who:
This protocol describes an efficient, low-cost method to sequence ASFV at scale. The method uses tiled PCR amplification of the virus to obtain good coverage, while enabling sample multiplexing to reduce run costs.
The kits used are the Native Barcoding Expansion 1-12 (EXP-NBD104) and 13-24 (EXP-NBD114), in conjunction with the Ligation Sequencing Kit (SQK-LSK109). There are 24 unique barcodes if using both expansion kits, allowing the user to pool up to 24 different samples in one sequencing experiment. It is highly recommended that a Lambda control experiment is completed first to become familiar with the technology.
Steps in the sequencing workflow:
Prepare for your experiment
You will need to:
Prepare your library
You will need to:
Sequencing
You will need to:
This protocol should only be used in combination with:
For customers new to nanopore sequencing, we recommend buying the NEBNext® Companion Module for Oxford Nanopore Technologies® Ligation Sequencing (catalogue number E7180S or E7180L), which contains all the NEB reagents needed for use with the Ligation Sequencing Kit.
Please note, for our amplicon protocols, NEBNext FFPE DNA Repair Mix and NEBNext FFPE DNA Repair Buffer are not required.
Name | Acronym | Cap colour | No. of vials | Fill volume per vial (µl) |
---|---|---|---|---|
DNA CS | DCS | Yellow | 1 | 50 |
Adapter Mix | AMX | Green | 1 | 40 |
Ligation Buffer | LNB | Clear | 1 | 200 |
L Fragment Buffer | LFB | White cap, orange stripe on label | 2 | 1,800 |
S Fragment Buffer | SFB | Grey | 2 | 1,800 |
Sequencing Buffer | SQB | Red | 2 | 300 |
Elution Buffer | EB | Black | 1 | 200 |
Loading Beads | LB | Pink | 1 | 360 |
Name | Acronym | Cap colour | No. of vial | Fill volume per vial (μl) |
---|---|---|---|---|
Flush Buffer | FB | Blue | 6 | 1,170 |
Flush Tether | FLT | Purple | 1 | 200 |
EXP-NBD104 kit contents
Name | Acronym | Cap colour | No. of vials | Fill volume per vial (μl) |
---|---|---|---|---|
Native Barcode 01-12 | NB01-12 | White | 12 | 20 |
Adapter Mix II | AMII | Green | 1 | 40 |
EXP-NBD114 kit contents
Name | Acronym | Cap colour | No. of vials | Fill volume per vial (μl) |
---|---|---|---|---|
Native Barcode 13-24 | NB13-24 | White | 12 | 20 |
Adapter Mix II | AMII | Green | 1 | 40 |
The native barcode sequences are the reverse complement of the corresponding barcode sequence in other kits. 24 unique barcodes are available in the Native Barcoding Expansion 1-12 and 13-24 (EXP-NBD104 and EXP-NBD114).
Native Barcoding Expansion 1-12 and 13-24 (EXP-NBD104 and EXP-NBD114)
Component | Forward sequence | Reverse sequence |
---|---|---|
NB01 | CACAAAGACACCGACAACTTTCTT | AAGAAAGTTGTCGGTGTCTTTGTG |
NB02 | ACAGACGACTACAAACGGAATCGA | TCGATTCCGTTTGTAGTCGTCTGT |
NB03 | CCTGGTAACTGGGACACAAGACTC | GAGTCTTGTGTCCCAGTTACCAGG |
NB04 | TAGGGAAACACGATAGAATCCGAA | TTCGGATTCTATCGTGTTTCCCTA |
NB05 | AAGGTTACACAAACCCTGGACAAG | CTTGTCCAGGGTTTGTGTAACCTT |
NB06 | GACTACTTTCTGCCTTTGCGAGAA | TTCTCGCAAAGGCAGAAAGTAGTC |
NB07 | AAGGATTCATTCCCACGGTAACAC | GTGTTACCGTGGGAATGAATCCTT |
NB08 | ACGTAACTTGGTTTGTTCCCTGAA | TTCAGGGAACAAACCAAGTTACGT |
NB09 | AACCAAGACTCGCTGTGCCTAGTT | AACTAGGCACAGCGAGTCTTGGTT |
NB10 | GAGAGGACAAAGGTTTCAACGCTT | AAGCGTTGAAACCTTTGTCCTCTC |
NB11 | TCCATTCCCTCCGATAGATGAAAC | GTTTCATCTATCGGAGGGAATGGA |
NB12 | TCCGATTCTGCTTCTTTCTACCTG | CAGGTAGAAAGAAGCAGAATCGGA |
NB13 | AGAACGACTTCCATACTCGTGTGA | TCACACGAGTATGGAAGTCGTTCT |
NB14 | AACGAGTCTCTTGGGACCCATAGA | TCTATGGGTCCCAAGAGACTCGTT |
NB15 | AGGTCTACCTCGCTAACACCACTG | CAGTGGTGTTAGCGAGGTAGACCT |
NB16 | CGTCAACTGACAGTGGTTCGTACT | AGTACGAACCACTGTCAGTTGACG |
NB17 | ACCCTCCAGGAAAGTACCTCTGAT | ATCAGAGGTACTTTCCTGGAGGGT |
NB18 | CCAAACCCAACAACCTAGATAGGC | GCCTATCTAGGTTGTTGGGTTTGG |
NB19 | GTTCCTCGTGCAGTGTCAAGAGAT | ATCTCTTGACACTGCACGAGGAAC |
NB20 | TTGCGTCCTGTTACGAGAACTCAT | ATGAGTTCTCGTAACAGGACGCAA |
NB21 | GAGCCTCTCATTGTCCGTTCTCTA | TAGAGAACGGACAATGAGAGGCTC |
NB22 | ACCACTGCCATGTATCAAAGTACG | CGTACTTTGATACATGGCAGTGGT |
NB23 | CTTACTACCCAGTGAACCTCCTCG | CGAGGAGGTTCACTGGGTAGTAAG |
NB24 | GCATAGTTCTGCATGATGGGTTAG | CTAACCCATCATGCAGAACTATGC |
ASFV primer sequences described in the protocol are subject to change. Any updates can be found at ASFV Lilo GitHub page.
Amplicon - primer pair | Forward sequence | Reverse sequence |
---|---|---|
ASFV1 | GGCGTTCATTTCACAAGATGC | ACGGCATCTAAGCAGCTCAATG |
ASFV2 | CAGGCCGATATATCATTTCATCAATATTCA | ACCCAAAGCCCTGGAATCCTTA |
ASFV3 | GCAAACCAAGTGACTCACCCTC | ATTGTATGACGTCGGGGCAGAT |
ASFV4 | ACCTAGTAAAAGTCCTAGAAAAACCTTCA | CGCCATTGTTTTACACAGTCGC |
ASFV5 | TCGAGATTTTATTATTTGGATGCATCATCA | GGACTGATGAAAGCCGTGAA |
ASFV6 | TCCACGCGGTACTTGGCTCC | AGGCCTCGTTGGTGGAAAGGA |
ASFV7 | AGGGCTGATGCAAATCTCTTTTTCA | TCTCCGATTTTCGCATGCCAAA |
ASFV8 | AGTTTGCAAAGAGCCTAAAGATAGACT | AGCGTGGAACTGTAGATGACGA |
ASFV9 | TGCAGAAACCGCAGATGAATGT | ATAGGATTAGATGCGACGCCCA |
ASFV10 | GCATGTAGAGAGGTTTTGGTAGTCA | GGAAACAGCTGGAGAGTTGTGG |
ASFV11 | TGGTTTTGAAATAAAATGCCTTCTACGG | GGAATGCATGGACGAAGAAGCA |
ASFV11 (alt) | CTATGGGATGGGAAGAGTGGTCAA | CGTCAACCGCCGCATTAGC |
ASFV12 | TCCTTGGGAGTTACAGCGAAGA | AATGAAATCATTCGCGGCGAGT |
ASFV13 | CAGACATTGGCAGTGATGGCTA | GAAATGCCGGGCCTTCTACAAA |
ASFV14 | GCTACTCCCCCAAATATCACATATAATTGT | TTTTTCGTGTTGCTGTTCGGGA |
ASFV15 | GGATGGCACCCTTCTCACAATC | TGCGTATGACCCGATGTTGTTG |
ASFV16 | GTCGACTTCACAGGAACAACGG | ACCCGCTTTACACAAAACACGT |
ASFV17 | TGGAATTTCCTGACGTGGCAAA | GCAACCGCTATTCCAAACAGGA |
ASFV18 | AGTTGTTGTCCTAGACCGTGGCA | TGAAAAGGAGGGCACGATCC |
ASFV19 | CCCGTATGCGGGCGTACTTT | TGGCCTCTTCTTTCCCCCGA |
ASFV20 | GGCCGCAACATTTGTGTCAAAG | GCTCGCGAACAAATTACTCCCA |
ASFV21 | GAATGGCAGCGATGATCTCAGG | TGCAGGGCAAGGGTATACTGAA |
ASFV22 | TGGCGTCGTTTAACAGCTTGAT | GCTGGATGGCAAATCGGTTGTA |
ASFV23 | AGGCGTGAAAATTCTTCTTCAAACA | AGACGTTTTAAGCTGCATGGCA |
ASFV24 | GGCAGCAGGATCTTAAAACCGG | TGCATAATGCCCAGCTTTTCGT |
ASFV25 | GCTGTTTAAGCGTTTCAAGCTGA | CTCCGCGGGGAACATTGTTTTA |
ASFV26 | CCCTGGGAGGAGTCATCATGAA | GGTCATTGACTTTGGAAGCGCT |
ASFV27 | ACTGTCTGCTAGACTCCCAGGA | CCCAAGAGGAGGAATGGTTTGC |
ASFV28 | GCCCCCTAGCGTCACCGAAT | CCAAGCCTGCTGCGAAGCTC |
ASFV29 | GACGCAATTTCGGCTGTTTTTAAAA | GACTTGGTCTCCGGCTCAAAAG |
ASFV30 | GTTGGGGTGTTGGAGCGAATAA | TTCTGCTTACGGACGATGCAAC |
ASFV31 | TAGTTGTGAAGCGTTCTCGGGT | GAGCACATGTTACTCGCCACTC |
ASFV32 | GGACTTCTTATGCTCAGATGGGC | ACTGCTGCAGGCGTTAAACATT |
Computer requirements and software
Sequencing on a MinION Mk1B requires a high-spec computer or laptop to keep up with the rate of data acquisition. Read more in the MinION Mk1B IT Requirements document.
The MinION Mk1C contains fully-integrated compute and screen, removing the need for any accessories to generate and analyse nanopore data. Read more in the MinION Mk1C IT requirements document.
The MinKNOW software controls the nanopore sequencing device, collects sequencing data and basecalls in real time. You will be using MinKNOW for every sequencing experiment to sequence, basecall and demultiplex if your samples were barcoded.
For instructions on how to run the MinKNOW software, please refer to the MinKNOW protocol.
The EPI2ME cloud-based platform performs further analysis of basecalled data, for example alignment to the Lambda genome, barcoding, or taxonomic classification. You will use the EPI2ME platform only if you would like further analysis of your data post-basecalling.
For instructions on how to create an EPI2ME account and install the EPI2ME Desktop Agent, please refer to the EPI2ME Platform protocol.
We highly recommend that you check the number of pores in your flow cell prior to starting a sequencing experiment. This should be done within 12 weeks of purchasing for MinION/GridION/PromethION or within four weeks of purchasing Flongle Flow Cells. Oxford Nanopore Technologies will replace any flow cell with fewer than the number of pores in the table below, when the result is reported within two days of performing the flow cell check, and when the storage recommendations have been followed. To do the flow cell check, please follow the instructions in the Flow Cell Check document.
Flow cell | Minimum number of active pores covered by warranty |
---|---|
Flongle Flow Cell | 50 |
MinION/GridION Flow Cell | 800 |
PromethION Flow Cell | 5000 |
DNA extraction
Tiled DNA amplification and clean-up
Odd primer pool:
Primer pair | Concentration |
---|---|
3 | 0.75X |
5 | 2X |
7 | 1X |
9 | 1X |
11 | 1X |
11 alt | 1X |
13 | 1X |
15 | 1X |
17 | 1.5X |
19 | 1X |
21 | 1X |
23 | 1X |
25 | 2X |
27 | 1X |
29 | 1X |
31 | 0.5X |
Even primer pool:
Primer pair | Concentration |
---|---|
2 | 1X |
4 | 2X |
6 | 0.5X |
8 | 1.5X |
10 | 2X |
12 | 2X |
14 | 2.5X |
16 | 1X |
18 | 1.5X |
20 | 1X |
22 | 1.5X |
24 | 1.5X |
26 | 1.5X |
28 | 0.75X |
30 | 1.5X |
32 | 1X |
Primer one:
Primer number | Concentration |
---|---|
1 | 1X |
Note: Due to the proximity to the telomeric sequence, primer 1 has a shorter amplicon length. The primer does not perform optimally in when pooled with others, therefore it is prepared separately.
Note: For each sample you will have three reactions – odd primer pool, even primer pool, and primer 1 pool.
Between each addition, pipette mix 10-20 times.
Reagent | Volume |
---|---|
Nuclease-free water | 9 µl |
ASFV DNA (1:10 dilution) | 2 µl |
Primer pool (1:10 dilution) | 1.5 µl |
VeriFi HS Mix (PCRBIO) | 12.5 µl |
Total | 25 µl |
Note: we recommend to make a PCR master mix, either for individual primer pools for multiple samples or one for the three primers sets.
Step | Temperature | Time | Cycles |
---|---|---|---|
Initial denaturation | 98°C | 1 min | 1 |
Denaturation Annealing Extension |
98°C 60°C 72°C |
15 sec 15 sec 4 min 40 sec |
40 |
Final extension | 72°C | 5 min | 1 |
Hold | 10°C | ∞ |
Note: At this point you should still have three tubes for each DNA sample.
Primer pool | Proportion |
---|---|
Pool 1 | 48% |
Pool 2 | 50% |
Amplicon 1 | 2% |
DNA repair and end-prep
For optimal performance, NEB recommend the following:
Thaw all reagents on ice.
Flick and/or invert the reagent tubes to ensure they are well mixed.
Note: Do not vortex the FFPE DNA Repair Mix or Ultra II End Prep Enzyme Mix.
Always spin down tubes before opening for the first time each day.
The Ultra II End Prep Buffer and FFPE DNA Repair Buffer may have a little precipitate. Allow the mixture to come to room temperature and pipette the buffer up and down several times to break up the precipitate, followed by vortexing the tube for 30 seconds to solubilise any precipitate.
Note: It is important the buffers are mixed well by vortexing.
The FFPE DNA Repair Buffer may have a yellow tinge and is fine to use if yellow.
Between each addition, pipette mix 10-20 times
Reagent | Volume |
---|---|
DNA | 48 µl |
NEBNext FFPE DNA Repair Buffer | 3.5 µl |
Ultra II End-prep reaction buffer | 3.5 µl |
Ultra II End-prep enzyme mix | 3 µl |
NEBNext FFPE DNA Repair Mix | 2 µl |
Total | 60 µl |
Reagent | Volume |
---|---|
500 ng end-prepped DNA | 22.5 µl |
Native Barcode | 2.5 µl |
Blunt/TA Ligase Master Mix | 25 µl |
Total | 50 µl |
Dispose of the pelleted beads
Adapter ligation and clean-up
Protocols that use the Native Barcoding Expansions require 5 μl of AMII per reaction. Native Barcoding Expansions EXP-NBD104/NBD114 contain sufficient AMII for 6 reactions (or 12 reactions when sequencing on Flongle). This assumes that all barcodes are used in one sequencing run.
The Adapter Mix II expansion provides additional AMII for customers who are running subsets of barcodes, and allows a further 12 reactions (24 on Flongle).
Reagent | Volume |
---|---|
700 ng pooled barcoded sample | 65 µl |
Adapter Mix II (AMII) | 5 µl |
NEBNext Quick Ligation Reaction Buffer (5X) | 20 µl |
Quick T4 DNA Ligase | 10 µl |
Total | 100 µl |
Dispose of the pelleted beads
We recommend storing libraries in Eppendorf DNA LoBind tubes at 4°C for short term storage or repeated use, for example, reloading flow cells between washes.
For single use and long-term storage of more than 3 months, we recommend storing libraries at -80°C in Eppendorf DNA LoBind tubes.
For further information, please refer to the DNA library stability Know-How document.
Additional buffer for doing this can be found in the Sequencing Auxiliary Vials expansion (EXP-AUX001), available to purchase separately. This expansion also contains additional vials of Sequencing Buffer (SQB) and Loading Beads (LB), required for loading the libraries onto flow cells.
Priming and loading the SpotON flow cell
We recommend all new users watch the 'Priming and loading your flow cell' video before your first run.
Press down firmly on the flow cell to ensure correct thermal and electrical contact.
This step can be omitted if the flow cell has been checked previously.
See the flow cell check instructions in the MinKNOW protocol for more information.
Note: Visually check that there is continuous buffer from the priming port across the sensor array.
Demo of how to use the Loading Beads.
Reagent | Volume per flow cell |
---|---|
Sequencing Buffer (SQB) | 37.5 µl |
Loading Beads (LB), mixed immediately before use | 25.5 µl |
DNA library | 12 µl |
Total | 75 µl |
Note: Load the library onto the flow cell immediately after adding the Sequencing Buffer (SQB) and Loading Beads (LB) because the fuel in the buffer will start to be consumed by the adapter.
We recommend leaving the light shield on the flow cell when library is loaded, including during any washing and reloading steps. The shield can be removed when the library has been removed from the flow cell.
Carefully place the leading edge of the light shield against the clip.
Note: Do not force the light shield underneath the clip.
Gently lower the light shield onto the flow cell. The light shield should sit around the SpotON cover, covering the entire top section of the flow cell.
Data acquisition and basecalling
For a full overview of nanopore data analysis, which includes options for basecalling and post-basecalling analysis, please refer to the Data Analysis document.
The sequencing device control, data acquisition and real-time basecalling are carried out by the MinKNOW software. Please ensure MinKNOW is installed on your computer or device. There are multiple options for how to carry out sequencing:
Follow the instructions in the MinKNOW protocol beginning from the "Starting a sequencing run" section until the end of the "Completing a MinKNOW run" section.
Follow the instructions in the GridION user manual.
Follow the instructions in the MinION Mk1C user manual.
Follow the instructions in the PromethION user manual or the PromethION 2 Solo user manual.
Follow the instructions in the MinKNOW protocol beginning from the "Starting a sequencing run" section until the end of the "Completing a MinKNOW run" section. When setting your experiment parameters, set the Basecalling tab to OFF. After the sequencing experiment has completed, follow the instructions in the Post-run analysis section of the MinKNOW protocol.
Downstream analysis
Note: Information subject to change, please refer to No part gets left behind: Tiled nanopore sequencing of whole ASFV genomes stitched together using Lilo by Amanda Warr et al., 2021 for most recent updates.
The shotgun sequencing data were basecalled and demultiplexed using MinKNOW (v19.06.8) using Fast basecalling.
Following basecalling the reads were aligned to an ASFV genome using minimap2 to identify ASFV reads, the .fast5 files for these reads were extracted using fast5_subset from the ont_fast5_api and these again using high accuracy basecalling (this reduces basecalling time, suitable for when working with lower spec laptops/computers that have low GPU capacity).
The reads were assembled with Flye (v2.6) - additional Flye resources available following the link: Assembly of long, error-prone reads using repeat graphs and polished three times with Medaka (v0.7.1).
Comparisons of quantity of data produced and the proportion of which were ASFV reads were done using NanoComp (v1.28.1) - additional Nanopack resources available following the link: NanoPack: visualizing and processing long-read sequencing data.
The data were basecalled and demultiplexed using Guppy (v5.0.14) using high or super accuracy model on a GPU.
The snakemake pipeline Lilo was used, taking the following steps:
The required input to Lilo are demultiplexed reads in FASTQ format in a directory named “raw/”, a reference FASTA, a .bed file of primer alignments (as output by primal scheme), and a .csv of primer sequences (if there are ambiguous bases it is advised to expand them first) and a config file, described on the GitHub page. It is adaptable to any species (with a single genome fragment/chromosome) with any tiled primer scheme. The pipeline outputs a FASTA file containing the assembled genome.
A subset of genomes were also assembled using the ARTIC pipeline (v1.2.1) following the bioinformatics SOP using the Medaka method.
Quast (v5.0.2) was used to compare the assembled genomes to the most closely related publicly available ASFV assembly according to BLAST alignment (MN715134.1) - links and additional resources available following the link: Short and Long-Read Sequencing Survey of the Dynamic Transcriptomes of African Swine Fever Virus and the Host Cells.
Samples where both WGS and tiled sequencing were used were compared for overall structure using nucmer (v4.0.0beta2) - links and aditional reources available following the link: MUMmer4: A fast and versatile genome alignment system.
The phylogeny analysis was limited to the tiled genomes, as these were the most accurate assemblies, and publicly available genomes. These were aligned using Mafft (v7.467) and maximum likelihood trees constructed using iqtree (v2.0.5).
Flow cell reuse and returns
The Flow Cell Wash Kit protocol is available on the Nanopore Community.
Instructions for returning flow cells can be found here.
Note: All flow cells must be flushed with deionised water before returning the product.
Issues during DNA extraction and library preparation
We also have an FAQ section available on the Nanopore Community Support section.
If you have tried our suggested solutions and the issue still persists, please contact Technical Support via email (support@nanoporetech.com) or via LiveChat in the Nanopore Community.
Observation | Possible cause | Comments and actions |
---|---|---|
Low DNA purity (Nanodrop reading for DNA OD 260/280 is <1.8 and OD 260/230 is <2.0–2.2) | The DNA extraction method does not provide the required purity | The effects of contaminants are shown in the Contaminants document. Please try an alternative extraction method that does not result in contaminant carryover. Consider performing an additional SPRI clean-up step. |
Low RNA integrity (RNA integrity number <9.5 RIN, or the rRNA band is shown as a smear on the gel) | The RNA degraded during extraction | Try a different RNA extraction method. For more info on RIN, please see the RNA Integrity Number document. Further information can be found in the DNA/RNA Handling page. |
RNA has a shorter than expected fragment length | The RNA degraded during extraction | Try a different RNA extraction method. For more info on RIN, please see the RNA Integrity Number document. Further information can be found in the DNA/RNA Handling page. We recommend working in an RNase-free environment, and to keep your lab equipment RNase-free when working with RNA. |
Observation | Possible cause | Comments and actions |
---|---|---|
Low output from PCR | Insufficient primer | Increase the amount of primer pool in the PCR reaction by 0.25-1 µl, decrease water proportionally. |
- | Insufficient DNA template | Use undiluted DNA. |
- | Thermocycler fault | Ensure that you use a thermocycler that has been recently calibrated. |
- | Insufficient viral DNA and an abundance of host DNA | Use a host depletion method such as NEBNext® Microbiome DNA Enrichment Kit before PCR*. |
- | Low representation of a particular primer in the sequencing data | Spike in a small quantity of the primer in the 100 µM pool before future runs |
* This may be prohibitively expensive at scale, but for precious samples this will have a noticeable impact on amplicon yield.
Observation | Possible cause | Comments and actions |
---|---|---|
Low recovery | DNA loss due to a lower than intended AMPure beads-to-sample ratio | 1. AMPure beads settle quickly, so ensure they are well resuspended before adding them to the sample. 2. When the AMPure beads-to-sample ratio is lower than 0.4:1, DNA fragments of any size will be lost during the clean-up. |
Low recovery | DNA fragments are shorter than expected | The lower the AMPure beads-to-sample ratio, the more stringent the selection against short fragments. Please always determine the input DNA length on an agarose gel (or other gel electrophoresis methods) and then calculate the appropriate amount of AMPure beads to use. |
Low recovery after end-prep | The wash step used ethanol <70% | DNA will be eluted from the beads when using ethanol <70%. Make sure to use the correct percentage. |
Issues during the sequencing run
We also have an FAQ section available on the Nanopore Community Support section.
If you have tried our suggested solutions and the issue still persists, please contact Technical Support via email (support@nanoporetech.com) or via LiveChat in the Nanopore Community.
Observation | Possible cause | Comments and actions |
---|---|---|
MinKNOW reported a lower number of pores at the start of sequencing than the number reported by the Flow Cell Check | An air bubble was introduced into the nanopore array | After the Flow Cell Check it is essential to remove any air bubbles near the priming port before priming the flow cell. If not removed, the air bubble can travel to the nanopore array and irreversibly damage the nanopores that have been exposed to air. The best practice to prevent this from happening is demonstrated in this video. |
MinKNOW reported a lower number of pores at the start of sequencing than the number reported by the Flow Cell Check | The flow cell is not correctly inserted into the device | Stop the sequencing run, remove the flow cell from the sequencing device and insert it again, checking that the flow cell is firmly seated in the device and that it has reached the target temperature. If applicable, try a different position on the device (GridION/PromethION). |
MinKNOW reported a lower number of pores at the start of sequencing than the number reported by the Flow Cell Check | Contaminations in the library damaged or blocked the pores | The pore count during the Flow Cell Check is performed using the QC DNA molecules present in the flow cell storage buffer. At the start of sequencing, the library itself is used to estimate the number of active pores. Because of this, variability of about 10% in the number of pores is expected. A significantly lower pore count reported at the start of sequencing can be due to contaminants in the library that have damaged the membranes or blocked the pores. Alternative DNA/RNA extraction or purification methods may be needed to improve the purity of the input material. The effects of contaminants are shown in the Contaminants Know-how piece. Please try an alternative extraction method that does not result in contaminant carryover. |
Observation | Possible cause | Comments and actions |
---|---|---|
MinKNOW shows "Script failed" | Restart the computer and then restart MinKNOW. If the issue persists, please collect the MinKNOW log files and contact Technical Support. If you do not have another sequencing device available, we recommend storing the flow cell and the loaded library at 4°C and contact Technical Support for further storage guidance. |
Observation | Possible cause | Comments and actions |
---|---|---|
Pore occupancy <40% | Not enough library was loaded on the flow cell | Ensure you load the recommended amount of good quality library in the relevant library prep protocol onto your flow cell. Please quantify the library before loading and calculate mols using tools like the Promega Biomath Calculator, choosing "dsDNA: µg to pmol" |
Pore occupancy close to 0 | The Ligation Sequencing Kit was used, and sequencing adapters did not ligate to the DNA | Make sure to use the NEBNext Quick Ligation Module (E6056) and Oxford Nanopore Technologies Ligation Buffer (LNB, provided in the sequencing kit) at the sequencing adapter ligation step, and use the correct amount of each reagent. A Lambda control library can be prepared to test the integrity of the third-party reagents. |
Pore occupancy close to 0 | The Ligation Sequencing Kit was used, and ethanol was used instead of LFB or SFB at the wash step after sequencing adapter ligation | Ethanol can denature the motor protein on the sequencing adapters. Make sure the LFB or SFB buffer was used after ligation of sequencing adapters. |
Pore occupancy close to 0 | No tether on the flow cell | Tethers are adding during flow cell priming (FLT/FCT tube). Make sure FLT/FCT was added to FB/FCF before priming. |
Observation | Possible cause | Comments and actions |
---|---|---|
Shorter than expected read length | Unwanted fragmentation of DNA sample | Read length reflects input DNA fragment length. Input DNA can be fragmented during extraction and library prep. 1. Please review the Extraction Methods in the Nanopore Community for best practice for extraction. 2. Visualise the input DNA fragment length distribution on an agarose gel before proceeding to the library prep. In the image above, Sample 1 is of high molecular weight, whereas Sample 2 has been fragmented. 3. During library prep, avoid pipetting and vortexing when mixing reagents. Flicking or inverting the tube is sufficient. |
Observation | Possible cause | Comments and actions |
---|---|---|
Large proportion of unavailable pores (shown as blue in the channels panel and pore activity plot) The pore activity plot above shows an increasing proportion of "unavailable" pores over time. |
Contaminants are present in the sample | Some contaminants can be cleared from the pores by the unblocking function built into MinKNOW. If this is successful, the pore status will change to "sequencing pore". If the portion of unavailable pores stays large or increases: 1. A nuclease flush using the Flow Cell Wash Kit (EXP-WSH004) can be performed, or 2. Run several cycles of PCR to try and dilute any contaminants that may be causing problems. |
Observation | Possible cause | Comments and actions |
---|---|---|
Large proportion of inactive/unavailable pores (shown as light blue in the channels panel and pore activity plot. Pores or membranes are irreversibly damaged) | Air bubbles have been introduced into the flow cell | Air bubbles introduced through flow cell priming and library loading can irreversibly damage the pores. Watch the Priming and loading your flow cell video for best practice |
Large proportion of inactive/unavailable pores | Certain compounds co-purified with DNA | Known compounds, include polysaccharides, typically associate with plant genomic DNA. 1. Please refer to the Plant leaf DNA extraction method. 2. Clean-up using the QIAGEN PowerClean Pro kit. 3. Perform a whole genome amplification with the original gDNA sample using the QIAGEN REPLI-g kit. |
Large proportion of inactive/unavailable pores | Contaminants are present in the sample | The effects of contaminants are shown in the Contaminants Know-how piece. Please try an alternative extraction method that does not result in contaminant carryover. |
Observation | Possible cause | Comments and actions |
---|---|---|
Reduction in sequencing speed and q-score later into the run | For Kit 9 chemistry (e.g. SQK-LSK109), fast fuel consumption is typically seen when the flow cell is overloaded with library (please see the appropriate protocol for your DNA library to see the recommendation). | Add more fuel to the flow cell by following the instructions in the MinKNOW protocol. In future experiments, load lower amounts of library to the flow cell. |
Observation | Possible cause | Comments and actions |
---|---|---|
Temperature fluctuation | The flow cell has lost contact with the device | Check that there is a heat pad covering the metal plate on the back of the flow cell. Re-insert the flow cell and press it down to make sure the connector pins are firmly in contact with the device. If the problem persists, please contact Technical Services. |
Observation | Possible cause | Comments and actions |
---|---|---|
MinKNOW shows "Failed to reach target temperature" | The instrument was placed in a location that is colder than normal room temperature, or a location with poor ventilation (which leads to the flow cells overheating) | MinKNOW has a default timeframe for the flow cell to reach the target temperature. Once the timeframe is exceeded, an error message will appear and the sequencing experiment will continue. However, sequencing at an incorrect temperature may lead to a decrease in throughput and lower q-scores. Please adjust the location of the sequencing device to ensure that it is placed at room temperature with good ventilation, then re-start the process in MinKNOW. Please refer to this FAQ for more information on MinION temperature control. |
Observation | Possible cause | Comments and actions |
---|---|---|
No input .fast5 was found or basecalled | input_path did not point to the .fast5 file location | The --input_path has to be followed by the full file path to the .fast5 files to be basecalled, and the location has to be accessible either locally or remotely through SSH. |
No input .fast5 was found or basecalled | The .fast5 files were in a subfolder at the input_path location | To allow Guppy to look into subfolders, add the --recursive flag to the command |
Observation | Possible cause | Comments and actions |
---|---|---|
No Pass or Fail folders were generated after basecalling | The --qscore_filtering flag was not included in the command | The --qscore_filtering flag enables filtering of reads into Pass and Fail folders inside the output folder, based on their strand q-score. When performing live basecalling in MinKNOW, a q-score of 7 (corresponding to a basecall accuracy of ~80%) is used to separate reads into Pass and Fail folders. |
Observation | Possible cause | Comments and actions |
---|---|---|
Unusually slow processing on a GPU computer | The --device flag wasn't included in the command | The --device flag specifies a GPU device to use for accelerate basecalling. If not included in the command, GPU will not be used. GPUs are counted from zero. An example is --device cuda:0 cuda:1, when 2 GPUs are specified to use by the Guppy command. |
Purchase a MinION Starter Pack from Avantor to get full community access and benefit from:
Already have a Nanopore Community account?
Log in hereRequest a call with our experts for detailed advice on implementing nanopore sequencing.
Request a callVisit our microbial sequencing spotlight page on vwr.com.
Microbial sequencingWe use cookies and similar technologies on our websites to help provide you with the best possible online experience.
By using our sites and apps, you agree that we may store and access cookies and similar technologies on your device.