IMP logo
RMF Categories

Categories are divided up by the arity of the entity they are used for (eg whether they are for single nodes, pairs of nodes etc.). The same category name can be used for different arities.

Categories

The following are pre-defined Categories for data stored in single nodes.

Physics

Identifying string: "physics"

Keys:

nametypedescriptioninvariants
cartesian xFloatthe x coordinate in angstrom
cartesian yFloatthe y coordinate in angstromrequired if other cartesian coordinates are included
cartesian zFloatthe z coordinate in angstromrequired if other cartesian coordinates are included
radiusFloatthe radius of the volume occupied by the entity in angstrompositive; requires coordinates
massFloatthe mass of the node in Daltonspositive; requires coordinates
diffusion coefficientFloatthe diffusion coefficient for the node in angstroms per squared femtosecondpositive
orientation rFloatthe real component or the orientation quaterionrequired if there are any orientation components
orientation iFloatthe i component or the orientation quaterionrequired if there are any orientation components
orientation jFloatthe j component or the orientation quaterionrequired if there are any orientation components
orientation kFloatthe k component or the orientation quaterionrequired if there are any orientation components

Related decorators: RMF::Particle, RMF::RigidParticle.

Sequence

Identifying string: "sequence"

Keys:

nametypedescriptioninvariants
first residue indexIntthe first residue index included in this nodeany descendent that has an index must be in the specified range
last residue indexIntthe last residue index included in this nodemust be greater than begin residue index
elementIndexthe atomic number of the elementnodes with elements cannot have children
secondary structureIndex0 for unstructured; 1 for helix; 2 for strandnode must have a residue type
sequenceStringsstore the sequence as a list of three letter codesif the index range is specified then the lengths must match; children with residue types must match
residue typeStringthe three letter code for the residue typethis must match any sequence information higher in the tree and no descendent must have a residue type
chain idIndexstores an integer for the chain identifier. When translating from pdb files the position in the alphabet of the chain should probably be used (eg chain 'A' is 0)
copy indexIndexstores an integer identifying which copy of a moleule this is

Related decorators: RMF::Residue.

Shape

Identifying string: "shape"

Keys:

nametypedescriptioninvariants
cartesian xFloatthe x coordinatemust have y and z or no coordinates fields
cartesian yFloatthe y coordinatemust have x and z or no coordinates fields
cartesian zFloatthe z coordinatemust have x and y or no coordinates fields
cartesian xsFloatsthe x coordinatesthe number must match that of the y and z coordinates
cartesian ysFloatsthe y coordinatesthe number must match that of the x and z coordinates
cartesian zsFloatsthe z coordinatesthe number must match that of the x and y coordinates
radiusFloatthe radiuspositive
rgb color redFloatthe red channel for the colorbetween 0 and 1; must have green and blue
rgb color greenFloatthe green channel for the colorbetween 0 and 1; must have red and blue
rgb color blueFloatthe blue channel for the colorbetween 0 and 1; must have red and green {triangle vertex 0s Indexes, indexes into the coordinates fields to define triangular faces, indexes must be less than the coordinates length; triangle vertex 1s and triangle vertex 2s must be there}
triangle vertex 1sIndexesindexes into the coordinates fields to define triangular facesindexes must be less than the coordinates length; triangles vertex 1 and triangles vertex 2 must be there
triangle vertex 2sIndexesindexes into the coordinates fields to define triangular facesindexes must be less than the coordinates length; triangles vertex 1 and triangles vertex 2 must be there
typeIndex0 for sphere(s); 1 for cylinder(s); 2 for surfaceappropriate attributes must be there; if cylinders or spheres there must be a radius; if cylinder and the coordinates fields are used the size must be divisible by 2

Related decorators: RMF::Ball, RMF::Cylinder.

Feature

Identifying string: "feature"

Keys:

nametypedescriptioninvariants
scoreFloatthe score
representationNodeIDsthe nodes involved in the feature

Related decorators: RMF::Score.

Publication

Identifying string: "publication"

Keys:

nametypedescriptioninvariants
titleStringarticle title
book titleStringthe book title
chapterStringthe book chaptermust have book title
journalStringthe name of the journal
urlStringa url for the publication
pubmed idIntthe pubmed id
yearIntthe year of publication
first pageIndexthe first page number
last pageIndexthe last page number
authorStringsthe author names as a list for "Firstname Lastname"

Related decorators: RMF::JournalArticle.

Pair Categories

The following are categories for storing data on pairs of nodes.

Bond

Identifying string: "bond"

Keys:

nametypedescriptioninvariants
lengthFloatthe length in angstromspositive
typeIndexthe bond type (0 covalent; 1 ionic; 2 hydrogen...)

Decorators

The library provides decorators to aid using the standard types of data. Each decorator comes in a const and a non-const version (as does everything else) and is constructued by an associated factory. It is simpler than this description sounds. See the RMF decorator example.


Generated on Tue May 22 2012 23:33:20 for IMP by doxygen 1.8.1