WSF 1.6.1 - 29 June 2009

General

  • Updated the MTT (Multi-Target Tracker) as a result of system-level tests conducted since the release of version 1.6.0

  • Route mover types are now updated to the new mover code (previously activated with WSF_NEW_MOVER). The old mover implementations are accessible by setting the environment variable WSF_OLD_MOVER with a non-empty value.

  • The build processes have been updated so 64-bit executables can optionally be generated on Linux systems.

Corrections

  • Corrected a couple of issues with the sensor_plot’s vertical_map command that caused incorrect results to be generated if the sensor under test was airborne. The first dealt with the incorrect conversion of negative downrange values and the second was incorrectly converting the target position from ground-range/altitude to world coordinates.

    Note

    This is NOT the command used to generate the often-seen vertical coverage diagrams. That command is vertical_coverage.

  • Corrected an issue where additional sensor gains for WSF_RADAR_SENSOR’s (integration_gain, operating_loss, adjustment_factor, and pulse_compression_ratio) were not being taken into account for coherent electronic_attack jamming techniques such as WSF_FALSE_TARGET_EFFECT. These gains are now multiplied into the coherent jammer power and provided in the event_output.

  • (CR 6707) Corrected an issue that was introduced in release version 1.5.4 where an antenna pattern’s tables for some antenna_pattern types was being copied multiple times in memory for each instance causing excessive memory usage. Updated to share the tables where applicable to improve memory usage and memory limitation issues.

  • (CR 6716) Modified the ALARM antenna pattern file reader so it could process pattern files from Windows systems when running on Linux systems.

  • Corrected problem where outgoing DIS entity state velocity and acceleration were set to zero whenever a platform’s appearance was non-zero.

  • Corrected an issue when using false-targets where the beam pointing was often incorrect when performing an interaction on individual blips when the radar’s two-way interaction failed on the blip. Corrected to allow for updating of the beam positioning even upon failure so the interaction between the jammer and the radar is correct and (sidelobe) antenna gain is looked up properly.

Enhancements