Write geometry to a python file for Chimera to read.
The writer writes a python file which can handle markers, edges and surfaces. Since these are native chimera objects, they are handled a bit better than vrml ones.
This format creates one file per frame. So if you want to use frames and save them all, make sure there is a "%1%" in the file name string passed to the constructor.
Examples: chain, display log, cube, show spheres, connectivity
Inheritance diagram for IMP::display::ChimeraWriter:Public Member Functions | |
| ChimeraWriter (base::TextOutput of) | |
| ChimeraWriter (const char *name) | |
| ChimeraWriter (std::string name) | |
Static Public Member Functions | |
| static ChimeraWriter * | get_from (IMP::base::Object *o) |
Protected Member Functions | |
| void | add_python_code (std::string code) |
| Add some arbitrary python code to the chimera file. | |
| void IMP::display::ChimeraWriter::add_python_code | ( | std::string | code | ) | [protected] |
Add some arbitrary python code to the chimera file.
You should import the bits of Chimera that you need. At the moment, you should not name a variable surf_sets or marker_sets.