This code allows build-up of three-dimensional de novo models of RNAs of sizes up to ~300 nts, given secondary structure and experimental constraints. It can be carried out reasonably automatically, but human curation of submodels along the build-up path may improve accuracy. A fully automated pipeline is in preparation (a previous iteration of this is described in rna assembly documentation).
Here's a movie of models created through iterative application of this modeling workflow on the lariat-capping GIR1 ribozyme, as part of a blind prediction trials (RNA puzzle 5):
This documentation page emphasizes the setup of multiple jobs that together permit the modeling of complex RNA folds. Each of the 'sub-jobs' is either a helix creation, a RNA comparative modeling job rna_thread, or a run with the FARFAR (fragment assembly of RNA with full-atom refinement) de novo modeling application. If desired, sub-models can be grafted together into bigger pieces.
The input files, algorithm, etc. for the FARFAR application are described separately here, but a detailed understanding of those file formats is not necessary for modeling.
This method has been developed to allow integrative modeling of complex RNA folds for which some parts can be modeled by homology and others by de novo modeling. It still relies on constraints for long-range contacts like pseudoknots as may be available from phylogenetic analysis or multidimensional chemical mapping approaches like MOHCA-seq or mutate-and-map.
The method is not yet a single automated pipeline.
The main wrapper code is available through installation of RNA tools.
The RNA puzzles have offered useful testbeds of helix modeling, motif homology modeling, de novo modeling, and grafting to larger RNA structures. Examples of all four steps are available in:
Examples of blind predictions carried out with this pipeline, including the one in the movie above, are in:
Some recent manuscripts that describe this workflow in detail are:
Cheng, C.Y., Chou, F.-C., Kladwang, W., Tian, S., Cordero, P., and Das, R. (2015) "Consistent global structures of complex RNA states through multidimensional chemical mapping." eLife 4 : e07600. Paper. Link.
You need two input files to run structure modeling of complex RNA folds:
Following are examples for a sequence drawn from RNA puzzle 11, a long hairpin with several submotifs. The fasta file
RNAPZ11.fasta looked like this:
>RNAPZ11 A:1-57 gggaucugucaccccauugaucgccuucgggcugaucuggcuggcuaggcggguccc
and the secondary structure file
RNAPZ11.secstruct for the whole problem looked like this:
There are four helices, H1, H2, H3, and H4.
Helices act as connectors between motifs. It can be useful to pre-build these and keep them fixed during each motif run, as grafting (Step 4 below) requires superimposition between shared pieces of separately built motifs.
A sample command line is the following:
rna_helix.py -o H2.pdb -seq cc gg -resnum 14-15 39-40
This application output the helix with chains A and B, but removing the chains prevents some confusion with later steps, so you can run:
replace_chain_inplace.py H2.pdb A
To setup the above python scripts, follow the directions for setting up RNA tools. Example files and output are in:
In the problem above, there is a piece which is a well-recognized motif, the UUCG apical loop.
Let's model it by threading from an exemplar of the motif from the crystallographic database. There is one here:
Download 1f7y.pdb from
Slice out the motif of interest:
pdbslice.py 1f7y.pdb -subset B:31-38 uucg_
Thread it into our actual sequence:
rna_thread -s uucg_1f7y.pdb -seq ccuucggg -o uucg_1f7y_thread.pdb
Let's get the numbering to match our actual test case:
renumber_pdb_in_place.py uucg_1f7y_thread.pdb 24-31
Example files and output are in:
To build motifs or several motifs together, we will use de novo Rosetta modeling. In this example, we'll model the motifs between H2 and H4, using our starting H2 and H4 helices as fixed boundary conditions. Note that a more advanced method, stepwise modeling is also available for high resolution modeling (and is actually easier to run the fragment assembly), but remains mostly untested in the context of buildup of large RNA complex folds; for motifs that have any kind of homology to existing junctions/motifs, FARFAR should be better & faster.
Fragment assembly of RNA with full atom refinement (FARFAR) has been equipped to map numbers from our full modeling problem into subproblems, as defined by the
rna_denovo.<exe> -fasta RNAPZ11.fasta \ -secstruct_file RNAPZ11_OPEN.secstruct \ -working_res A:14-25 A:30-40 \ -s H2.pdb H4.pdb \ -fixed_stems \ -tag H2H3H4_run1b_openH3_SOLUTION1 \ -native example1.pdb
You don't need to supply a native if you don't have it -- just useful to compute RMSDs as a reference.
[Historical note: there is also a script
rna_denovo_setup.py which was used to set up input files for
rna_denovo before it could handle residue mapping. You may see it called in older Rosetta RNA modeling workflows.]
Example output after a couple of structures goes to
For convergent results, you may have to do a full cluster run -- some tools are available for
slurm queueing systems as part of rna tools.
Extract 10 lowest energy models:
extract_lowenergy_decoys.py H2H3H4_run1b_openH3_SOLUTION1.out 10
Inspect in Pymol, using, e.g., the commands available in RiboVis. (For an automated workflow, you can also cluster these runs and just carry forward the top 5 clusters.)
Demo files are available in:
Some useful options for
Required: -sequence sequence supplied directly [string] OR -fasta Fasta-formatted sequence file -- but concatenate all RNA chains in one sequence! Commonly used options -secstruct secondary structure in dot-parentheses notation (enclose in quotes) OR -secstruct_file file containint secondary structure on top line (can have sequence or anything else on later lines) -offset integer specifying how much to add to each sequence position to get conventional numbering (default: 0) -cutpoint_open positions of any strand breaks -working_res which residues to model in the desired sub-problem (example: '122-135 166-190', default is all res.) -fixed_stems set up de novo modeling fold tree so that helices are connected by rigid-body transforms (default:false, but now recommended) -s list of PDB files to use; must have residue numbers corresponding to location in full modeling problem (default: no input files) Less commonly used options, but useful -nstruct number of structures for each FARFAR denovo modeling run to produce (default: 500) -tag string to put in front of all input files and final output file (default: name of working directory) -native_pdb file with reference PDB for RMSD values (optional) Advanced options -out_script name of output script with Rosetta command line (default: "README_FARFAR") -silent any *input* Rosetta silent files with multiple options for a subset of residues -input_silent_res residue numbers that go with the silent files -no_minimize do not carry out full-atom refinement, just fragment assembly under lo res score function. -working_native_pdb supply a reference PDB file that has just working_res only. -cst_file constraint file in old 'section-based' Rosetta constraint format -data_file data file with, e.g., DMS data in 'DMS position value' format, or in RDAT format. -cutpoint_closed specify that transient chain breaks occur at specific positions, rather than chosen randomly at loops -extra_minimize_res positions that may be in input residues (specified in -s or -silent) but should be minimized -extra_minimize_chi_res positions that may be in input residues (specified in -s or -silent) but side-chains should be minimized -virtual_anchor poorly named; creates a virtual anchor necessary for rigid-body sampling of separate parts of the pose -obligate_pair specify pairs of positions that must be in base pairs (perhaps at the expense of transient chain breaks elsewhere) -obligate_pair_explicit like obligate pair, but specify sets of 5: <pos1> <pos2> <W/H/S> <W/H/S> <A/P>, where W/H/S means Watson-Crick/Hoogsteen/sugar edge; and A/P means antiparallel/parallel base normals. -chain_connection specify that pairings must occur between two sets of residues: SET1 <positions in set 1> SET2 <positions in set 2>
Once you have several models of sub pieces, they can be combined in two ways.
One option is to run further FARFAR jobs (rerun Step 3), but supplying solutions to sub-pdbs via
-s <pdb1> <pdb2> ... into larger modeling jobs. This is particularly powerful if a set of jobs can be set up in which each new job builds an additional peripheral element or junction into a well-converged model of a sub-set modeled in a previous job – a stepwise buildup, analogous to what is being explored in high-resolution stepwise modeling.
Alternatively, you can quickly graft two PDBs based on superimposition of shared residues, either using the
align command in Pymol, or with the following Rosetta command lines:
Demo files are available in:
rna_graft -s H2H3H4_run1b_openH3_SOLUTION1.pdb uucg_1f7y_thread.pdb H1H2_run2_SOLUTION1.pdb -o full_graft.pdb