Current Defines used in JFORCES Builds


Name

Purpose

Normal Status

C2_DEBUG

Turns on C2 diagnostics. Should not affect program execution

off

DEBUG_COMM

Turns on communications module diagnostics. Should not affect program execution

off

NMD

Turns on special programming for the NMD module. This code has also been incorporated into the Red Force Operator engagement board. This code affect SAM reporting and controls

on

NETWORK_DIAGS

Turns on diagnostics for the communications network analysis module

off

FRATRICIDE

Turns on the option to consider fratricide (killing members of own team) in the engagement modules

off

DEBUG_ENGMENT

Turns on engagement module diagnostics. Should not affect program execution

off

AUTO_BDA

Flag to automatically assign a BDA mission after a bombing mission.

off

LINUX / SUN4 / SOLARIS / SGI / HP-UX / SUN_DEFS / DEC_DEFS

Flags for machine architecture

On as appropriate for the architecture. The system sets the via a call to sac_arch- verify this routine is working correctly when porting

CONFIRMATION_DIAGS

Turns on onfirmation diagnostics for autmated invocation of alternate plans (e.g. Redeployment). While this flag won't directly affect the program execution, these diagnositics have been used for operation situration awareness and are unavailable if this option is not selected

off

SIMPLE_CONFIRMATION

Turns on a simpler detection confirmation module for the automated alternate plan invocation

off

SNOR

Turns on tailored satellite reporting and retention algorithms developed for the SNOR project. When this flag is turned off the the interactive SNOR intface can not be supported

off

DEBUG_LIST

Turns on diagnostics for the air operations planning and event list. This option should cause no change in program execution

off

DEBUG_MOTION

Turns on diagnostics for asset motion. This option should cause no change in program execution

Off

REPAIR

Turns on the mean-time-between-failure and repair cycle. Both of these are outside the combat damage model (that is, this is not the repair of combat damage)

off

MODEL_AB_SUPPORT

This turns on limited or no support for specific aircraft types at airbases. By default any aircraft can be rearmed, refueled and fully prepped at any airbase. With this flag only selected bases can do full turn-around, while others can refuel but not rearm.

off

DEBUG_ROVER

Flag to turn on rover diagnostics. The rover is a automated flight algorithm for tasking airborne sensors to optimize coverage of key points over time. This flag should not affect program execution.

off

DEBUG_INPUTS

Flag to turn on diagnostics on tabular inputs. This flag should not affect program execution.

off

FIRST_DETECT

This flag prevents redetection of targets. Used for specialized “first-contact” studies.

off

ALL_DETECTIONS

When on sensors detect all assets regardless of whether they're friendly, foe, or neutral. When on no attempt is made to detect friendly assets.

off

INCLUDE_BDA

When on a detection of all targets, including dead ones, is attempted. The default is to attempt to detect only live assets

off

CONFIDENTIAL

Flag to include confidential-level code for TADIL-A

off

RAP_STANDALONE

Flag specifying this code is being run in RAP, as opposed to within the JFORCES simulation

On for RAP, off otherwise

TRACKER_DIAGS and TRACK_DIAGS_SHORT

Flag to dump tracker diagnostics. This flag should not affect program execution.

off

INTEL

Flag for whether the machine architecture is INTEL-based. This is really a flag for big-endian versus little-endian.

According to amchine architecture.

SENDMAIL

Flag for whether email should be sent from JFORCES as part of the USMTF format

off

SENDMAIL_DEBUG

Flag to dump diagnostics associated with the embedded email program. This flag should not affect program execution.

off

SIM_NO_VERSION

Flag for formatting engineering reports.

off

DEBUG_SENSOR

Flag for whether to send sensor error basket reports to the MMI for live display

off

INSTANTANEOUS

Flag for whether a sensor tasking command is instantaneous (as opposed to requiring an adjustment for time)

Off:w


IMRCVR

Flag for whether this code is being compiled into the rcvr executable (as opposed to the menus or other remote executable)

On for the rcvr main, off otherwise

RCVR

Flag for whether a standalone rcvr application is being employed (the alternative is to incorporate it into the wn directory). NOTE: this was an experiment, we found that maintaining a separate rcvr greatly improved the GUI response, so it's recommended to always maintain a separate rcvr.

on

MAPS_USE_SHARED_MEMORY_COMM

Flag for whether the rcvr & wn should communicate with the maps via shared memory versus using the executive.

off

MAPS_USE_POLLED_TCP_COMM

Flag for whether the rcvr & wn should communicate with the maps via standard TCP versus using the executive.

off

MAPS_USE_EXEC

Flag that the rcvr & wn should communicate with the maps via the JFORCES executive

on

MIN_RCVR

A temporary flag to generate a less-capable rcvr to minimize application investment. No longer used and not recommended since the rcvr is not a CPU hog anyway.

off

ALTERNATE_ASSET_OVERLAP

Turns on an alternate display of asset uncertainty over time. Needs to be reviewed; I suspect this is dead code

off

NETW_ANAL_DEBUG

Turns on stdout debugging data for network communications analysis (sim/comm/network_analysis.c and sim/comm/network_analysis_report.c). Expect significant performance penalty, so default is OFF.

off

BEHAVIOR_DEBUG

Turns on stdout debugging data for the behavior module. Be aware that the amount of data dumped in copious

off

STANDALONE_ANANCASE

This defines the mode for the airborne network communications transport model. Currently supported values are:

0 – There is no standalone ANCASE module, so all related messages should automatically be transmitted successfully by the core simulation

1 – There is a full-up ANCASE module employing QualNet, OpNet and any other related models

2 – Both the core simulation and an external dummy ANCASE module should be built and used. This is used for testing ANCASE scenarios and behaviors at locations without network communications models

1 for ANCASE sites, 0 elsewhere

STANDALONE_BEHAVIORS

The configures the behavior module to either be part of the core simulation, separate, or non-existent (to improve speed). Current values are:

0 – No behavior module should be built

1 – Build separate simulation and behavior modules.

2 – Build a single Simulation with behavior executable

2

SCRM_COLLECT_ONLY_ON_CHANGE

If this flag is set the DA_COMM_TEST_STATUS and DA_COMM_TEST_SERVER_USE are collected only upon data change; otherwise this data is collected for every timestep

undefined

ANCASE_MSG_START_NUM

Optional entry for the starting point for numbering ANCASE messages originating from any application. When set this is typically set in the Make.config used to create the executable. and 1000000 for any other applications. Setting this variable is recommended for any applications that initiate Msg_ANCASE messages since it helps identify the source.

When not set the default is 1 for the central data collection site (typically the sim)