🐲
Illumina Infectious Disease Software
Illumina Connected Software
  • 👾Illumina Infectious Disease and Microbiology Software
  • DRAGEN Microbial Amplicon
    • ▶️DRAGEN Microbial Amplicon App Documentation
      • 🌀How to start
      • Page
      • 🧬Custom reference
        • 📄Reference BED file format
        • 📄PCR Primer definition file formats
      • 📂Output files
      • 📖Understanding the BaseSpace Reports
        • 📄Summary
        • 📄Sample Report
      • 💠Pipeline Logic
      • ⭐Special considerations for amplicon detection
      • ❓Frequently Asked Questions (FAQ)
  • DRAGEN Targeted Microbial
    • ▶️DRAGEN Targeted Microbial App Documentation
      • 🌀How to set up and run an analysis
      • 🧬Custom genomes and primer sets
        • 📄Genome definition file formats
        • 📄Primer definition file formats
      • ⚙️App Settings
      • 📖Understanding the BaseSpace Reports
        • 📄Summary Report
        • 📄Result Reports
      • 📂Output files
      • 💠Pipeline Logic
      • ⭐Special considerations for amplicon sequencing with IMAP protocols
      • ❓Frequently Asked Questions (FAQ)
      • 🚩Known issues
  • DRAGEN Microbial Enrichment Plus
    • ▶️DRAGEN Microbial Enrichment Plus App Documentation
      • 🌀How to set up and run an analysis
        • 🧬Custom reference FASTA and BED files
        • 📄Microorganism Reporting File format
      • 📂Output files
        • 📖Understanding the BaseSpace HTML reports
        • 📖Report JSON format
      • 💠Pipeline logic
      • ⭐Test information
        • 📄RPIP
        • 📄UPIP
        • 📄RVOP/RVEK
        • 📄VSP
        • 📄VSP V2
        • 📄Custom Panel
      • 🕵️‍♀️Scientific evidence
      • ❓Frequently Asked Questions (FAQ)
      • 🚩Release notes
Powered by GitBook
On this page
  • If primer coordinates are known (recommended)
  • If primer coordinates are unknown
  • Formatting rules

Was this helpful?

Export as PDF
  1. DRAGEN Microbial Amplicon
  2. DRAGEN Microbial Amplicon App Documentation
  3. Custom reference

PCR Primer definition file formats

If primer coordinates are known (recommended)

Provide a BED file with at least 4 columns: accession, start, end, primerName. Additional columns can be included: pool, strand, sequence, but their order must be maintained.

For example, accession, start, end, primerName, pool for 5-column BED format:

seqX    0           15        primer1_LEFT   1
seqX    1745        1760      primer1_RIGHT  1
seqY    0           15        primer2_LEFT   2
seqY    1015        1030      primer2_RIGHT  2

And accession, start, end, primerName, pool, strand, sequence for 7-column BED format:

seqX    0           15        primer1_LEFT   1     +       GGGCAAACCTAAAGG
seqX    1745        1760      primer1_RIGHT  1     -       GTTATGTAAAGGTGC
seqY    0           15        primer2_LEFT   2     +       GGGCGAAACTAAAGG
seqY    1015        1030      primer2_RIGHT  2     -       GTTATGTAAAGGTGC

If primer coordinates are unknown

Option 1. One line per amplicon with 3 columns: ampliconName, forwardSequence,reverseSequence.

amplicon1      GGGCAAACCTAAAGG  GTTATGTAAAGGTGC
amplicon2      GGGCGAAACTAAAGG  GTTATGTAAAGGTGC

Option 2. One line per primer with 3 columns: primerName, sequence, pool.

primer1_LEFT      GGGCAAACCTAAAGG  1
primer1_LEFT_alt  GGGCGAAACTAAAGG  1
primer1_RIGHT     GTTATGTAAAGGTGC  1

Formatting rules

  • General

    • All text is case sensitive.

    • Any line starting with '#' is ignored. This can be used to add a header line with column names.

    • Every line must have the same number of columns and format (except those starting with '#').

    • Any number of spaces can separate the columns. A value within a single column should not have any space.

  • BED format

    • Per standard BED conventions, sequence coordinates are given as 0-based, half-open intervals, such that the start field (2nd column) contains the first nucleotide in the primer binding site and the last nucleotide in the primer binding site is the value in the end field (3rd column) minus 1.

    • accession field must contain a sequence identifier that matches the header of the FASTA file containing the sequence that the coordinates are relative to.

    • Multiple sequence identifiers (accession) are permitted within one file.

  • Primer name

    • primerName must be unique and encode the name of the amplicon for which the primer is designed, the direction tag indicating which side of the amplicon, left or right, the primer belongs to, and an optional indicator that the primer is an alternative primer for that amplicon.

    • In addition to _LEFT and _RIGHT, we permit _L and _R as direction tags in primerName. Any text after the direction tag should be separated by an underscore.

    • Text in primerName before the direction tag is considered to be an amplicon identifier. Ensure that the text of the amplicon identifier is unique for that amplicon and that the direction tag occurs only once in primerName.

    • Each amplicon must have at least one left and right primer (including alternative primers) associated with it.

    • Alternative primers are used to bind to locations that avoid sequence variation in the default primer binding site that may disrupt hybridization. An amplicon may have an arbitrary number of alternative primers (as long as the primer name is unique), but most amplicons will have none. Alternative primers are indicated by the presence of the _alt after the direction tag in primerName, followed by optional text to distinguish between different alternative primers, such as a number.

    • Examples of valid primer names:

      • MY_SEQUENCE_434_A_LEFT

      • virus1_L

      • amplicon_4934m_RIGHT_alt

      • amplicon_4934m_RIGHT_alt1

      • amplicon_4934m_R_altprimerB

    • Examples of invalid primer names:

      • LEFT_MY_SEQUENCE_434_A

      • virus1_l

      • amplicon_4934m_RIGHT_L

PreviousReference BED file formatNextOutput files

Last updated 5 months ago

Was this helpful?

▶️
🧬
📄