Notes on Supporting JFORCES and RAP Over Prolonged Periods
Both JFORCES and RAP save archive files for replay that should be archived and purged periodically. There is no need to keep any of the files in any of these directories for any purpose other than replay, so feel free to delete the contents of these directories if there's no immediate desire to replay the files. As with common archival systems, you can back these files up, delete them from the hard drive, and restore them as required by your needs. In general you probably wouldn't want more than a month or two of information saved on-line in any of these files (unless you're restroring data for specific purposes).
The locations of these archives are:
$RAP_DATA_DIR/archives – The archives of all the raw radar returns collected by the RAP server are stored here for replay and analysis. The general format of the names of these files is RAPdata_(date).(unix date). For example the fileRAPdata_2003_Nov_01_09_00.3fa37613 indicates that this datafile records incoming raw data starting at 9:00 am GMT on November 1st, 2003. The suffix (3fa37613) is the corresponding unix time. The unix time is used by RAP scripts to aid the user in replaying or analyzing selected epochs, so it is inadvisable to alter the suffix.
$DTA_DIR/ccs/archives – These are the archives of all of the range ACMI information. Filename format is CCS_data_(date).(unix date). For example the file CCSdata_2003_Jun_13_09_58.3ee9e6a0 indicates this datafile records ACMI data starting at 9:58 am on June 13th, 2003. The suffix is the corresponding unix time.
$DTA_DIR/ccs/sadl – These are the archives of all data received or sent over the EPLARS/SADL link. Filename format is sadl_(date).(unix date) of data received and sadl_send_(date).(unix date). Only the sadl_(date).(unix date) files are required for replay; the others are saved for debugging the system. For more information on the contents of this directory see the SADL related links under www.jforces.info/faq.
$DTA_DIR/ccs/jtida – These are the archives of all data received or sent over the JTIDS/MIDS link. Current filename format is jtids_(unix date).
$DTA_DIR/replay – These are the archives of simulation inputs and are used to replay JFORCES exercises. These files are actually paired, one file having an .rpf suffix and the other having a .rpf.lnk suffix. Both files are required to replay a scenario. The principle part of the filename (e.g. Seans_test1 in the case of the paired replay files Seans_test1_replay.rpf and Seans_test1_replay.rpf.lnk) are assigned one of two ways. When any scenario is run these files are automatically saved according to the name of the scenario (or "Default" in the case of a run with only live participants). This is worthwhile to know because if you end a run and wish to replay it but you didn't select "Save Replay" during runtime you can go to this directory and change the principle part of both files to an alternate name and use these files for replay. The other way these principle components are selected is by the user during runtime. In this case the name specified by the user in the "Save Replay" widget is used instead of the scenario name upon a successful completion.
We have left it up to the site manager to determine which file pairs should be archived and which just ignored. This is because we have found that only occassionally are user's interested in replaying JFORCES scenarios. Also, as described in the replay description, these files only work if the scenario hasn't been changed. So if you're going to archive these files you should also dump and archive the matching scenario database. See the database note for information on how to do this.