A busy molecular scene can contain more than the structures you are actively working on. When property models are mixed in with other nodes, it can be difficult to narrow a search to the right kind of object—and then tell which of those objects are visible or selected. SAMSON’s Node Specification Language (NSL) offers a direct way to express these checks.
The useful detail is that property models have their own attribute space: propertyModel, shortened to pm. That prefix makes a query specific to property model nodes. For example, pm.v checks the visible attribute for property models, while not pm.v checks the opposite value.
Start with a focused query
If the question is “which property models are visible?”, use pm.v. To look for property models that are not visible, use not pm.v. These short expressions are useful when you want to inspect one aspect of the scene at a time, rather than relying on memory or scanning a long list of nodes.
The same pattern applies to selection. The attribute is called selected, and the documented expressions are pm.selected and not pm.selected. One small but important syntax detail: unlike some other attributes in this space, selected has no short name for property models. Use the full form rather than assuming that the node-level short name s applies here.
Keep similar-looking attributes distinct
The property model attribute list includes both visible and visibilityFlag, as well as hidden. They are separate attributes, each with its own query form: pm.v for visible, pm.vf for visibilityFlag, and pm.h for hidden. The reference lists true and false as possible values for each. Don’t substitute one attribute for another just because their names sound related; choose the one that matches the property you intend to check.
For an explicit flag value, the examples include pm.vf false and pm.sf false. The corresponding attributes are visibilityFlag and selectionFlag. Their short names—vf and sf—make repeated queries compact. The reference also shows the bare forms pm.vf and pm.sf; use the explicit false form when you want to state that value in the expression.
Find a named property model
When you are looking for a particular property model, add a name condition. The attribute is name, abbreviated as n, and its values are written in quotes. The reference examples are pm.n "A" and pm.n "L*". These give you a starting point for expressing a name-based search while keeping the query scoped to property models.
Other inherited attributes can help answer focused questions: pm.hm checks hasMaterial, and pm.om checks ownsMaterial. For either, add not to ask for the opposite value, as shown in the reference’s general Boolean expression pattern.
A practical habit
When a scene feels hard to navigate, first decide what you need to identify: the node type, its name, or a state such as visibility or selection. Then use the matching property model attribute instead of treating similar labels as interchangeable. The pm prefix keeps the search focused; the attribute name makes the question precise. This small habit can make scene inspection more deliberate and reduce the chance of overlooking the property models you meant to examine.
For the full attribute list and additional details, see the property model attributes reference.
Note: SAMSON and all SAMSON Extensions are free for non-commercial use. Get SAMSON.
