This is a list of some of the less commonly asked questions about Rosetta.
In truth this is a grab-bag for short bits of documentation which have not (yet) found a home elsewhere.
RosettaDesign identifies low energy sequences for specified protein backbones, and has been used previously to stabilize proteins and create new protein structures. Please visit our RosettaDesign server: http://rosettadesign.med.unc.edu
RosettaDock predicts the structure of a protein-protein complex from the individual structures of the monomer components. See http://rosie.rosettacommons.org/docking/ for the current server.
RosettaNMR combines the Rosetta de novo structure prediction method with limited experimental data from NMR for rapid prediction of protein structure. NMR constraints of RDC and NOE have been used successfully in RosettaNMR to determine global folds.
RosettaLigand employs the full atom modes of Rosetta to predict the interactions of protein-small molecule interactions.
You can find an optional package named BioTools in the software download page. The createTemplate.pl is in this package.
Rosetta uses "REUs" for its energy unit. (See Units in Rosetta.) As such, the temerature is also in arbitrary units.
pNNMAKE.gnu is not a pre-existed file. You need generate it after you download the rosetta_fragments package. After entering the rosetta_fragment/nnmake directory, type "make" to compile and the pNNMAKE file will be generated.
Coordinates for all fragments are precalculated in the vall_cst_coord.dat.* file. The fields in this file are:
1 frag source pdb name 2 frag source chain 3 frag source residue 5-7 HN coords (x,y,z) 8-10 HA coords 11-21 coefficients for evaluating RDC restraints 22-24 N coords 25-27 CA coords 28-30 CB coords 31-33 C coords 34-36 O coords
All fragments in fragment libraries are identified by the frag source pdb name, chain and residues, allowing relevant coordinates to be extracted from the vall_coord_cst.dat.* data file.
For speed, the Packer uses an "Interaction Graph" to cache the residue interaction energies. (See packing-options for command line options to control the packer.) Depending on the protocol you're using, maintaining this interaction graph can account for a considerable amount of time and memory. As such, different interaction graphs (IG) are available.
-linmem_ig) reduces both the memory and runtime over the default interaction graph
-lazy_ig) is in all cases faster than the Linear Memory Interaction Graph, but at the cost of more memory usage.
-double_lazy_ig) is only useful for multistate design.
No. The FastRelax algorithm relies on the stochastic behavior of the packer to get adequate sampling of the conformational space. The Multicool annealer (the
-multi_cool_annealer option) is too convergent, and does not give enough variability in results for a good relax results.