When a molecular scene gets busy, a small search mistake can turn into a frustrating cleanup task: the property model you want is hidden among other nodes, has an unexpected name, or is difficult to distinguish from models that are already selected. SAMSON’s Node Specification Language (NSL) provides a focused way to describe property model nodes using their attributes.
This guide is about a practical first step: narrowing a search to property models, then checking their names and display or selection-related attributes. The examples use the propertyModel attribute space, whose short name is pm.
Start by targeting property models
Property model attributes match only property model nodes. That makes pm a useful prefix when your goal is to work with that node type rather than describe nodes more generally. For instance, pm.h refers to the hidden attribute in this attribute space, and pm.v refers to visible.
Using the short prefix consistently also makes expressions easier to scan. The documented long attribute names include hidden, visible, name, and selected; their short forms include h, v, and n. The selected attribute is an exception: it has no short name in the property model attribute space, so write pm.selected.
Use visibility checks to narrow the scene
If you are looking for property models that are currently visible, try pm.v. To describe the opposite condition, use not pm.v. The same pattern works with the hidden attribute: pm.h and not pm.h.
These pairs are useful when you are troubleshooting what appears in a scene. Rather than changing several objects and trying to remember what happened, you can first express the state you want to inspect. For example, a search for not pm.v gives you a way to focus on property models that are not visible; pm.h lets you inspect those marked hidden. The attributes are separately available, so use the one that matches the question you are asking.
Find a model by name
Names are another practical way to reduce a long list of candidates. The name attribute accepts strings in quotes. The documentation shows pm.n "A" and pm.n "L*" as examples. If you recognize a model’s name, a name expression can help focus your search without relying only on its display state.
When using a name expression, keep the quotation marks around the string. If you are unsure of the exact name, the documented "L*" example illustrates a pattern-style string; consult the NSL examples for further guidance on expression syntax rather than assuming that every search tool interprets patterns in the same way.
Check selection-related attributes deliberately
Property models expose both selected and selectionFlag. The page gives examples such as pm.selected, not pm.selected, pm.sf, and pm.sf false. It also lists visibilityFlag, with examples pm.vf and pm.vf false.
These are distinct attribute names in the reference. If your search is about whether a node is selected, use pm.selected; if you specifically need the selection flag, use pm.sf. Likewise, pm.v asks about visibility, while pm.vf asks about the visibility flag. Choosing the attribute that matches your intent helps avoid treating similarly named concepts as interchangeable.
A simple troubleshooting sequence
-
Use the
pmprefix to restrict the expression to property model nodes. -
Check the name with
pm.nand a quoted string if you know what to look for. -
Use
pm.vorpm.hto inspect visibility-related state. -
Use
pm.selected,pm.sf, orpm.vfonly when that specific attribute is relevant.
Property models also inherit attributes such as hasMaterial (hm) and ownsMaterial (om) from the general node attribute space. Their documented examples include pm.hm and pm.om. Keeping the inherited attributes in mind can help when visibility or naming alone does not describe the nodes you need to inspect.
For the complete attribute list and links to the inherited node attributes, see the property model attributes reference.
Note: SAMSON and all SAMSON Extensions are free for non-commercial use. Get SAMSON.
