STAR
Cal STAR — firmware, DAQ server, and engine design
Loading...
Searching...
No Matches
fsw::script::SlugTables Struct Reference

What a script's slugs are allowed to name, built from the loaded config. More...

#include <StateScript.hpp>

Collaboration diagram for fsw::script::SlugTables:
[legend]

Public Attributes

std::map< std::string, std::string > actuators
std::map< std::string, std::string > sensors
std::map< std::string, std::string > states
std::set< std::string > allowed_transitions
 State slugs reachable from the state that owns this script, per state_transitions.csv.

Detailed Description

What a script's slugs are allowed to name, built from the loaded config.

Maps rather than sets so a diagnostic can name the canonical spelling a slug resolves to, which is what the operator sees elsewhere in the UI.

Definition at line 256 of file StateScript.hpp.

Member Data Documentation

◆ actuators

std::map<std::string, std::string> fsw::script::SlugTables::actuators

Definition at line 257 of file StateScript.hpp.

◆ allowed_transitions

std::set<std::string> fsw::script::SlugTables::allowed_transitions

State slugs reachable from the state that owns this script, per state_transitions.csv.

Every transition_to target is checked against this — not just the configured fallbacks — because a script that runs 25 s and THEN cannot leave is worse than one that never starts.

Definition at line 264 of file StateScript.hpp.

◆ sensors

std::map<std::string, std::string> fsw::script::SlugTables::sensors

Definition at line 258 of file StateScript.hpp.

◆ states

std::map<std::string, std::string> fsw::script::SlugTables::states

Definition at line 259 of file StateScript.hpp.


The documentation for this struct was generated from the following file: