|Home > Iris APIs > Instance registry, instance discovery, and interface discovery API > Hierarchical instance names and instance classes|
Every entity in a simulation is uniquely identified by a hierarchical instance name string. Hierarchy levels are separated by dots.
The first hierarchy level in the string defines the instance class that this instance belongs to. It can be one of the following:
An entity that primarily is controlled and observed, typically:
component. is the name of the top-level component of the component tree, or
root if it has no name. This is followed by the instance names of all components in the hierarchical path up to and including the instance name that is being registered, for example
An entity that primarily observes other instances or controls the simulation. Typically:
FM_PLUGINSenvironment variable, or built-in plug-ins that are statically linked into the simulator executable.
client. is the instance name of the client, which might or might not be hierarchical, for example
An entity that is part of the simulation framework. The following instance names are defined for this instance class: