Patrick Weinkam
Ben Webb
Ursula Pieper
Elina Tjioe
Andrej Sali
Version main.c726385
Protein glycosylation can be modeled as explained in this help page and in our paper
(Guttman et al. 2013 Structure).
For help to model non-glycosylated proteins, click here.
This tool is meant to sample the range of conformations accessible to sugars. There are a few ways to run the server
depending on the desired conformational flexibility of the protein and/or sugars:
1) Input: a protein without sugars. Output: a semi-rigid protein (motions will be limited to loops and surface side chains) with flexible sugars.
2) Input: a protein with sugars. Output: a flexible protein with rigid sugars.
3) Input: a protein without sugars. Output: a flexible protein with flexible sugars.
For option 1, input the protein sequence only and a file describing sugar connectivity (glyc.dat). See below for more information and for an example
click here. For option 2, run option 1 and then use a single
structure from the output as input for another run. In the input sequence, specify the protein sequence and a "." for each sugar. The "."
specifies a block residue in MODELLER and will remain rigid. Such rigid bodies can cause problems during dynamics so care should be given here.
You will also need to upload a file allosmod.py that was generated in option 1. For option 3, first run
simulations of the protein only using AllosMod. Then
take the resulting structures and do option 1 (one for each structure) using AllosMod. This can be best achieved using the batch mode (see below).
Take all the glycosylated protein structures as input into the FoXS server, if desired.
HINTS:
The following help page is organized to run batch jobs. Each input field in single landscape mode has a corresponding file/section below.
Upload a zip file containing a set of directories for each glycosylated protein that you want to model. For an example directory, click here. Each directory should contain the following files:
PDB file(s): the template structures used to model the protein.
Alignment file: (align.ali) contains one entry for each PDB file. Another entry (named pm.pdb) pertains to the sequence to be modeled.
This alignment file should be generated after an alignment procedure, as this alignment will be used to generate restraints for modeling.
Multiple chains can be specified by using a "/" as a separator, the same specifications
used in MODELLER. There are many ways to create an alignment file including: 1) MODELLER
and 2) ClustalW.
***WARNING*** Small errors in the alignment can cause big errors during a simulation due to energy conservation problems.
Make sure there are no misalignments in which adjacent residues are aligned far apart in sequence (alignment programs often do this at the beginning
or end of chains).
Structure list: (list) contains all PDB files used as template structures.
Input file: (input.dat) contains one line per parameter as follows:
NRUNS = X
The output is a zip file containing the same directories that were uploaded with subdirectories containing glycosylated structures named pm.pdb.B99990001.pdb.