The scripts and input files that accompany this demo can be found in the
demos/protocol_captures directory of the Rosetta weekly releases.
This is a protocol capture, and represents the protocol at a fixed point in time. It may not work with the current version of Rosetta.
KEYWORDS: DESIGN PEPTIDES
Vikram K. Mulligan, Ph.D. (firstname.lastname@example.org) Baker laboratory Institute for Protein Design University of Washington
This is the protocol capture for a protocol used to design large (60-residue) peptides with C3 symmetry, cross-linked with a threefold-symmetric cross-linking agent (1,3,5-tris(bromomethyl)benzene, or TBMB). A manuscript describing this work is in preparation, a joint effort between the Baker and DeGrado laboratories.
This protocol uses RosettaScripts to design a peptide in a single script. The steps in the design process are as follows:
The design.xml file included in the xml/ sub-directory contains extensive comments describing each Rosetta module used and why it was invoked. Note that this has been modified slightly from the original file, insofar as it samples a much smaller number of samples very close to a known designable region of Crick parameter space. This is to allow the demo to run in a reasonable amount of time.
(A) Overall design workflow. The script included here fully describes this workflow. (B) An example of a designed C3-symmetric 60-mer cross-linked with TBMB (orange), with hydrophobic core residues shown in grey. (C) Ab initio energy landscape of the peptide shown in B. Points from ab initio are shown in orange and points from relaxation of the design structure are shown in blue. Note that Rosetta's ab initio algorithm can neither model the cyclic geometry nor the cross-linker, so this is a deceptively shallow folding funnel.
All commandline flags needed are included in xml/rosetta.flags. To run this script, one therefore uses the following command:
$> $ROSETTA3/bin/rosetta_scripts.default.linuxgccrelease @xml/rosetta.flags
Note that, in the above, the string "default.linuxgccrelease" may need to be modified for your build type, operating system, and compiler. For example, for a static build using the Clang compiler on a Mac, the executable's name would be rosetta_scripts.static.macosclangrelease.
The RosettaScripts executable may be compiled with support for parallelization using the Message Passing Interface (MPI). This allows multiple RosettaScripts trajectories to be split over many processors, and in this case, this allows the sampling of Crick parameter space during the first step to be divided over many processors. In order to run with MPI-based parallelization, after compiling with MPI support, one simply types:
$> mpirun -np <number_of_processes> $ROSETTA3/bin/rosetta_scripts.mpi.linuxgccrelease @xml/rosetta.flags
This is particularly recommended for this design protocol, since many hundreds of thousands of parameter value combinations must be sampled, which is best done in parallel.
This script was implemented with, and has been tested with, Rosetta 3.8 on 1 March 2017. The GIT sha was 99781a84f0b6fa3adb1bf8ecaf1abe9fb248088f.