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 13 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.10.0 Build 830 - 08 Jul 2016

New Features

  • Added controls to the Quick Command Panel to enable users to save and restore a default PPI position and zoom level. This is useful when the Sentinel MPEG recording capability is used in conjunction with a VMS because it enables the user to quickly revert the PPI to a default position and zoom level which is best for recording.
  • WIT-2754 - Added RTS plugin to the installer to enable easy integration with the RTS GPS tracking solution.
  • Added a security option which enables supervisors and administrators to disable the PPI pan and zoom for standard users. This is useful for sites using the UI in a shared Kiosk mode or where they are recording the UI in a VMS.
  • Experimental release of the Milestone VMS integration interface, This provides facilities for recording Witness alarms in Milestone to support synchronised playback and also manual override controls.

Improvements

  • Improved the default classification settings to support the HDR series of radars.
  • WIT-2764 - Change Weight on Track to represent actual weight and add new property called AdjustedWeight with old behaviour (Upgrading will use old behaviour if Weight was used in any rules)
  • Added size to the classification settings to help better distinguish between vehicles and people.
  • Added adjusted size and weight to the classification logic which helps normalise these values over the full detection range.
  • WIT-2767 - Improved the alarm locate function in Sentinel. This will now pan and zoom to an appropriate position and level in order to show all the live tracks associated with the selected alarm. Using the locate button during an incident will ensure all related tracks remain visible on screen.
  • WIT-2761 - Improved the Track Correlation logic to ensure that tracks can't be correlated / merged together unless they are from different sources or different channels from the same radar.
  • WIT-2766 - Minor improvements to Sentinel to ensure the classification probability logic is consistent across all parts of the UI.
  • Added record count and selected record count to the track results list in Sentinel to help users select the maximum number of tracks for display on the PPI.
  • WIT-2760 - Improved the ClearWay reversing rule to include the option of checking for heavy traffic on the same carriageway.
  • Ensure that the last track sighting seen in Sentinel is the last confirmed sighting and not the deleted sighting

Fixes

  • WIT-2765 - Fixed a bug in writing consolidated tracks to database is some circumstances
  • Fixed a bug with Cyclops that was preventing tracks being locked & followed correctly and was also preventing multiple tracks being selected for following.
  • Fixed a bug which meant that UI tracks which were held or retained lost their classification after the last sighting. The classification is now maintained.
  • Fixed bug in Sentinel that was causing a validation error on the longer ranges being reported by the HDR 300 series.
  • Fixed a bug in the classification logic which was preventing the model looking at track direction change and acceleration.
  • Fixed a bug in the ONVIF camera controller that was causing problems for cameras which do not support relays.
  • Fixed a bug which was causing a edit validation error in Sentinel for ranges over 1600m. This affected the new long range HDR model.
  • Fixed a bug where system was incorrectly not copying classification from later sightings when using correlation so all tracks were unclassified

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