44. Operational Modes¶

SolarNode supports a concept called operational modes. Modes are simple names like quiet and hyper that can be either active or inactive. Any number of modes can be active at a given time. In theory both quiet and hyper could be active simultaneously. Modes can be named anything you like.

Modes can be used by SolarNode components to alter their behavior dynamically. For example a data source component might stop collecting data from a set of data sources if the quiet mode is active, or start collecting data at an increased frequency if hyper is active. Some components might require specific names, which are described in their documentation. Components that allow configuring a required operational mode setting can also invert the requirement by adding a ! prefix to the mode name, for example !hyper can be thought of as "when hyper is not active". You can also specify exactly ! to match only when no mode is active.

Datum Filters also make use of operational modes, to toggle filters on and off dynamically.

44.1 Automatic expiration¶

Operational modes can be activated with an associated expiration date. The mode will remain active until the expiration date, at which time it will be automatically deactivated. A mode can always be manually deactivated before its associated expiration date.

44.2 Operational Modes management API¶

The SolarUser Instruction API can be used to toggle operational modes on and off. The EnableOperationalModes instruction activates modes and DisableOperationalModes deactivates them.