KB_OAT_Maneuver_Actions.txt

Deprecated Legacy Feature

Maneuvering actions are a deprecated legacy feature of ADS-IDAC. Their use is no longer recommended. For new projects, this file must exist in the input directory but should contain only a stub with number_of_maneuvering_actions set to 0.

Purpose

Maneuvering actions were designed to allow ADS-IDAC to model continuous control manipulations without activating mental beliefs or related procedures. A maneuvering action models a simple control system that actuates a single component to maintain a target parameter within a specified band.

As the sophistication of the ADS-IDAC knowledge base increased, mental beliefs and mental procedures became available to exercise similar control outputs in a more realistic manner. Specifically:

• Mental beliefs can control more than a single component or consider more than one target parameter and control band.
• Maneuvering control actions bypass certain aspects of the information gathering and perception filtering processes; the use of mental beliefs and mental procedures does not bypass these cognitive processes.

Because some older ADS-IDAC project files may still use maneuvering action capability, the program will attempt to read KB_OAT_Maneuvering_Action.txt during program initiation. For new projects, the file must be present but should declare zero actions.

Input File Format

Number_of_operator_Maneuver_action
number_of_maneuvering_actions

Parameter Description

Parameter	Type	Description	Example Value
number_of_maneuvering_actions	Integer	Number of maneuvering actions defined in the file. Range: ≥ 0. For new projects, set to 0.	0

Recommended Stub Configuration

For all new ADS-IDAC projects, the file should be left as a stub with no actions specified:

Number_of_operator_Maneuver_action

0

New Projects

The above stub is the recommended content of KB_OAT_Maneuvering_Actions.txt for any new project. Setting number_of_maneuvering_actions to 0 ensures the file satisfies the program's read requirement without activating any legacy behavior.

Legacy Format Example

For reference only, the following illustrates a fully specified legacy maneuvering action entry. This format is provided to support reading of older project files and should not be used in new work.

Number_of_operator_Maneuver_action

1

MANEUVER_Throttle_HPI_to_50_SCM
X_HPI
0.0
1.0
SCM_113
45.0
50.0
55.0
RATE_SCM_113
-1.0
1.0
50.0
0.0
25.0
0.0
0.0
0.0
15.0
3600.0

0.0
-25.0
-50.0

The legacy format fields are, in order: maneuver name, interactive control name, control lower bound, control upper bound, targeted parameter name, lower bound target, center target, upper bound target, targeted parameter rate name, rate lower bound, rate upper bound, and the 3×3 ratio control table entries followed by maneuver time interval and maneuver total duration.