Version for device: MinION
This kit is soon to be discontinued and we recommend all customers to upgrade to the latest chemistry for their relevant kit which is available on the Store. If customers require further support for any ongoing critical experiments using a Legacy product, please contact Customer Support via email: support@nanoporetech.com. For further information on please see the product update page.
This kit is highly recommended for users who:
This protocol describes how to carry out a Direct RNA Sequencing Control Experiment using the Direct RNA Sequencing Kit (SQK-RNA002). The Control Experiment can be used to try out nanopore sequencing technology using stock RNA supplied in the kit, before preparing your own library.
Steps in the sequencing workflow:
Prepare for your experiment
You will need to:
- Ensure you have your sequencing kit, the correct equipment and third-party reagents
- Download the software for acquiring and analysing your data
- Check your flow cell to ensure it has enough pores for a good sequencing run
Library preparation
You will need to:
- Synthesise the complementary strand of the RNA
- Attach sequencing adapters supplied in the kit to the ends of the RNA-cDNA hybrid
- Prime the flow cell, and load your RNA library into the flow cell
Sequencing
You will need to:
- Start a sequencing run using the MinKNOW software, selecting "SQK-RNA002 - control experiment" in kit selection.
Note: When using the control experiment kit, run length will automatically be reduced to 6 hours.
- Start the EPI2ME software and select a workflow to align the reads to the RNA control strand
This protocol should only be used in combination with:
Name | Acronym | Cap colour | No. of vials | Fill volume per vial (μl) |
---|---|---|---|---|
RT Adapter | RTA | Blue | 1 | 10 |
RNA Adapter Mix | RMX | Green | 1 | 45 |
RNA Calibrant Strand | RCS | Yellow | 1 | 25 |
Wash Buffer | WSB | Orange | 2 | 1,200 |
Elution Buffer | ELB | Black | 1 | 300 |
RNA Running Buffer | RRB | Red | 1 | 600 |
Note: The RNA CS (RCS) is the calibration strand and contains the Enolase II from YHR174W, extracted from the yeast saccharomyces cerevisiae. The reference FASTA files for the yeast is available here.
Name | Acronym | Cap colour | No. of vials | Fill volume per vial (μl) |
---|---|---|---|---|
Flush Buffer | FB | Blue | 6 | 1,170 |
Flush Tether | FLT | Purple | 1 | 200 |
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 |
Reagent | Volume |
---|---|
NEBNext Quick Ligation Reaction Buffer | 3.0 µl |
RNA CS (RCS), 110 nM | 9.5 µl |
RT Adapter (RTA) | 1.0 µl |
T4 DNA Ligase | 1.5 µl |
Total | 15 µl |
Reagent | Volume |
---|---|
Nuclease-free water | 9.0 µl |
10 mM dNTPs | 2.0 µl |
5x first-strand buffer | 8.0 µl |
0.1 M DTT | 4.0 µl |
Total | 23.0 µl |
Reagent | Volume |
---|---|
NEBNext Quick Ligation Reaction Buffer | 8.0 µl |
RNA Adapter (RMX) | 6.0 µl |
Nuclease-free water | 3.0 µl |
T4 DNA Ligase | 3.0 µl |
Total (including all reagents) | 40 µl |
If you have omitted the reverse transcription step, please use the Qubit RNA HS Assay Kit instead. However, please note that the kit will measure all RNA present, including any non-adapted RNA that has been carried through in the RNAClean XP bead clean-up. The reported quantity of RNA may therefore not fully represent the amount of sequenceable RNA.
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.
Reagent | Volume per flow cell |
---|---|
RNA Running Buffer (RRB) | 37.5 µl |
RNA library in nuclease-free water | 37.5 µl |
Total | 75 µl |
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
Once you have loaded your flow cell, the sequencing run can be started on MinKNOW, our sequencing software that controls the device, data acquisition and real-time basecalling. For more detailed information on setting up and using MinKNOW, please see the MinKNOW protocol.
MinKNOW can be used and set up to sequence in multiple ways:
For more information on using MinKNOW on a sequencing device, please see the device user manuals:
To start a sequencing run on MinKNOW:
1. Navigate to the start page and click Start sequencing.
2. Fill in your experiment details, such as name and flow cell position and sample ID.
3. Select the sequencing kit used in the library preparation on the Kit page.
4. Configure the sequencing and output parameters for your sequencing run or keep to the default settings on the Run configuration tab.
Note: If basecalling was turned off when a sequencing run was set up, basecalling can be performed post-run on MinKNOW. For more information, please see the MinKNOW protocol.
5. Click Start to initiate the sequencing run.
After sequencing has completed on MinKNOW, the flow cell can be reused or returned, as outlined in the Flow cell reuse and returns section.
After sequencing and basecalling, the data can be analysed. For further information about options for basecalling and post-basecalling analysis, please refer to the Data Analysis document.
In the Downstream analysis section, we outline further options for analysing your data.
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.
Downstream analysis
There are several options for further analysing your basecalled data:
For in-depth data analysis, Oxford Nanopore Technologies offers a range of bioinformatics tutorials and workflows available in EPI2ME. The platform provides a vehicle where workflows deposited in GitHub by our Research and Applications teams can be showcased with descriptive texts, functional bioinformatics code and example data.
Oxford Nanopore Technologies' Research division has created a number of analysis tools, which are available in the Oxford Nanopore GitHub repository. The tools are aimed at advanced users, and contain instructions for how to install and run the software. They are provided as-is, with minimal support.
If a data analysis method for your research question is not provided in any of the resources above, please refer to the resource centre and search for bioinformatics tools for your application. Numerous members of the Nanopore Community have developed their own tools and pipelines for analysing nanopore sequencing data, most of which are available on GitHub. Please be aware that these tools are not supported by Oxford Nanopore Technologies, and are not guaranteed to be compatible with the latest chemistry/software configuration.
Issues during DNA/RNA 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 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.