Inferensys

Glossary

Dot-Bracket Notation

A standard string representation of RNA secondary structure where matching parentheses denote canonical base pairs and dots represent unpaired nucleotides, used as a training target for deep learning models.
ML engineer managing model training cluster on laptop, GPU utilization visible, technical deep learning setup.
RNA STRUCTURE REPRESENTATION

What is Dot-Bracket Notation?

Dot-bracket notation is the standard string encoding for RNA secondary structure, where matching parentheses denote canonical base pairs and dots represent unpaired nucleotides, serving as a primary training target for deep learning models.

Dot-bracket notation is a one-dimensional string representation that encodes the secondary structure of an RNA molecule. In this format, each character corresponds to a nucleotide in the primary sequence: a ( represents a base paired with a downstream partner, a ) represents a base paired with an upstream partner, and a . denotes an unpaired nucleotide in a loop, bulge, or junction region. The notation captures the nested, non-crossing base pairs that define canonical secondary structure elements such as stems and hairpin loops.

This format serves as the standard output target for secondary structure prediction algorithms, from thermodynamic minimum free energy methods to modern deep learning models like SPOT-RNA and UFold. Because dot-bracket strings are inherently tree-structured and cannot represent pseudoknots (crossing base pairs), extended formats such as WUSS notation or connectivity tables are required for tertiary motifs. The simplicity and direct sequence alignment of dot-bracket notation make it the preferred format for training RNA language models and evaluating prediction accuracy using metrics like F1-score and Matthews correlation coefficient.

RNA Structure Representation

Key Characteristics of Dot-Bracket Notation

Dot-bracket notation is the standard string representation for RNA secondary structure, encoding base-pairing interactions and unpaired regions in a compact, machine-readable format essential for training deep learning models.

01

Core Encoding Rules

The notation uses three characters to represent nucleotide states:

  • . (dot): Unpaired nucleotide (loop, bulge, or dangling end)
  • ( (open): Nucleotide paired with a downstream partner
  • ) (close): Nucleotide paired with an upstream partner

Pairs must be balanced and nested—each opening parenthesis has exactly one matching closing parenthesis at the corresponding position.

02

Training Target for Deep Learning

Dot-bracket strings serve as the ground-truth label for supervised RNA secondary structure prediction models. Neural networks are trained to map raw sequence tokens to per-nucleotide pairing probabilities, with the dot-bracket string as the discrete target.

  • Models like SPOT-RNA and UFold output a dot-bracket prediction
  • Loss functions compare predicted vs. true bracket positions
  • Enables direct benchmarking against thermodynamic methods
03

Limitations: Pseudoknots

Standard dot-bracket notation cannot represent pseudoknots—non-nested base pairs where nucleotides within a loop pair with nucleotides outside that loop.

  • Pseudoknots violate the context-free grammar assumption
  • Extended formats like extended dot-bracket use additional bracket types ([], {}, <>) to encode crossing pairs
  • Models targeting pseudoknot prediction require these richer representations
04

Vienna Format Convention

The widely adopted Vienna format pairs a dot-bracket string with the corresponding RNA sequence and a free energy value:

code
>sequence_name
AUCGAUCG
((....))
(-12.40)

This format is the standard output of tools like RNAfold and mfold, and the expected input for many downstream analysis pipelines.

05

Ensemble Representation

Beyond single structures, dot-bracket notation supports ensemble representations using additional characters:

  • , (comma): Nucleotide unpaired in all suboptimal structures
  • | (pipe): Nucleotide paired but with varying partners
  • { }: Weakly paired regions

These extended characters capture structural ambiguity and are used in partition function outputs.

06

Canonical Base Pairs Only

Standard dot-bracket notation implicitly represents only canonical Watson-Crick (A-U, G-C) and wobble (G-U) base pairs. Non-canonical interactions—such as Hoogsteen pairs, A-minor motifs, or base triples—are not captured.

  • Requires complementary annotation formats like Leontis-Westhof classification for full 3D interaction mapping
  • Limits the notation's utility for tertiary structure description
RNA STRUCTURE REPRESENTATION

Frequently Asked Questions

Common questions about dot-bracket notation, the standard string representation for RNA secondary structure used as training targets in deep learning models.

Dot-bracket notation is a one-dimensional string representation of RNA secondary structure where matching parentheses ( and ) denote canonical base pairs, and dots . represent unpaired nucleotides. The notation captures the nested topology of base-pairing interactions along the linear RNA sequence. For example, the string (((...))) represents a simple stem-loop: three consecutive base pairs forming a helix, followed by three unpaired loop nucleotides, closed by three complementary base pairs. Each opening parenthesis at position i must have a corresponding closing parenthesis at position j, indicating that nucleotide i pairs with nucleotide j. This format is the standard output of minimum free energy (MFE) prediction algorithms and serves as the primary training target for deep learning models like SPOT-RNA and UFold that predict RNA secondary structure directly from sequence.

REPRESENTATION COMPARISON

Dot-Bracket vs. Other Structure Representations

Comparison of RNA secondary structure representation formats used as training targets or outputs for deep learning models.

FeatureDot-Bracket NotationAdjacency MatrixContact Map

Data Structure

1D string

2D binary matrix

2D distance/heatmap matrix

Human Readability

Encodes Pseudoknots

Memory Complexity

O(N)

O(N²)

O(N²)

Standard for MFE Algorithms

Native Loss Function Compatibility

Cross-entropy (per-position)

Binary cross-entropy

MSE or MAE

Used in AlphaFold 3 Training

Encodes Base Pair Type

Prasad Kumkar

About the author

Prasad Kumkar

CEO & MD, Inference Systems

Prasad Kumkar is the CEO & MD of Inference Systems and writes about AI systems architecture, LLM infrastructure, model serving, evaluation, and production deployment. Over 5+ years, he has worked across computer vision models, L5 autonomous vehicle systems, and LLM research, with a focus on taking complex AI ideas into real-world engineering systems.

His work and writing cover AI systems, large language models, AI agents, multimodal systems, autonomous systems, inference optimization, RAG, evaluation, and production AI engineering.