Creating a new scenario, SGET generates a blank scenario with no targets, commands or any definitions. A New Scenario Wizard is used to guide the user through selection of a scenario name, adaptation and optional weather scenario to be used in the newly created scenario.
To create a new scenario, select from the GSGT Main Window (see Section 2.3, “Main Window”)
![[Note]](note.png) | Note |
|---|---|
|
If a scenario is already open when the option is selected, the new scenario will be automatically configured to use the same adaptation(s) as the current scenario. If you wish to select the adaptation(s), exit and re-start GSGT without opening another scenario, then select . |
-
Goes to the previous screen.
-
Goes to the next screen.
-
Quits the scenario wizard without creating a new scenario.
Adaptations are grouped by charting cycle. The charting cycle is displayed in blue and the adaptation is displayed in green. Users select the desired adaptation by clicking or highlighting the file name and clicking on 'Finish'. The window is displayed and the status line is updated as the adaptation and scenario are loaded and displayed (see Section 3.2.1, “Load Progression Display”). Once parsing of the adaptation data is complete the list of available adaptation is displayed.
| Note |
|---|---|
|
This step is skipped if another scenario was open before was selected. |
While loading adaptation list a dialog is displayed until all adaptation data information is collected.
Single adaptation. The selected adaptation is parsed to create the airspace adaptation objects as well as parsed for their facility adaptation information.
Multiple Adaptations. Multiple adaptations may be selected. The first adaptation selected (marked with a diamond in front of its name) is parsed to create the airspace adaptation objects (which define the entire airspace), All selected adaptations are parsed for their facility adaptation information. To select additional adaptations hold down the CTRL key while clicking on individual adaptation files names, or hold SHIFT key while clicking on the additional adaptation to select a range (all adaptations will be selected between the first and last adaptation selection).
Depending on the GSGT mode, additional option is presented allowing to select type of aircraft characteristics to be used in the scenario. Each set of aircraft characteristics is tailored to its specific use. Available sets are describe in Table 4, “Aircraft Characteristic sets”
Table 4. Aircraft Characteristic sets
| Mode | Description |
|---|---|
| Adapted |
Set of aircraft characteristics included the adaptation. |
| Training |
a specific set of aircraft characteristics tailored for running with training scenarios. |
| Minimal | A set of aircraft characteristics with minimal values. |
| Built-in |
A set that closely resembles adapted aircraft characteristic for use with adaptations that do not include aircraft characteristic. |
- Location Selector
-
Location of the scenarios, such as default local location or other media such as CD-ROM or flash drive.
- Scenario Name
-
Scenario name can be an existing scenario name or a non-existing scenario name typed in by the user. The new scenario will be created in the selected directory. Selecting an existing scenario will populate the name for the new scenario, and if user proceeds with creation of new scenario the existing scenario will be overwritten (see Section 3.1.5, “Scenario Overwrite Warning”)
| Note |
|---|---|
|
Directories are displayed in blue and scenarios are displayed in green. Read-only directories and scenarios are colored black and grey respectively. Right-click on a directory allows the user to create a new directory or subdirectory under the selected directory. |
Weather files may be selected by clicking or highlighting the desired weather directory. Selecting a weather file is optional.
-
Parses the adaptation data and loads the scenario. Not enabled until an adaptation is selected.
-
Cancels creation of the new scenario.
To open a scenario select from the GSGT Main Window (see Section 2.3, “Main Window”).
| Note |
|---|---|
|
Starting GSGT Editor from a command line while inside the scenario directory it will automatically open that scenario. |
-
Disabled in this window.
-
The selected scenario is opened in the GSGT main window. Enabled after a scenario is selected.
-
Closes the window and cancels scenario open action.
| Note |
|---|---|
|
Opening a scenario which uses different adaptation than the current scenario will close the current GSGT session and start a new one. It may take a few seconds for the new GSGT session to appear (depending on system performance). |
The above window will be displayed and the step currently being performed will be listed at the bottom of the window.
When completed, an adaptation window will be displayed and the scenario can be reviewed or modified.
If there are errors encountered while loading the scenario, the Gsgt Session Log will be displayed listing all errors encountered during loading.
When a scenario is opened, GSGT also opens a session with ATCoach. The ATCoach simulation engine is used to preview flights, derive target messages, and run certain reports. The ATCEngine window, shown below, displays all commands sent to the ATCoach engine as well as all status messages and responses.
| Note |
|---|---|
|
If the ATCoach engine should terminate, a red 'ATCoach exited unexpectedly!' message will be displayed in the ATCEngine window. |
The main scenario editor window displays a list of objects by type that can be edited. Clicking on an object type displays all of the instances of the object type contained in the scenario, if any.
Select from the GSGT Main Window (see Section 2.3, “Main Window”).
Clicking the button will toggle between sorting the object instances in ascending and descending order. The triangle in the button indicates which ordering will be used after the button is clicked. The same applies for the other buttons.
Scenario Editor also provides ability to view adapted equipment as defined by selected adaptation(s), such as Arts and FDIOs, to mention few, as well as Radars and ADS-B Service Volumes (see Section 4, “Scenario Editor”)
To create a new object, right-click on the object listing. A context menu with the option is displayed. Selecting from the menu opens a dialog window to define the new object.
To delete an object. right-click on an object instance name. A context menu with (and possibly other options) is displayed. Selecting from the menu opens a confirmation dialog, asking user to confirm deletion of the selected object(s).
To edit an object, double-click on an instance name and the editor window will be replaced with the editor dialog for specific type of object instance selected (see Section 4, “Scenario Editor”)
Replication provides the ability to produce copies of the selected objects such as System Commands or Targets. The replications can be dynamic or non-frozen, so that single object manages all its replications and a change to that object is reflected across all replications of that object. Or replications can be frozen, which in essence create an exact copy of the original object, and therefore the new objects can be independently modified to specific needs.
The Replication Editor dialog varies depending whether a System Command or Target is being replicated. As shown in screen capture below, following options are available for Target replications. System Command replication options do not include ability to replicate ACID, ICAO Address or Beacon, other wise the dialogs are identical.
-
Scroll-menu allowing you to choose the number of copies.
-
Scroll-menu to select how the target identifiers will be separated. If the base target has the identifier UAL001, and you choose '1' for the Delta AID, the following targets will be separated numerically UAL002, UAL003, UAL004...
-
Scroll-menu to select how the ICAO addresses will be separated. If the base target has an ICAO Address of AB00E9, and you choose '3' for the Delta ICAO Address, the following target beacon codes will be separated numerically AB00EC, AB00EF, AB00F2....
-
Scroll-menu to select how the beacon codes will be separated. If the base target has a beacon code of 1011, and you choose '3' for the Delta Beacon, the following target beacon codes will be separated numerically 1014, 1017, 1020....
-
Scroll-menu to select when the replications will enter the scenario. The default time is 20 minutes. If the original has a scenario time of 00:10:00 then the first replication will enter the scenario at 00:30:00.
-
When checked, produces a hard copy replications that are no longer tied to the original object. Frozen replications will appear separately in the GSGT Editor list view. Non-frozen replications remain associated with the original.
-
Adds the specified number of replications to the scenario.
-
Closes the 'Replicate' window without saving changes.
Leaving the pointer over a non-frozen replicated System Command or Target will cause a balloon help to appear with the details of the replication.
To save current scenario select from the GSGT Main Window (see Section 2.3, “Main Window”).
To save a scenario under a different name select from the GSGT Main Window. This allows to specify the name and location of the scenario files. A directory with the name as the specified in Scenario Name is created in the selected location.
When a scenario name is specified in the Save Scenario dialog already exists, the user is prompted to overwrite the existing scenario.
-
The existing scenario file is overwritten.
-
The save action is cancelled.
When the user attempts to exit the GSGT application and unsaved changes have been made to the scenario, the following dialog is displayed.
-
The scenario file is saved and the application is exited.
-
The scenario file is NOT saved and the application is exited.
-
The scenario file is NOT saved and the application is exited.
-
The scenario is not saved and the application exit is cancelled.
- save the GSGT Session Log?
When the GSGT session is exited, a dialog prompting to save scenario before exit or dialog confirming program termination includes an option to save the Save Gsgt Session Log. Selecting this option will open a dialog (similar to the Save As dialog) which allows a name and location to be specified for saving the Gsgt Session Log.
Additionally when session is closed by opening another scenario, a dialog is presented to save the Save Gsgt Session Log.
The Scenario Information dialog displays a summary of the scenario. Included in the summary are the scenario Start time, Airspace Adaptation name and site, Facility Adaptation name(s) and site, Weather directory, and the number of Targets, RSIs, and AC characteristics defined.
Select Info from the GSGT Main Window (see Section 2.3, “Main Window”).
-
Closes the Scenario Information dialog.
Scenario Manager opens a default file manager, which may vary depending on the system and configuration, that enables to list the source directories and scenarios that can be copied, moved, or deleted.
Select from the GSGT Main Window (see Section 2.3, “Main Window”).
One of the methods to include a weather scenario to an existing GSGT scenario consists of a process that may be lengthy if the scenario is large. Adding a weather scenario this way will link in the weather scenario and enable the preview of weather in the GUI in the same way as when creating a new scenario with weather.
- Step 1
-
Create a new GSGT scenario and select the weather scenario of choice in the New Scenario Wizard (see Section 3.1, “Create new scenario”).
- Step 2
-
Import the original GSGT scenario into the new GSGT scenario created in the step above.
- 2.1
-
From the menu bar select . This will open a window Open existing scenario.
- 2.2
-
Select the original GSGT scenario from the list of scenarios and select Open.
- 2.3
-
Place check marks on all sections to import entire scenario and select Next and on final page select Finish.
- 2.4
-
Wait for the scenario import to finish and once done, verify all data was imported.
An alternative method of including a weather scenario into an existing GSGT scenario doesn't involve re-importing the scenario but requires editing the scenario source files manually. At this point there is no option in the GSGT GUI to perform this task. Adding a weather scenario this way will link in the weather scenario and enable the preview of weather in the GUI.
- Step 1
-
Edit
scenario.xmlfile in the directory to where the scenario source is located. - Step 2
-
Add a new line before </scenario> (should be the last line in the file) and type the following in the new line:
<wx dir=”<weather_scenario_name>” readOnly=”1” />
where
<weather_scenario_name>is the name of the weather scenario to be included into the scenario. This is an actual name of the weather scenario. If weather scenario was saved in subdirectory of default location of weather scenario, include the relative path. (This should be relative path from $WX_PATH directory)Example 3. GSGT Scenario with weather (scenario.xml file)
<scenario version="7.4.1.4" > <airspace file="c100we29/release.dbm" readOnly="1" /> <facility file="c100we29/release.dbm" readOnly="1" /> <facility file="./zdcadaptation.xml" /> <achar file="userachar.xml" /> <prefs file="prefs.xml" /> <rsi file="rsi.xml" /> <targets file="tgts.xml" /> <syscmds file="syscmds.xml" /> <radars file="radars.xml" /> <svols file="svols.xml" /> <atcoach file="atcoach.xml" /> <wx dir="wx_swd3b" readOnly="1" /> </scenario>