A crowded molecular scene can make a simple task surprisingly difficult: finding the property model you want to inspect without confusing it with other nodes. Node Specification Language (NSL) gives you a way to describe property model nodes by attributes such as visibility, selection, and name. That makes it easier to narrow your attention to the right kind of node before you continue working.
The key is the propertyModel attribute space, abbreviated pm. It matches only property model nodes. For example, pm.v selects property models whose visible attribute is true, while not pm.v matches those whose visible attribute is false. These are useful starting points when you need to distinguish property models that are currently visible from ones that are not.
Start with visibility
When the scene feels cluttered, try checking the visible and non-visible groups separately:
pm.v— property models withvisibleset to true.not pm.v— property models withvisibleset to false.
These expressions describe which nodes match; they do not, by themselves, mean “show” or “hide.” That distinction is useful: a search or specification can help you identify a group without assuming that the query itself changes the scene.
The page also lists visibilityFlag, with the short name vf. Its documented examples are pm.vf and pm.vf false. Since visible and visibilityFlag are separate attributes in the reference, keep their names distinct when writing a specification. The reference lists both, but does not define their relationship, so avoid treating one as a synonym for the other.
Use names to narrow the search
If visibility alone leaves too many candidates, use the inherited name attribute. The property-model examples include pm.n "A" and pm.n "L*". The first is a quoted name expression; the second shows a name pattern. This gives you a practical two-step approach: first identify whether the models you are interested in are visible, then use their names to focus on a particular candidate or naming pattern.
NSL also includes attributes for selection state. For example, pm.selected and not pm.selected match selected and unselected property models. One easy-to-miss detail: selected has no short name in this attribute space. Use pm.selected, rather than guessing a shortened form. By contrast, selectionFlag does have the short name sf, and the documented examples are pm.sf and pm.sf false.
A small checklist for reliable specifications
- Begin with
pmso the specification targets property model nodes. - Use
pm.vornot pm.vto check the visible state. - Add a name expression such as
pm.n "A"when the model’s name is known. - Keep similarly named attributes separate:
visibleis not the same attribute asvisibilityFlag, andselectedis not the same attribute asselectionFlag.
These small details can make a crowded scene easier to reason about: first identify the relevant property model nodes, then continue with the task you intended to perform. For the complete attribute list and additional inherited attributes, see the property model attributes reference.
Note: SAMSON and all SAMSON Extensions are free for non-commercial use. Get SAMSON.
