This page summarizes input and ouput file formats for RNAstructure. Example files can be found in the examples/ directory.
Sequence File Formats:
FASTA and SEQ
Nucleotide Sequences can be provided to RNAstructure in
either FASTA or SEQ format.
In FASTA
files, each nucleotide sequence begins with a single-line description
that must start with the greater-than symbol (>).
Subsequent lines should only contain the sequence itself. The
sequence may be formatted with whitespace, which is ignored,
however blank lines are not allowed in the middle of FASTA input. FASTA
files should have a ".fasta"
extension.
Important notes regarding sequences in RNAstructure:
Sequences are case-sensitive and should generally be in CAPITAL letters. Lowercase letters indicate a base that cannot form basepairs (i.e. is constrained
to be single-stranded/unpaired) in the predicted structure.
For RNA and DNA alphabets, nucleotide sequences can contain U or T interchangably.
These will be interpreted based on the context of the desired operation
(i.e. as U in RNA calculations or as T in DNA calculations).
Whitespace characters (spaces, tabs, and line-breaks) are allowed in sequences (for formatting), and will simply be ignored.
The special letters X and N can be used (interchangably) to represent an unknown base or a base that cannot interact with other bases (i.e. it can neither pair nor stack).
Placing at least three X or N bases next to each other allows them to act like an unstructured loop, which can represent a section of unknown identity or a section that has been purposely left out of the prediction.
SEQ files have the following format:
Comment lines must be at the beginning of the file
and must each start with a semicolon. At least one comment
line is required. Additional comment lines are allowed as
long as each starts with a semicolon.
The title
of the sequence must be provided on a single line immediately following
the comment line(s).
The sequence must start on the line after the title.
It should be entered from 5' to 3' and can include spaces
and line breaks for formatting.
Finally, the sequence must end in "1" (the character representing the number one).
The important notes about sequences in RNAstructure also pertain to SEQ files.
Multi-Sequence FASTA File
Some RNAstructure programs (e.g. TurboFold) can accept a FASTA file
that contains multiple sequences as input.
These are similar to single-sequence FASTA files,
except that additional sequences can be listed, each preceeded
by a title-line starting with ">" (the greater-than symbol). The important notes about sequences in RNAstructure also pertain to multi-sequence FASTA files.
Alignment FASTA File
The AlignmentFold and AlignmentPartition programs require muliple sequence alignments.
CT File Format
A CT (Connectivity Table) file contains secondary
structure information for a sequence. These files are saved with a CT
extension. When entering a structure to calculate the free energy, the
following format must be followed.
Start of first line: number of bases in the sequence
End of first line: title of the structure
Each of the following lines provides information
about a given base in the sequence. Each base has its own line, with
these elements in order:
Base number: index n
Base (A, C, G, T, U, X)
Index n-1
Index n+1
Number of the base to which n is paired. No
pairing is indicated by 0 (zero).
Natural numbering. RNAstructure ignores the
actual value given in natural numbering, so it is easiest to repeat n
here.
The CT file may hold multiple structures for a single
sequence. This is done by repeating the format for each structure
without any blank lines between structures.
The CT file format is such that files generated by RNAstructure are
compatible with mfold/Unafold (available from Michael Zuker), and many
other software packages.
Example File Content:
300 ENERGY = -89.7 bmori in vector
1 G 0 2 22 1
2 G 1 3 21 2
3 G 2 4 20 3
4 C 3 5 19 4
5 G 4 6 0 5
6 A 5 7 0 6
7 A 6 8 0 7
8 U 7 9 18 8
9 U 8 10 17 9
10 G 9 11 16 10
...290 additional lines...
Dot Bracket File Format
Dot bracket files are plain text. They encode a sequence and secondary structure.
Common file extensions are .dot, .bracket, and .dbn
The first line is a title and starts with a ">" character.
The second line contains the sequence.
The third line contains structure information in dot-bracket notation:
The dot/period "." represents an unpaired nucleotide.
An open-parenthesis "(" represents the 5'-nucleotide in a pair, and the matching closing parenthesis ")" represents the 3'-nucleotide in the pair.
Other "bracket"-type symbols can be used to represent basepairs, thereby allowing pseudo-knots to be encoded.
Bracket Characters: ()<>{}
Constraint File Format
Folding constraints are saved in plain text with a CON
extension. These can be hand edited. For multiple entries of a specific
type of constraint, entries are each listed on a separate line. Note
that all specifiers, followed by "-1" or "-1 -1", are expected by
RNAstructure. For all specifiers that take two arguments, it is assumed
that the first argument is the 5' nucleotide. Nucleotides positions are
specified from the 5' end, where the first nucleotide in the sequence
is in position 1.The file format is as follows:
XB: Nucleotides that will be single-stranded
(unpaired)
XC: Nucleotides accessible to chemical modification
XD1, XD2: Forced base pairs
XE: Nucleotides accessible to FMN cleavage (a U that
must be in a GU pair)
XF1, XF2: Prohibited base pairs
Note that all the X* entries in this example text must be integer values (of nucleotide position starting at nucleotide 1 at the 5' end) or removed if a constraint type is absent.
SHAPE Data File Format
The file format for SHAPE reactivity comprises two
columns. The first column is the nucleotide number, and the second is
the reactivity.
Nucleotides for which there is no SHAPE data can either
be left out of the file, or the reactivity can be entered as less than
-500. Columns are separated by any white space.
Note that there is no header information. Nucleotides 1
through 10 have no reactivity information. Nucleotide 11 has a
normalized SHAPE reactivity of 0.042816. Nucleotide 12 has a normalized
SHAPE reactivity of 0, which is NOT the same as having no reactivity
when using the pseudo-energy constraints.
By default, RNAstructure looks for SHAPE data files to
have the file extension SHAPE, but any plain text file can be read.
List File Format
List files have a LIS extension. This file contains any
number of sequences of any length or nucleic acid, each on its own line.
Offset File Format
Offset files are plain text. The files contain two
colums: the nucleotide followed by the offset value in kcal.
Experimental Pair Bonus File
Format
Bonus files are plain text. They are formatted as an nxn
matrix of bonus values, where n is the length of
the sequence.
Alignment File Format
Alignment files are plain text. They are formatted as a
nucleotide in the first sequence immediately followed by the nucleotide
in the second sequence it's aligned to, separated by a space. Only one
alignment pair can be on each line, and the last line of the file must
be "-1 -1".
NMR File Format
NMR file provides experimantal NRM constraints to NAPSS.
FASTA Alignment Format
This is the expected format for sequence alignments used
by Multifind.
Bias File Format for Sequence Design
This is the expected format for specifying a nucleotide and pair biases for the program design. Note that the file assumes that pairs have the same bias regardless of which nucleotide is 5' and which is 3'. Also, Bias-in-Leaf-Refinement can be set to "Yes" or "No". Extended alphabets (those with additional nucleotides beyond A, C, G, U/T must use "Yes".