ATCoach  Tactical Edition PAR Simulator (APARS) DATA MANAGEMENT: ATCOACH FILES PART ONE

1. ATCoach Tactical Edition PAR Simulator • (APARS) • DATA MANAGEMENT: • ATCOACH FILES • PART ONE • Function Key Config, .atcinit, & Radar Type Data Files • CLS2004.A.0-004.1

2. LESSON OBJECTIVE • Action: • Define the format of ATCoach files. • Condition: • In a classroom environment. • Standards: • In accordance with the ATCoachTactical Edition PAR Simulator User Manual.

3. ATCoach Files • ATCoach Files - Introduction. (UM Section 4.1) • ATCoach obtains information from several data files in order to run: • Function Keys Configuration File. • .atcinit File. • Radar Type Data File. • Site File. • Scenario File. • Aircraft Model File. • To manipulate specific files, the file must be opened with the text editor. This editor is similar to the notepad utility in the Windows environment. • The vi (view) editor may also be used, but this is not recommended if you are not familiar with using vi. • All files are accessible from the Workspace submenus. (Except for the radar data file) You must be logged in as atcdev to modify any ATCoach file. You must be logged in as atcdev to modify any ATCoach file. You must be logged in as atcdev to modify any ATCoach file. You must be logged in as atcdev to modify any ATCoach file.

4. ATCoach Files • ATCoach Files - Introduction. _ Underscore. Usually indicates a space between entries is required, however, the symbol is required in some entries. < > Greater than/Less than. Indicates entry is mandatory. [ ] Brackets. Indicates entry is optional. | Pipe. Indicates options within an entry. # Pound. Not recognized by Unix, this symbol is typically used to enter remarks. (Similar to the REM command used in DOS). • File names & Extensions. • Scenarios are designed for a specific site. Each Scenario has a filename containing an extension. • The three letter extension corresponds to the first three letters of the Site file name. • Format and Symbols. • Each file has a specific format that must be adhered to. • Standard symbols used throughout these files: EXAMPLES prob1.gsbcorresponds with gsb.st prob1.lyb corresponds with lybs.st prob1.tuz corresponds with tuz.st

5. . • The function key "F10" is unavailable for use. Function Keys • Function Keys Configuration File. (UM Section 4.2.6) • Any ATCoach command can be assigned with the exception of commands that require additional data from the user (other than aircraft call sign). • To program the function key assignments, access the IQAK configuration file via the Workspace menu under IQAK Config. • Within the Instructor Quick Action (IQAK) configuration File. • Allows the user to program up to 11 function keys for each student position to execute ATCoach commands. • Each key is configurable by position, and mode of operation standalone or interactive. (Interactive mode is N/A for APARS). • For example, the altitude command may not be assigned to a function key because it requires the user to enter an altitude in addition to the aircraft call sign.

6. IQAK_CONFIG [Default] | <exercise mode> <position type> IQAK_DEF <#> <Make> <ATCoach command> <Init Flag> Function Keys • Function Keys Configuration File. • Entry Configuration and Definition field formats. • EXAMPLE IQAK_CONFIG STANDALONE FINAL IQAK_DEF 1 MAKE CE NO IQAK_DEF 2 MAKE CS8 NO IQAK_DEF 3 MAKE CS15 NO IQAK_DEF 4 MAKE CS20 NO IQAK_DEF 5 MAKE CTA NO IQAK_DEF 6 MAKE CTDA NO IQAK_DEF 7 MAKE CTDI NO IQAK_DEF 8 MAKE CTB NO IQAK_DEF 9 MAKE CMT0 NO IQAK_DEF 11 MAKE CTHE NO IQAK_DEF 12 MAKE CTS NO • <exercise mode> Standalone or Network*. *(Network N/A for APARS). • <position type> Arrival* or Final. *(Arrival N/A for APARS). • <#> Number of Key; up to 11 allowed; 1 - 9 and 11, 12. • <Make> Make indicates the button is pressed. • <ATCoach command> Any ATCoach command not requiring additional data other than aircraft call sign. • <Init Flag> Y or N indicates if the command should be executed during initialization. Note that the _ does not indicate that a space is required in these entries.

7. CS20 • This example would apply to all scenarios because Begin and End have not been specified for a specific scenario. .atcinit File • Initialization Data File (.atcinit). (UM Section 4.2.4) Begin ex001.gsb CS20 End ex001.gsb Assigns 20 mile scope range for a single scenario (ex001). • The .atcinit file contains ATCoach initialization information. It may contain entries for modifying site, scenario, and system parameters at startup. • All ATCoach console and controller keyboard system settings can be preset at startup, rather than entering the commands manually after the exercise has started. • Since all of these features have initial default settings, the file is not required. • The file is not case sensitive, however, site and scenario names must be entered explicitly. • The entries can be used for all scenarios or sites on a global basis, or individually by site or scenario. Begin gsb.st CS20 End gsb.st Assigns 20 mile scope range for all associated .gsb scenarios. • EXAMPLES • Keywords Begin and End are only required if an entry is made for a specific site or scenario.

8. Radar Type Data File • Radar Type Data File (angpn22.dat/antpn25.dat) (UM Section 4.2.5) • The radar type data files contain the initialization information that configures the facility’s radar display. • Contains multiple parameters to adjust or limit the settings on the display. Examples: • Soft panel • Intensities • Antenna performance • Cursors • Target tracking performance

9. ATCoach Tactical Edition PAR Simulator (APARS) PART ONE COMPLETE CLS2004.A.0-004.1