Action Taker Input Files
Overview
The Operator Action Taker (OAT) represents the Reactor Operator in the ADS-IDAC simulation. The OAT is responsible for physically manipulating the control panel in response to directions from the Decision Maker (ODM). Unlike the ODM, the OAT does not have knowledge-based reasoning capability — it does not independently diagnose plant state or select goals. All knowledge-based diagnostic and goal-selection logic resides in the ODM subsystem.
The OAT reads plant state information through perception filters, applies performance influencing factors (PIFs), and executes procedure steps directed by the Decision Maker. Its behavior is shaped by static configuration files that establish scan limits, information load thresholds, update-time recency criteria, action timing distributions, and the hard-wired mental belief system used to trigger memorized procedures.
INFO
The OAT and ODM share the same file naming conventions and formats in many cases. Files with KB_OAT_ prefixes are exclusive to the Action Taker. Equivalent files for the Decision Maker use the KB_ODM_ prefix.
Input Files
| File | Description |
|---|---|
ActionTaker.txt | Main OAT configuration: action time multiplier, scan queue limit, information load thresholds, Weibull update-time distributions, skip thresholds, communication time, and branching probabilities. |
KB_OAT_Bias_Factors.txt | Models failed or biased control panel instruments; applies proportional, additive, stuck, or threshold-clamped distortions to the parameter values perceived by the OAT. |
KB_OAT_Diagnosis_Actions.txt | Stub file required by the input processor; knowledge-based diagnosis actions are not implemented for the OAT — must contain number_of_diagnoses = 0. |
KB_OAT_Event_Matrix.txt | Fuzzy logic diagnostic matrix linking observable symptoms (mental beliefs) to event categories (Normal, AOO, DBA, Imbalance) via numerical relationship values. |
KB_OAT_HardWired_Diagnosis.txt | Mental belief (hard-wired instinctive response) definitions; encodes prerequisite conditions, activation/reset Weibull delays, branch probabilities, and optional mental procedure triggers. |
KB_OAT_Maneuver_Actions.txt | Defines continuous control-manipulation actions activated by procedure steps with the MANEUVER_ prefix; models throttling and banding control without mental belief triggers. |
KB_OAT_Safety_Parameters.txt | Specifies the key safety-function parameters used to calculate the criticality-of-system-condition performance influencing factor (PIF). |
KB_OAT_Scanned_Parameters.txt | Defines the quantitative perception filter: the set of control panel parameters that the OAT can place in the periodic scan queue. |
KB_OAT_System_Decomposition.txt | Provides the functional decomposition of plant systems, mapping control panel indicators, controls, and alarms to high-level plant functions for use by the diagnostic engine and knowledge base. |
KB_OAT_Time_Constrained_Input.txt | Defines the plant parameters and critical thresholds used to calculate the time-constraint load PIF value for the OAT. |
Relationship to the Decision Maker
The OAT and ODM run as paired subsystems. The ODM directs procedure execution; the OAT carries out physical control panel actions and reports completion. Many of the OAT knowledge-base files have direct ODM equivalents (e.g., KB_ODM_HardWired_Diagnosis.txt). When a feature is documented as "not implemented for the OAT", the equivalent functionality is available in the corresponding KB_ODM_ file.