Notes on External JFORCES Interfaces

Proven interfaces to the JFORCES system (for the most part documentation is still in process):








The current NWARS interface is unusual among the JFORCES interfaces because the interface is not a simple real-time interface but instead a two-step process. In the first step a JFORCES run generates a set of three input file for NWARS. These input files are used to initialize an NWARS run. JFORCES and NWARS are then run together and a JFORCES interface procedure searches for new TACELINT reports by NWARS and forwards them to JFORCES, where they are currently shown as Intel messages on the MMI.

The reason that a procedure was created to generate an NWARS scenario from a JFORCES scenario was no other immediate method was found for verifying the compatibility of JFORCES and NWARS scenarios with as little maintenance. Today, there's a NWARS / TACSIM interface that the NWARS programmers have suggested as a real-time alternative to this process. If any program wishes to use these two models in an integrated environment on a regular basis it's recommended that this new interface be persued. In the meantime here's how to set up the simulations to run in a roughly integrated manner currently:

First a JFORCES scenario needs to be set up output NWARS input files. Any JFORCES scenario can be used for this purpose, but there's ancillary data that must be loaded into the nwars amplification database table for each asset whose presence should be identitied to NWARS. One line should be added to this table for any asset whose data should be save for NWARS. Each line has the following fields:

  1. Scenario – the name of the JFORCES scenario this record applies to.

  2. Name – the platform name of the asset

  3. id – the asset's tailnumber. The scenario, name and id provide a unique key into the objectdefn table so the system can determine which asset data should be collected on.

  4. BE – The BE information on the asset.

  5. BE_category – The asset's BE category.

  6. equip_code - MIDB equipment code

  7. emitter_policy – the asset's emmitter policy as defined by NWARS.

Fields 4 through 7 are used by JFORCES but are instead passed to NWARS for it's use. Fields 4 through 6 must correspond to MIDB protocol and field 7 to NWARS protocol.

There is no JFORCES special interface to this database table. It's recommended that the “pgaccess” utility be used to fill in the data.

After this data is included JFORCES must be told to save the files. This is done in the run configuration's software model specification. To set this start the FORCES interface and go to System Controls->DBA->Plan Run->Run Configuration->Maintain Run Configurations and select the run configurationyou intend to run in JFORCES. When this information is displayed click on the Software Configuration option and select “Review Current Choice” from the displayed list. Then verify the “NWARS Output” option is clicked on. Alternately a new software configuration can be defined and used.

Verify the NWARS_DATA_DIR environmental variable is set and the associated directory exists. Typically the $DTA_DIR/NWARS directory is used. Then run the JFORCES scenario. Three files will be created in the $NWARS_DATA_DIR directory:

  1. MIDB_static – MIDB data for static assets.

  2. MIDB_mobile – MIDB data for mobile assets.

  3. NWARS_event – this is the NWARS event files telling NWARS how assets moved over time

Together these files can be used to define an NWARS run.

After NWARS is initialized with this data the NWARS and JFORCES simulations can be run together with NWARS TACELINT messages being injected into JFORCES in real time. However, timing synchronization is the user's responsibility. (As said earlier, it's recommended that the new interface be explored if regular integrated runs are planned.) Before running verify that NWARS can run tcl. Then start NWARS and JFORCES and hold in the initialized but paused state. Start the real-time injection interface in JFORCES viea the runtime menus by going to System Controls->Remote Interfaces->TACELINT sniffer.

Finally, start the TACELINT_sniffer.tcl on the NWARS machine (alternately, crosslink the NWARS TACELINT output directory to the JFORCES host and start the TACELINT_sniffer on this machine). This “sniffer” will recognize new messages as they are created in this directory and forward them to JFORCES, where they will subsequently be sent to the runtime interface as intel reports. The intel reports can be interrogated by selecting Scenario Controls->Umpire Controls->Intelligence Reports->Review Intelligence Reports (or the equivalent Blue interface).