Symexp
Symexp is used to reconstruct neighboring asymmetric units from the crystallographic experiment that produced the given structure. This is assuming the use of a PDB file or equivalent that contains enough information (CRYST1 record) to reproduce the lattice.
Symexp creates all symmetry related objects for the specified object that occurs within a cutoff about an atom selection. The new objects are labeled using the prefix provided along with their crystallographic symmetry operation and translation.
USAGE
# Expand the ''object'' around its ''selection'' by cutoff Angstroms and
# prefix the new objects withs ''prefix''.
symexp prefix, object, selection[, cutoff]
For one protein:
symexp name_for_new_objects,asymmetric_name,(asymmetric_name),distance
name_for_new_objects (prefix)
- PyMOL will generate a number of new objects corresponding to copies (rotated and translated) of the given asymmetric unit with the given name (prefix) appended with a numerical counter
asymmetric_name (object)
- This is the name of the loaded asymmetric unit that you wish to reproduce neighboring crystal partners for; the source of the symmetry operators
(asymmetric_name)
- (selection) - the same name, but with parentheses around it if you are reproducing a crystal from its asymmetric unit - the source of atom coordinates
distance
- (cutoff) - in Angstroms; reproduce any other unit that has any part of it falling withing distance Angstroms from the original asymmetric unit
EXAMPLE
load any .pdb file into PyMOL (here we use 1GVF).
At the PyMOL command prompt type the following:
symexp sym,1GVF,(1GVF),1
produces three new objects. We now have four objects corresponding to two biologic units (the functional protein in a cell).
symexp sym,1GVF,(1GVF),5
If we color all of the sym* cyan we will produce the following:
As you can see, we can begin to understand the crystal environment of our asymmetric unit. Increasing distance will reveal more of the crystal lattice, but will place in increasing demand on your computer's rendering ability.
PyMOL is known to exit dramatically (crash) if you provide a scene that is too large or complex. This is a result of the low-level malloc function failing. See Category:Performance for workarounds.
See Also
- PDB Symmetry Info
- SuperSym
- From within PyMOL, help symexp and symexp ?.