Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

These release notes cover Witness V3.5 and above, however only release notes from version 3.6 are available. Older release notes can be found here on the Extranet.

On this page:

Version 3.11.0 Build ??? - 08 Aug 2016

New Features

  • WIT-2776 - Added option to exclude Coasted tracks from classification
  • WIT-2775 - Added option of triggering a classification reset and excluding a classification based on trigger values
  • WIT-2770 - Added ability to skip provisional tracks when classifying
  • WIT-2772 - When selecting an area it will display if Rule/Trackers are using it.
  • WIT-2747 - Milestone available from installer

Improvements

  • WIT-2769 - Added hyperlink to Area Movement Rule which enables the user to bring selected area to centre of the screen
  • WIT-2754 - Updated RTS plugin to send out deleted tracks when comms are lost to a base unit
  • Sentinel logs are now recorded in C:\ProgramData\WitnessLogs
  • WIT-2767 - Provide a location for active alarms based on a rect centre drawn around the live tracks holding the alarm ID
  • Add ability for tracker to set expiry period of track based on rotation update rate of the radar

Fixes

  • Fixed a bug for memory leak in MPJEG support in Sentinel
  • Fixed a bug to ensure that the first track sighting comes through to sentinels
  • Fixed a bug for incorrectly not copying classification from later sightings when using correlation
  • Fixed a bug where ppdated to fix deleted tracks not being sent to Sentinel

The classification settings are now optimised for the HDR 200 & 300 series radars. The critical settings should work across all models as they did before, however they should work even better for the HDR models. If you find the classification performance to be sub-optimal on older radars we would recommend reverting to the original default settings. Suitable classification configuration files can be provided if required.

  • No labels