This protocol has been upgraded to our Kit 14 chemistry and describes how to carry out PCR amplification and native barcoding of influenza amplicons using the Native Barcoding Kit 24 or 96 V14 (SQK-NBD114.24 or SQK-NBD114.96). There are 96 unique barcodes available, allowing the user to pool up to 96 different Influenza A and/or Influenza B samples in one sequencing experiment.

While this protocol is available in the Nanopore Community, we kindly ask users to ensure they are citing the following references, that this protocol is based on.

Single-reaction genomic amplification accelerates sequencing and vaccine production for classical and Swine origin human influenza A viruses by Bin Zhou et al., 2009. and Universal influenza B virus genomic amplification facilitates sequencing, diagnostics, and reverse genetics by Bin Zhou et al., 2014.

Steps in the sequencing workflow:

Prepare for your experiment

You will need to:

• Ensure you have the 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

Prepare your library

You will need to:

• Perform RT-PCR amplification on influenza samples
• Prepare the DNA ends for adapter attachment
• Ligate native barcodes supplied in the kit to the DNA ends
• Ligate sequencing adapters supplied in the kit to the DNA ends
• Prime the flow cell, and load your DNA library into the flow cell

Sequencing

You will need to:

• Start a sequencing run using the MinKNOW software, which will collect raw data from the device and basecall the reads
• Demultiplex barcoded reads in MinKNOW choosing the SQK-NBD114.24 or SQK-NBD114.96 kit option
• Analyse your data using the Influenza typing workflow (wf-flu) in EPI2ME Labs.

A minimum volume of 1 µl is required per sample input of Influenza A or B.

If performing typing of an unknown sample, 2 µl of input will be required:

• 1 µl input for the Influenza A primer mix
• 1 µl for the Influenza B primer mix

This protocol outlines how to carry out PCR amplification and native barcoding of influenza amplicons from multiple samples on a 96-well plate using the Native Barcoding Kit 24 or 96 V14 (SQK-NBD114.24 or SQK-NBD114.96).

When processing multiple samples simultaneously, we recommend making master mixes with an additional 10% of the volume. We also recommend using a template-free pre-PCR hood for making up the master mixes, and a separate template pre-PCR hood for handling the samples. It is important to clean and/or UV irradiate these hoods between sample batches. Furthermore, to track and monitor cross-contamination events, it is important to run a negative control reaction at the reverse transcription stage using nuclease-free water instead of sample, and carrying this control through the rest of the prep.

All post-PCR procedures must be carried out in a separate area to the pre-PCR preparation, with dedicated equipment for liquid handling in each area.

We have validated and recommend the use of all the third-party reagents used in this protocol. Alternatives have not been tested by Oxford Nanopore Technologies.

For all third-party reagents, we recommend following the manufacturer's instructions to prepare the reagents for use.

Influenza A primer sequences described in the protocol originated from: Single-reaction genomic amplification accelerates sequencing and vaccine production for classical and Swine origin human influenza A viruses by Bin Zhou et al., 2009.

Influenza B primer sequences described in the protocol originated from: Universal influenza B virus genomic amplification facilitates sequencing, diagnostics, and reverse genetics by Bin Zhou et al., 2014.

Note: We are in the process of reformatting the barcodes provided in this kit into a plate format. This will reduce plastic waste and will facilitate automated applications.

Plate format

Note: This Product Contains AMPure XP Reagent Manufactured by Beckman Coulter, Inc. and can be stored at -20°C with the kit without detriment to reagent stability.

Note: The DNA Control Sample (DCS) is a 3.6 kb standard amplicon mapping the 3' end of the Lambda genome.

Vial format

Note: This Product Contains AMPure XP Reagent Manufactured by Beckman Coulter, Inc. and can be stored at -20°C with the kit without detriment to reagent stability.

Note: The DNA Control Sample (DCS) is a 3.6 kb standard amplicon mapping the 3' end of the Lambda genome.

Note: We are in the process of updating our kits with reduced EDTA concentration.

Higher EDTA concentration format:

† Higher concentration of EDTA with a clear cap.

Reduced EDTA concentration format:

‡ Reduced concentration of EDTA with a blue cap.

Note: This Product Contains AMPure XP Reagent Manufactured by Beckman Coulter, Inc. and can be stored at -20°C with the kit without detriment to reagent stability.

The barcodes are orientated in columns in the barcode plate.

Note: The DNA Control Sample (DCS) is a 3.6 kb standard amplicon mapping the 3' end of the Lambda genome.

These expansions provide extra library preparation and flow cell priming reagents to allow users to utilise any unused barcodes for those running in smaller subsets.

Both expansion packs used together will provide enough reagents for 12 reactions. For customers requiring extra EDTA to maximise the use of barcodes, we recommend using 0.25 M EDTA and adding 4 µl for library preps using the SQK-NBD114.24 kit and 2 µl for preps using the SQK-NBD114.96 kit.

Native Barcode Auxiliary V14 (EXP-NBA114) contents:

Note: This Product contains AMPure XP Reagent manufactured by Beckman Coulter, Inc. and can be stored at -20°C with the kit without detriment to reagent stability.

Sequencing Auxiliary Vials V14 (EXP-AUX003) contents:

Below is the full list of our native barcode (NB01-96) sequences. The first 24 unique barcodes are available in the Native Barcoding Kit 24 V14 (SQK-NBD114.24). The Native Barcoding Kit 96 V14 (SQK-NBD114.96) include the first 24 native barcodes, with the additional 72 unique barcodes. The native barcodes are shipped at 640 nM.

In addition to the barcodes, there are also flanking sequences which add an extra level of context during analysis.

Barcode flanking sequences:

Forward sequence: 5' - AAGGTTAA - barcode - CAGCACCT - 3' Reverse sequence: 5' - GGTGCTG - barcode - TTAACCTTAGCAAT - 3'

Native barcode sequences

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.

MinKNOW

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.

EPI2ME (optional)

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.

• When handling the primer stocks and derivatives, use a clean template-free PCR hood.
• When handling the samples and/or a positive control, use a clean template-addition PCR hood.

For most sequencing experiments, use the Library Beads (LIB) for loading your library onto the flow cell. However, for viscous libraries it may be difficult to load with the beads and may be appropriate to load using the Library Solution (LIS).

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:

1. Data acquisition and basecalling in real-time using MinKNOW on a computer

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.

2. Data acquisition and basecalling in real-time using the GridION device

Follow the instructions in the GridION user manual.

3. Data acquisition and basecalling in real-time using the MinION Mk1C device

Follow the instructions in the MinION Mk1C user manual.

4. Data acquisition and basecalling in real-time using the PromethION device

Follow the instructions in the PromethION user manual or the PromethION 2 Solo user manual.

5. Data acquisition using MinKNOW on a computer and basecalling at a later time using MinKNOW

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.

The analysis of the FASTQ format sequence data is performed using a Nextflow workflow called Influenza Typing Workflow (wf-flu). The use of the Nextflow software has been integrated into the EPI2ME Labs software that we recommend for running our downstream analysis methods.

Alternative methods for downstream analysis are available using your device terminal or command line, however we only suggest this for experienced users.

The workflow processes the basecalled and demultiplexed DNA sequence data output generated by MinKNOW:

• The sequences are filtered for a minimum length and quality thresholds (200 nucleotides and Q9 respectively) prior to sequence alignment to the CDC multi-fasta Influenza reference.
• The alignment is performed using the Minimap2 software.
• Depth of coverage across the mapped sequences is measured using Samtools before genetic variants are called using Medaka.
• A coverage-masked consensus sequence is prepared for each sample using bcftools.
• The influenza strain typing is then performed using the abricate software with an insaflu database.

The influenza strains included in the database are listed in the project documentation pages for the Influenza Typing Workflow.

The workflow returns a per-run HTML-format summary report along with a CSV file of typing results. Additional files that include mapping BAM files and VCF files of Medaka variants are also included in the workflow output.

For more information, please refer to the Influenza workflow blog.

The EPI2ME application provides a clean interface to accessing bioinformatics workflows, and is our recommended method in performing your post-sequencing analysis.

Follow the instructions in the EPI2ME Installation guide to install the application on your device.

For more information on how to use EPI2ME, refer to the EPI2ME Quick Start guide.

Ensure you have installed the wf-flu workflow prior to the first analysis set-up.

In the EPI2ME Labs home page, scroll down to the "Install workflows" section and click on epi2me-labs/wf-flu:

If you have already installed the wf-flu workflow, ensure you are using the latest version.

Updating the workflow can be done directly through EPI2ME Labs by navigating to the wf-flu workflow page and clicking Update Workflow:

The wf-flu analysis requires FASTQ sequence data that has already been demultiplexed.

Reads will be demultiplexed during sequencing if you are following the recommended "Required settings in MinKNOW". However, demultiplexing can also be done post-sequencing using the MinKNOW software.

For more information and guides on demultiplexing using MinKNOW, refer to the "Post-run analysis" section in our MinKNOW Protocol.

The expected input for wf-flu is a folder of folders as shown below. Each of the barcode folders should contain the FASTQ sequence data and files may either be uncompressed or gzipped.

$ tree -d FluFastq/

FluFastq/

├── barcode01

├── barcode02

├── barcode03

├── barcode04

├── barcode05

├── barcode06

└── unclassified

The wf-flu analysis outputs will be written to the Working Directory folder specified in the EPI2ME Labs Settings tab. The location of this folder is specified in the wf-flu run Instance parameters preceeded by out_dir.

However, these files can also be accessed directly in the EPI2ME Labs application from the completed analysis page for your run:

The "Working Directory" can be specified in the EPI2ME Labs "Settings" tab and defines where the workflow intermediate files and outputs are stored.

This folder will accumulate a significant number of files that correspond to raw BAM files, other larger intermediates and analysis results files. We recommend this folder to be routinely cleared.

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.

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.