The FLAMES Analysis option includes features for Enhanced Analysis and Sensor Coverage.
FLAMES® provides exceptional support for analytical simulation, including system design modeling, parametric trades studies, and Monte-Carlo simulation. Using FLAMES you can compress weeks or months of effort in conducting simulation-based analysis into just a few days.
The foundation for FLAMES support for analytical simulation is scenario variables. You can use a scenario variable to specify the value of almost any scenario input parameter. For example, the range of a sensor, the type of missile to be used by a fighter aircraft, the location of a target, the type of tactics to be employed, and the seed of a random number generator can be specified using scenario variables rather than constant values. A scenario can include any number of scenario variables, and you can choose the name, data type, and default value for each variable.
When a scenario is defined that includes scenario variables, the values of the variables can be specified when the scenario is executed. Using this capability, a single scenario can be executed multiple times in order to determine results based on different sets of scenario variable values.
The values of scenario variables can be specified in several ways:
- Values can be defined within the scenario in tables as a function of “run number”. One or more run numbers are then specified when the scenario is executed. If multiple run numbers are specified, a single execution of FIRE will automatically execute each run.
- Values can be defined in experiment files. An experiment file can specify a set of values for all variables for multiple runs of the scenario. You can create an experiment file manually using a text editor or a spreadsheet program, or you can create one automatically using a third-party “design of experiments” tool, such as JMP® from SAS®. An experiment file and one or more run numbers can then be specified when the scenario is executed. If multiple run numbers are specified, a single execution of FIRE will automatically execute each run.
- Values can be defined in a third-party design of experiments tool. The tool can then be used to execute FIRE automatically and provide a new set of values to FLAMES dynamically each time it is executed.
FLAMES also includes a robust, flexible, and customizable data recording capability to capture scenario execution results and write them to user-specified output files. These output files can be processed in a number of different data analysis programs.
FLAMES Sensor Coverage allows you to evaluate and visualize the coverage provided by the sensors deployed in a scenario inside FORGE. Sensor Coverage can also be used to help position the sensors deployed in a scenario to improve their detection coverage.
Sensor coverage calculations are performed by invoking the detection algorithms of a user-selected set of sensors in a scenario. For each sensor, the detection algorithm is invoked for a target located at many locations distributed throughout a specified coverage area in either a radial or grid pattern. A graphical image is then displayed in the FORGE 2D View that represents the locations at which the target could be detected.
The Analysis option is enabled without a runtime license in FORGE or FIRE if the application is executing with only the bundled components loaded. Therefore, you can try it out using the free copy of the Runtime Suite. If custom component plug-ins are loaded, a runtime license to the Analysis option is required to enable the option. Runtime licenses must be purchased separately. In addition, ALL of the custom component plug-ins loaded by the application must have been developed on computers that were licensed for the Analysis development option.
An Analysis option development license is required in order to create custom component plug-ins using the FLAMES Development Suite that support the option. Development licenses must be purchased separately. As stated above, the functionality of the Analysis option is enabled in an application only if ALL of the component plug-ins loaded by the application were developed on computers that were licensed for the Analysis development option.