What Am I Looking At? A Practical Guide to SAMSON’s Model Categories

When a molecular scene looks unfamiliar, it is easy to mistake what you see on screen for what the object represents. A surface, for example, may look like the molecule itself—but in SAMSON, its graphical appearance can come from a visual model, while the atoms and bonds belong to a structural model. Knowing the difference helps you choose the right object to inspect, the right tool to apply, and the right kind of model for your next task.

A useful starting point is to ask: Does this object describe the nanosystem, show it, define how it can move, calculate how it interacts, or store another property? These questions map to SAMSON’s five model categories.

1. Structure: what is there?

Structural models describe geometry and topology. They typically contain atoms and bonds, and can include higher-level organization such as molecules, chains, and residues. If you need to reason about the molecular building blocks and how they are connected, start here.

2. Visualization: how is it shown?

Visual models provide graphical representations of structures or data. Examples include a protein’s secondary structure, a Gaussian surface, an electron-density isosurface, or a volumetric view of an electrostatic field. A visual model changes how information is represented on screen; it is not the same thing as the underlying structural model.

This distinction is especially useful when selecting or inspecting objects. Visual models can be applied to selected nodes—or to the whole document when nothing is selected—through the selection’s context toolbar, Visualization > Add > Visual model, or the shortcut Ctrl/Cmd + Shift + V. Some visual models also expose parameters in the Inspector: select the visual model in the Document view, then choose Inspect from its context menu.

Examples of default visual models in SAMSON
Different visual models offer different ways to view molecular information.

Depending on the current selection filter, default visual models can also make it possible to highlight and select atoms, residues, chains, and other elements directly through surfaces.

Highlighting residues on the Solvent Excluded Surface
A surface representation can support selection as well as visualization.

3. Motion: what can change?

Dynamical models indicate where the degrees of freedom are in structural nodes. For example, a particle-system dynamical model applied to atoms assigns three translational degrees of freedom to each atom. Dynamical models describe the dynamical state and store positions, momenta, and masses. If your question is about the system’s motion or state, this is the category to understand.

4. Energies and forces: how do parts interact?

Interaction models represent energies and forces associated with a dynamical model. Examples include Lennard-Jones interactions, spring models, elastic network models, and universal force fields. An interaction model provides forces corresponding to the degrees of freedom; for a particle system, it can provide the total energy and the force on each particle.

5. Other information: what does not fit above?

Property models represent properties outside the first four categories. Examples include a number such as a protein’s gyration radius, a scalar field such as electron density, a vector field such as an electrostatic field, or a function.

One more distinction: state updaters

A state updater is not a sixth model category. It implements methods for advancing states during simulations; examples include minimization algorithms, Monte Carlo methods, and molecular dynamics algorithms. In practical terms, dynamical models describe the state and its degrees of freedom, interaction models provide energies and forces, and state updaters advance the state.

So when an object in the Document view is hard to identify, first separate its scientific role from its visual appearance. Ask what information it represents, then whether it describes structure, depiction, motion, interactions, or another property. That small check can prevent a common modeling mix-up: changing how a system is displayed when what you meant to change was the system’s underlying model—or vice versa.

Explore the SAMSON model reference for more details on each category and how models fit into documents.

Note: SAMSON and all SAMSON Extensions are free for non-commercial use. Get SAMSON.

Comments are closed.