RMF
Mapping data to RMF files

This page outlines how one would go about storing various types of data in RMF files. Much of what it says is merely suggestions, and is not mandatory.

For nodes types, the following node shapes are used

And a dot means an RMF::ALIAS node. The key concept to keep in mind with RMF::ALIAS nodes is that, unlike everything else, they don't introduce a new entity, simply point to one that exists elsewhere. See RMF::ROOT, RMF::REPRESENTATION, RMF::BOND, RMF::ORGANIZATIONAL, RMF::PROVENANCE, RMF::FEATURE for more information.

PDB files

PDB files are most naturally mapped as follows:

All bonds are stored as RMF::BOND nodes with two children for the endpoints of the bond. The bonds are stored as children of the first common ancestor of the endpoints.

If the PDB file has more than one model, all with the same structure, the models should be stored as frames in the RMF file.

Rigid fits of proteins into EM maps or other data

When you have a number of structures that are formed by applying a rigid transform to a set of base structures (eg fitting pdb structures into an EM map), they can be stored as follows:

Multiple structures can be stored as separate frames.

Structures with multiple organization schemes

If the file contains data that has multiple organization schemes, for example, grouping by type of protein, which unit cell etc, several different hierarchies can be provided, all with the same child structures using RMF::ALIAS nodes to provide the different organization schemes.

Symmetries

When there is symmetry, or other repeated unit, define the unit cell in one sub hierarchy and then add RMF::decorator::ReferenceFrame nodes that have that unit cell as a child to define the symmetric parts.