I was interested in learning where the protein-protein interaction sites were on a particular protein (the receptor). I had pdb files for that protein, and for three proteins that it is known to bind to (the ligands). There are specific amino-acids of interest on the receptor protein, where there is variability among different species. For every combination of receptor and ligand, I want to perform a prediction of where the proteins interact, and then generate an image where the variable amino-acids are highlighted.
Use I-TASSER to generate pdb files for all of the proteins of interest (two isoforms of the receptor, three different ligands). Submit the pdb files to ZDOCK in receptor-ligand pairs (six runs total). Use Chimera scripts to render each combination, highlighting the proper residues in the rendering.
Submitting sequences to I-TASSER and ZDOCK is straightforward. For I-TASSER results, I usually download the tar.bz file, then use 7-zip to extract it. I then typically just use the file called model1.pdb for downstream analyses.
For the ZDOCK submission, I did not select any specific residues to be part of the binding pocket, or excluded from the binding pocket.
To download the ZDOCK results, I just click the four links in the "Download Files" box. An additional file that is of great interest to me is the representation of the the centers of mass of the top 500 docking positions as spheres in space. There isn't a direct link to that file. Instead, you have to enter the url of the file directly into the address bar of your browser. The file itself is called ligcms.pdb. To obtain it, just append that name to the end of the url for your results. For example, one of my results urls was: http://zdock.umassmed.edu/results/88cedc8055/
So to get the file of centers of mass, I used http://zdock.umassmed.edu/results/88cedc8055/ligcms.pdb
Instead of manually highlighting the same residues in every rendering, I'm using a Chimera Python script to do the work for me.
Chimera can be executed from the command line, and given a python script as an argument. For example: chimera myscript.py
Chimera scripting is a little quirky (or I'm just bad at it, probably both). Here are a few quirks I had trouble with:
To change the color of something, you must first get a color object representing the color you want. To get a color object, you must use the convertColor function from the Commands module. For example: red = Commands.convertColor('red')
Amino acid residues in a peptide are zero-indexed, rather than one-indexed as is the convention for biologists. The first amino acid is called amino acid 0, not 1. So when you use the model.findResidue(x) command, be aware that x should be 1 less than the conventional position.
Chimera has some trouble reading the ZDOCK pdb files. Fix that by removing everything after the x y z columns.
There are two distinct syntaxes for executing commands in Chimera Python scripts, one is through the Python API. The other is using command line functions. My impression is that the Python API is more powerful, but it is also exceedingly poorly documented (as far as I can tell). The command line functions are well documented, and can be accessed through Python via the chimera.runCommand function. In the code below, I use a mix of both kinds of commands.
Quick introduction to scripting Chimera. Shows how to open files, and save images.
In chimera the camera does not rotate, it always points in the -z direction. It can pan and zoom and focus, but it cannot rotate. To get the effect of rotating the camera, you must instead rotate all of the models. This can be done using the python interface, or using the command line "turn" function.
An index of all of the commands that can be used through the Chimera command line, or through the chimera.runCommand function in python.