Skip to content

Input Files — Overview ​

ADS-IDAC is supported by a structured collection of plain-text input files that together define the nuclear plant model, operator knowledge bases, and program executive control parameters needed for code execution. All input files are located under the Input/ directory of the project (the directory given as --project-dir), organized into the categories below. The complete tree is described in Directory Structure.


Generic Input File Format ​

All ADS-IDAC input files follow a common set of formatting conventions:

  • One datum per line — each input value occupies its own line
  • Keyword headers — sections begin with a keyword string that identifies the data block (e.g., Action_Taker, Number_of_biased_parameters)
  • Count integers before lists — when a variable-length list of items follows, an integer specifying the count must appear first
  • No spaces in strings — string parameters (names, labels) must not contain spaces; use the underscore character _ as a substitute (e.g., SG_Level not SG Level)
  • Case-sensitive — all keywords, parameter names, and string values are case-sensitive and must match exactly the identifiers used in cross-referenced files (e.g., ControlPanel.txt, Procedures.txt)

Input Consistency

String identifiers used in one input file (e.g., a control_volume_name in ControlPanel.txt) must exactly match the corresponding identifier in all referencing files. Case mismatches and spelling differences will cause errors during input file processing. Review err messages.txt after every simulation run to confirm all input files were processed without errors.


Input File Categories ​

Crew — Action Taker ​

The Action Taker fulfills the role of the reactor operator. All crew interactions with the plant model are executed by the Action Taker through control panel indicators, alarms, and controls. The ten Action Taker input files define static behavior factors, the operator's knowledge base, and the diagnostic/reasoning engine parameters. Files are located in Input/Crew/ActionTaker/.

Crew — Decision Maker ​

The Decision Maker fulfills the role of the Senior Reactor Operator, directing the Action Taker and selecting high-level goals and problem-solving strategies. The Decision Maker knowledge base uses an identical file structure to the Action Taker, with the OAT prefix replaced by ODM. Files are located in Input/Crew/DecisionMaker/.

Procedures ​

Procedure files define the ADS-IDAC representations of the plant's written emergency and abnormal operating procedures, plus mental procedures triggered by knowledge-based beliefs. Six file types govern procedure content, procedure step definitions, and the three types of branching rules (action time, control value, and mental procedure activation time). Files are located in Input/Crew/Procedures/.

Plant Hardware and Simulation Control ​

These files define the interface to the plant model, hardware and support system reliability, initiating events, and the simulation control parameters. They are located in Input/Indicators/, Input/System/, Input/HardwareReliability/, Input/SupportSystemsReliability/ and Input/Scheduler/. The optional ZiniADS.txt options file is read from the launch directory.


Complete Input File Reference Table ​

#File NameDirectoryPurpose
1ActionTaker.txtInput/Crew/ActionTaker/Static Action Taker behavior parameters: action time multiplier, scan queue limit, memorized information use, skip thresholds, communication time, troubleshooting and procedure use probabilities, goal/strategy tendencies
2KB_OAT_Bias_Factors.txtInput/Crew/ActionTaker/Simulates failed control panel instrumentation: additive errors, proportional errors, stuck instrumentation, and threshold-limited instruments visible to the Action Taker
3KB_OAT_Diagnosis_Actions.txtInput/Crew/ActionTaker/Maps diagnostic imbalance events to candidate Action Taker actions; includes reset delay times and action priority ordering
4KB_OAT_Event_Matrix.txtInput/Crew/ActionTaker/Fuzzy logic diagnostic event matrix: maps symptom patterns to event classifications (normal, AOO, DBA) for the Action Taker's diagnosis engine; all events should have corresponding mental beliefs
5KB_OAT_HardWired_Diagnosis.txtInput/Crew/ActionTaker/Defines mental beliefs for the Action Taker: activation criteria (evidence thresholds), branch probabilities, associated mental procedures, and priority levels
6KB_OAT_Maneuver_Actions.txtInput/Crew/ActionTaker/Knowledge-based maneuver action definitions available to the Action Taker for non-proceduralized responses
7KB_OAT_Safety_Parameters.txtInput/Crew/ActionTaker/Critical safety function parameters and their acceptance thresholds monitored by the Action Taker
8KB_OAT_Scanned_Parameters.txtInput/Crew/ActionTaker/Defines the set of control panel parameters included in the Action Taker's periodic scan queue; governs which plant indicators are actively monitored
9KB_OAT_System_Decomposition.txtInput/Crew/ActionTaker/System functional decomposition used by the Action Taker for knowledge-based system-level diagnosis
10KB_OAT_Time_Constrained_Input.txtInput/Crew/ActionTaker/Time-constrained action parameters governing the time constraint loading PIF for the Action Taker
11DecisionMaker.txtInput/Crew/DecisionMaker/Static Decision Maker behavior parameters: same structure as ActionTaker.txt; troubleshooting and procedure use probabilities are active for the Decision Maker
12KB_ODM_Bias_Factors.txtInput/Crew/DecisionMaker/Decision Maker failed/biased instrumentation definitions
13KB_ODM_Diagnosis_Actions.txtInput/Crew/DecisionMaker/Maps diagnostic events to Decision Maker candidate actions; includes reset delay times
14KB_ODM_Event_Matrix.txtInput/Crew/DecisionMaker/Decision Maker fuzzy logic diagnostic event matrix
15KB_ODM_HardWired_Diagnosis.txtInput/Crew/DecisionMaker/Decision Maker mental beliefs: activation criteria, branch probabilities, mental procedure references, and priority levels
16KB_ODM_Maneuver_Actions.txtInput/Crew/DecisionMaker/Decision Maker knowledge-based maneuver action definitions
17KB_ODM_Safety_Parameters.txtInput/Crew/DecisionMaker/Critical safety parameters monitored by the Decision Maker
18KB_ODM_Scanned_Parameters.txtInput/Crew/DecisionMaker/Decision Maker control panel periodic scan queue
19KB_ODM_System_Decomposition.txtInput/Crew/DecisionMaker/Decision Maker system functional decomposition
20KB_ODM_Time_Constrained_Input.txtInput/Crew/DecisionMaker/Time-constrained action parameters for the Decision Maker
21Procedures.txtInput/Crew/Procedures/Master procedure list: defines procedure names, types (EOP, AOP, mental), and entry condition cross-references; all procedure steps must be listed here
22ZProcedure_[name]_[step].txtInput/Crew/Procedures/Individual procedure step files (one per step): defines initial action, action expectations, non-response action, baseline skip probabilities, step type, and control variable references
23ZProcedure_MPBG_[name]_[step].txtInput/Crew/Procedures/Mental procedure step files: procedural actions activated by mental belief states from the operator knowledge base
24MentalProcedureActivationTimeBranches.txtInput/Crew/Procedures/Weibull distribution parameters (α, β, u) for branching on mental procedure activation time; references valid mental beliefs in HardWired_Diagnosis.txt
25ProcedureActionTimeBranches.txtInput/Crew/Procedures/Weibull distribution parameters for branching on procedure step action timing; specifies number of branches and associated time quantiles
26ProcedureControlValueBranches.txtInput/Crew/Procedures/Discrete control value options and associated branch probabilities for operator control input variability (e.g., valve throttle positions)
27ControlPanel.txtInput/Indicators/Defines all control panel indicators (parameters, alarms, component states), controls (state controllers, fine adjustment controllers, setpoint controllers), and scanning priorities visible to the ADS-IDAC operator model
28Initiating_Event.txtInput/System/Defines initiating events: specifies RELAP interactive variable assignments and activation conditions for equipment failures or disturbances that initiate the accident scenario
29RELAP5_channels.txtInput/System/Cross-references ADS-IDAC interactive control channel names to RELAP5 input deck card numbers (800 to 999 series); links the operator model to the thermal-hydraulic model
30SystemReliability.txtInput/HardwareReliability/Hardware reliability branching parameters: Beta distribution α and β values for initial failure, recovery, and conditional failure probabilities; specifies trigger events
31ZCtrlPar.txtInput/Scheduler/Simulation executive control parameters: sequence truncation time, probability cutoff value, and time step control
32Consultant.txtInput/Crew/Consultant/Consultant role parameters. No Consultant operator is instantiated in current simulations
33Calculation_Aid.txt, StaticPIF.txtInput/Crew/Polynomial calculation aids available to the crew model; static performance influence factors
34<support system>.ftaInput/SupportSystemsReliability/Support system fault trees, one file per support system
35ZiniADS.txtlaunch directoryOptional options file: option=value lines with the command-line option names; values on the command line take precedence

ADS-IDAC Engine Documentation