KB_OAT_Diagnosis_Actions.txt
Purpose
KB_OAT_Diagnosis_Actions.txt is the Action Taker's counterpart to the knowledge-based diagnosis action file. Diagnosis actions are used to implement knowledge-based problem solving when the control room crew is executing the troubleshooting goal. Diagnostic actions are grouped within functional areas that align with the imbalance events defined in KB_OAT_Event_Matrix.txt.
Implementation Status
Feature not implemented for the OAT
In the current version of ADS-IDAC, all knowledge-based actions are initiated by the Decision Maker (ODM). The KB_OAT_Diagnosis_Actions.txt file does not affect the simulation outcome.
However, the input processor requires this file to be present and syntactically valid. If the file is absent, an input error is generated during startup. The ADS-IDAC code has been architected to allow a future upgrade that implements Action Taker-initiated knowledge-based actions; this file is the placeholder for that capability.
Until Action Taker knowledge-based actions are fully implemented, it is recommended that no diagnosis actions be specified in this file. Set number_of_diagnoses to 0.
Knowledge-based diagnosis actions are fully implemented for the Decision Maker. See KB_ODM_Diagnosis_Actions.txt for complete documentation of the diagnosis action format and usage.
Parameters
| Parameter | Type | Description | Example Value |
|---|---|---|---|
number_of_diagnoses | Integer (>= 0) | Number of diagnosis event categories specified in this file. For the OAT, this value must be set to 0. If set to a non-zero value, that many diagnosis action data blocks must follow — but because they have no effect, setting the value to 0 is strongly recommended. | 0 |
File Format
number_of_diagnoses NUMBERFor the OAT, NUMBER must be 0:
number_of_diagnoses 0Sample Input
number_of_diagnoses 0Relationship to the ODM
The Decision Maker equivalent file, KB_ODM_Diagnosis_Actions.txt, uses an identical format header but may contain one or more complete diagnosis action data blocks. Each block specifies a functional area name (matching an imbalance event in KB_ODM_Event_Matrix.txt), a priority level, and prerequisite conditions. Refer to the ODM documentation for the full format specification.