HOW TO USE THE RHAW/HFI INTERFACE
JFORCES task within the Horizontal Fusion Initiative was to take Lines
of Bearing (LOB) data provided from RHAW sensors on AH64 Apache
Helicopters and FA-18 Hornets, and geolocate potential threats. Two
files were provided by the FA-18: one containing the aircraft's
lat/long position and one containing the LOB detections. The AH-64
provided the combined data in one file. At the time of the project,
there wasn't enough accuracy in the data to be able to fully automate
the geolocation process, so JFORCES was implemented to allow for a
human to perform some degree of manual interpretation by viewing the
results on the JFORCES Map.
The following describes how to perform geolocation within JFORCES
(also see Support Functions and
Running RHAW data in JFORCES:
- start JFORCES.
- from System Controls, select Start HFI Replay
- Select the Database (ie: 'tactical').
- select the Type (AH-64 or F/A-18)
- click on Undefned under the Nav File:
- for the F/A-18, select the input *.nav file
- for the AH-64, click on the Files of Type: and select
Apache LOB Files, then select the input *.lob file
- for the F/A-18, select the input *.aef file (disregard for the
- press Go (disregard the FREQ file missing error)
- wait for the Simulation to load, then in System Controls,
- you probably want to adjust the Clock Control to fast
- let the replay run through to the end of the recording.
- in Scenario Controls, go to Blue Controls,
Sensors, Sensor Controls, RHAW Controls.
- from the menubar, select Controls, Manage LOBs,
- the gui displays Tracks for Sensor 1, listing all the
LOB's replayed within the default Frequency (0. to 999.) and PRI
range (0. to 10000.).
- in the HFI exercises, we were provided with Frequency and PRI
values of 2 known emitters on the range. To filter the tracks display
down to a specific emitter:
select Controls, Reset History Filters, and enter
a range slightly outside the Freq/PRI given, and Confirm.
For example: given site K02: frequency = 28.629 and PRI = 166.77,
enter: Frequency: 28.0 - 29.0, PRI: 165 - 168
- from the tracks now listed in the Tracks for Sensor 1, double
click each line to popup the Historical Frame Info gui.
Select All On. You'll note from the forcesMap that the LOB(s)
and aircraft position is displayed. You'll observe that some tracks
are complete garbage, in which case you can de-select them (All Off,
or click off individual LOB's). Once you have established a set of LOB's
with intersecting lines,
- select the Controls, Estimate SOI from Displayed
Historical LOB's option to pop up the Threat Region gui.
- select Pick New Region From Map, and going over to the
forcesMap, click 2 opposing rectangle points on the map to create a
box around the most valid intersections. You may re-select Pick
New Region From Map as often as needed to surround the
intersections correctly. Once you have that established, click on
Confirm in the Threat Region gui.
- the Manage Emitter Sites gui will display, showing the
results of the SOI:
and the forcesMap will display a white diagonal box where the SOI
point has been located:
- select the Edit button on the SOI you just created, and
edit the Report Type field with the emitter id you're working
from, the Threat with the identifier requested for the
exercise, and Save.
- To repeat the process with another emitter, close all the gui's
except the Manage Emitter Sites gui, and from there, select
Controls, Manage LOBs, and 1 to return to the
Tracks for Sensor 1 gui where you can proceed with Frequency
PRI filtering at step 12.
- Once you have created all the SOI's required, return to the
Manage SOI's gui, and from Controls, select the
Export SOI's option appropriate to the emitter. The generic
Export SOI's option will ask for a filename and generate a
comma delimited file of the SOI data you created as is. The other
Export SOI's - ?? Hack are designed to create a file with
the lat/long points adjusted from China Lake to Ft.Eglin.
For example, if you created, a K02 and J29 emitter SOI, you will
need to save a file via the Export SOI's - K02 Hack and
the Export SOI's - J29 Hack, and edit the output files into
one (taking the K02 SOI from the K02 Hack output file, and the J29
SOI from the J29 Hack output file, together into a new file).
Support Functions and Utilities