Witness V3.11.x Release Notes

Owned by Benedict Dakin-Norris (Unlicensed)
Last updated: Sept 25, 2017 by Guy Avery (Deactivated)
2 min read

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 849 - 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 the first N provisional tracks when classifying

  • WIT-2772 - When selecting an area it will display if Rule/Trackers are using it.

  • WIT-2747 - Experimental release of the Milestone available from installer

  • WIT-2773 - Added ruler with distance and angle

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 - see note below

  • Stopped the clutter floor from loading during a tracker update and causing false alarms

Fixes

  • Fixed a bug for memory leak in MPJEG support in 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.



The Sentinel logs have been moved to the recommended location for applications running on the later versions of Window. This is C:\ProgramData\WitnessLogs. In version 3.9.x we changed the logic to store the logs in the user's profile but this is not helpful because log data was being split across multiple folders. So now all Sentinel logs, regardless of user, will use the same log folder.