HOW TO USE THE RHAW/HFI INTERFACE

JFORCES support functions

The following tools are provided within JFORCES to assist in geolocating.

From the Tracks for Sensor 1 gui, Controls tools include:


Insert New SOI
The Insert New SOI gui allows the user to manually define an SOI lat/long point (as an alternative to semi-automating geolocation in Estimate SOI from Displayed Historical LOB's). You can enter the lat/long coords, or select a point on the FORCES map.


Emitter Data
The Emitter data used in JFORCES is provided by the range/site via hardcopy and verbal information. The emitter data is required for Review All Known Site Information, Review Threat/Track Information, and Load AEF diags table. We maintain the provided information in a SQL plaintext file in our cvs repository called: sim/maintenance/rhaw_db/emitter_data_2
The command:
psql tactical < emitter_data_2
..will create the database table 'emitter_data' for use in JFORCES.


Review All Known Site Information
This option lists all the emitter definitions known for the area (as stored in the 'emitter_data' table).

The gui displays the name and lat/long position. If you double click (left mouse button) on a particular emitter, it will list all the frequencies and PRI's given for that emitter.

If you have Loaded the AEF diags table, then if you double click the middle mouse button, it will drop down a list of track id's that have frequency/PRI's that match this emitter (if any). In order for the track id cross reference to be accurate, you must be sure that the Load AEF diags table has been performed for the .aef file you are analyzing. Each time you Load the AEF diags table, it deletes the previous data, so you will have to re-load it every time you analyze a different .aef file from your previous analysis.


Review Threat/Track Information
Review Threat/Track Information reviews the .aef data against the known emitters database table, and returns a list of the emitters where tracks have been found that have matching frequency/PRI's.

The gui displays the name and lat/long position. If you double click (left mouse button) on a particular emitter, it will list all the frequencies and PRI's given for that emitter.

In order for the known emitter list and track id cross reference to be accurate, you must be sure that the Load AEF diags table has been performed for the .aef file you are analyzing. Each time you Load the AEF diags table, it deletes the previous data, so you will have to re-load it every time you analyze a different .aef file from your previous analysis.


Load AEF diags table
Load AEF diags allows user to create a rhaws_diags database table in the database to store LOB data from the input .aef and .nav file currently being analyzed.

Each time you Load the AEF diags table, it deletes the previous data, so you will have to re-load it every time you analyze a different .aef file from your previous analysis.

This table is required to be current for Review All Known Site Information and Review Threat/Track Information.


Back to How to run the HFI/RHAW interface