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 29 Next »

These release notes cover Clearway V4.1 and above.

Version 4.1.0 Build 450 - 21 January 2019

Tracker 4.0.1.77 Release Notes / Tracker 4.0.1.82 Release Notes

Fixes

  • Fixed System layers and the layers folder being able to be deleted
  • Fixed performance issues when adding radars
  • Fixed ability to delete a carriageway with child entities
  • TUN-2599 - Fixed playback track path being very slow to move and edit
  • Modified rotation control to mouse wheel for playback track and breach line
  • Fixed issue with Section filter slider in Rule Editor being zero based not one based
  • Fixed minor issue with Highways Log Query results tab not showing record count
  • Try and stop authenticode from using the internet for revocation checks
  • Ensures the existing user does not get saved twice, as it will fail the password and hash check on the second save attempt
  • Fixed notification stating system profile changed when any system settings settings are changed

New Features

  • TUN-2377 - Added debris and other channel threshold window sizes to the radar multi-edit options
  • TUN-2429 - Added  user defined start number to POI creation tool
  • TUN-2376 - Added ability in CW to record config and update notes
  • TUN-2375 - Added ability to auto add a CW alarm exclusion area over a selected track in playback
  • TUN-2374 - Added ability to assign a track analysis status to a track from playback 
  • TUN-2579 - Added ability to assign a alarm analysis status to an alarm from playback
  • TUN-2380 - Add alarm summary dashboard with full alarm details over the previous 24 / 48 / 72 hours
  • TUN-2567 - Added (SSO) Single Sign On for use in an active directory environment

Improvements

  • Changed UI notifications for clutter floor capture and system profile change to be TE based to TrackerManager. Fixed issue where all alarm logs were using the wrong field in System Logs
  • TUN-2427 - Add to upgrade facility to enable changing distance travelled to a positive value if negative
  • TUN-2381 - Added Queue break allowance and allowance curve support
  • TUN-2378 - Improved ability to classify debris as vehicles using previous track data as a pointer
  • Rename Rule Sub Type Default to Person
  • Improved handling of errors when starting Scafell
  • TUN-2111 - There will be a distance tolerance of 2m between the center of the mouse and the contour area


Tracker Change

Please note tracker version 4.0.1.82 is only required for legacy radar support, there is no need to upgrade on board trackers from 4.0.1.77

Version 4.1.0 Build 427 - 17 December 2018

Tracker 4.0.1.77 Release Notes

Fixes

  • Fixed error in shutting down track engine when running with Unicast Discovery

Version 4.1.0 Build 423 - 13 December 2018

Tracker 4.0.1.77 Release Notes

Fixes

  • Fixed error in not sending ICD-001 Heartbeats

Version 4.1.0 Build 412 - 23 October 2018

Tracker 4.0.1.77 Release Notes

Fixes

  • Fixed inability to copy a rule

Version 4.1.0 Build 411 - 22 October 2018

Tracker 4.0.1.77 Release Notes

Fixes

  • TUN-2258 - Fixed the first row of clear buttons on the CW rule section override tab
  • Fixed Highways logs to show show correct queue data
  • Fixed playback track initial wait for track simulation
  • Fixed bug in ICD-001 (Common) where tracks were not being filtered based on TrackOutputMode
  • Fixed bug in ICD-001 to ensure broken rules are populated on ICD-001 tracks
  • TUN-2243 - Changed windows sizes to Hits from Metres in SSI settings

New Features

  • Added close following rule (Experimental)
  • TUN-2256 - Added the ability to use a CW alarm area for alarm exclusion
  • TUN-2375 - Added ability to create an alarm area from a historic track. This feature can be used to exclude alarms
  • TUN-2301 - Added an option to raise bad health alarm for radars even in the event of an intentional track engine shutdown
  • TUN-2307 - Added Per Track Alarms option to Track Speed Rules (Experimental)
  • TUN-2213 - Added ability to show start and end range rings for STC
  • TUN-2310 - Added system log for all alarm actions
  • TUN-2344 - Added ability to search for highway logs in playback
  • Added Area Info panel, enables quick access to disable/enable and help link

Improvements

  • Improved Tab styles
  • Improved reliability and performance of the VLC based camera viewer
  • Improved camera alignment process to handle live updates more effectively
  • TUN-2265 - Improved camera shape
  • TUN-2234 - Added normal track colour as a user setting
  • Added Node Id's to CSV export for OCP Plugin
  • TUN-2250 - Changed default settings for debris channel (Window Size: 25, Coast Extended Time: 10, Coast Age Min: 6, Coast Scans: 6)
  • TUN-2253 - Removed persist from ClearWay rules because its not applicable
  • TUN-2248 - Removed properties attribute from Track Classification Probability - this can be achieved using the normal rule classification settings
  • TUN-2264 - Implemented feature to hide and show height map
  • TUN-2257 - Add Ticks unit and Hits unit to advanced tab of highways rule to help identify the update increments or decrements that will be used dependent upon the update unit chosen
  • TUN-2212 - Allow maximum range to be shown in the UI on a camera by camera basis
  • TUN-2289 - Add a camera priority setting to the user account, commands with a higher priority take priority over lower
  • TUN-2306 - Improve track recording so that we don't record excessive sightings for stationary debris tracks
  • TUN-2322 - Changed colour of image pin and placed second pin in bottom right corner
  • TUN-2341 - Added channel count to radar wizard, allowing users to specify required channels. CW default remains 2
  • TUN-2373 - Added new alarm description tags for Lane Id and Carriageway Id so these can be included in the alarm output. See notes below
  • TUN-2385 - Removed requirement for Ctrl key modifier to move or add, remove nodes in areas
  • Upgraded database Mongo to 3.6.8 - see notes below

Due to the changes made for the alarm description tags, we have had to change the {LANE} tag to display the Lane Name and {LANEID} to display the Lane Id. This ensures all the tags remain consistent for carriageways, lanes and areas. A full list of tag place holders can be found here.


Version 4.1.0 Build 372 - 08 August 2018

Tracker 4.0.1.77 Release Notes

Improvements

  • Added ability for OPC to allow anonymous logins
  • Added support for refreshing the clutter map periodically for SA

In order to fully utilise the clutter map refresh facility, the Clutter Time Constant for SA should be set 100%. This will ensure data is persisted for as long as possible and will be only be absorbed during the scheduled clean up.

Version 4.1.0 Build 371 - 08 August 2018

Tracker 4.0.1.76 Release Notes

Fixes

  • Fixed Carriageway Mode and Section Mode not updating in ICD007

Improvements

  • TUN-2126 - Enable OPC events to notify clients of value changes

Version 4.1.0 Build 367 - 07 August 2018

Tracker 4.0.1.76 Release Notes

Fixes

  • Fixed incorrect handling of Date Time and Timezone in Licence files

Licence Changes

This version of software requires a new licence file to be created by Navtech.

Old licence configurations cannot be used, a new configuration is required.

After installing, the installer may have to be run again using Repair to correctly re-install all components. Please note that this must be done on all installations, not just the system hosting the UI.

Version 4.1.0 Build 366 - 06 August 2018

Tracker 4.0.1.76 Release Notes

New Features

  • TUN-2188 - Add option to backup and restore Alarm history from the database
  • TUN-2058 - Raise a notification / alarm if we identify a significant time gap between the TEs and MS
  • TUN-2068 - Added track and track sightings query exports from the playback queries
  • TUN-2068 - Added carriageway statistics and analysis exports from the playback queries
  • TUN-2190 - Added the ability to upgrade the database on system start-up to cater for more significant improvements when upgrading with future releases
  • Added ability to search for tracks of any speed in track query
  • Added ability to use Area Covered in carriageway rules as part of property filters
  • Added support for ADAM6060 DIO Unit
  • Added max network client limit for ICD-001 plugin
  • Added a new Use NTP TIme system setting. This option provides the ability to ignore NTP track time stamps coming from the radar even when they are configured. This forces the software to use the local time on the Track Engines
  • Added NTP health metric for the radar so that a alarm will be raised per radar if the NTP time stamp is significantly different to its Track Engine

It is recommended to use the new system setting to disable the use of the NTP time stamps from radar unless you are 100% confident that the NTP setup is working properly for all radar and RPUs.

Fixes

  • Fixed issue with radars sending bad NTP times causing recorded tracks to never expire
  • TUN-1996 - Disabled image controls on back image config wizard whilst image is loading from the Db so user can't load another image
  • TUN-2062 - Added option to toggle trace logging for ICD001, this stops track reports from flooding the logs
  • TUN-2106 - Updated numeric range input for playback queries and rules to handle speed conversions correctly
  • TUN-2072 - Fixed issue preventing the entering of decimal coordinate values when using the Czech keyboard/locale
  • TUN-2011 - Ensure we always save the current classification config Id on a sighting so we can always re-inflate data even if track was unclassified.
  • Fixed Licence error on restart of MS causing exception notifications in the UI
  • TUN-2115 - Fixed after doing Management server restart the system sends out multiple alarm messages
  • Fixed inability for Carriageway Profiles to be saved

Improvements

  • TUN-1931 - Modified track distance travelled to be aligned with carriageway direction instead of actual distance. This ensures distance travelled is now an accurate reflection of how far a track has moved relative to the carriageway rather than distance along the ground
  • Added option to carriageway rules to filter required distance travelled to Any direction, Forward or Reverse 
  • TUN-1989 - Made single entities stay in edit when constructed using the wizard, except for folders
  • TUN-2060 - Removed external IP address binding for the Mongo DB Service so it binds on all
  • TUN-1661 - Improved operation of drop down lists to make selections easier
  • TUN-2155 - Added ability to limit number of sightings recorded for a very long living track so that we continue to record but never exceed the specified limit
  • TUN-2057 - Added break allowance unit to carriageway wizard rules
  • TUN-2184 - Added entity GUID in entity search results and enables user to copy GUID to clipboard through mouse right click
  • TUN-2187 - Change maximum retention days for alarms to 1095 from 90
  • TUN-2070 - Fixed order for Track Engines in Topology editor
  • TUN-2071 - Added error overview for track engines and radar in topology editor. The alarm notification provides quick access to faulted track engines
  • Added support for disabling use of NTP time stamps from trackers
  • Updated Track to only use date / times from the last sighting not the deleted sighting
  • Enabled support for larger signal strengths and weights for playback tracks
  • Fixed issue with stopping MS whilst Primary Server check was in discovery with other MS's
  • A number of minor improvements and cosmetic fixes for the UI

Experimental camera support

The release contains experimental support for controlling cameras and having alarms move cameras to point at the incident. We do not recommend the use of this sub-system until it is formally released.

Distance Travelled Update

Due to the improvement of the distance travelled settings in the rules, the travelled distance setting is now always positive. Prior to this update the distance was negative (-ve) to indicate a reverse distance and positive (+ve) for a forward direction. With the improvement, the value will now always be positive (+ve). So if you previously had a negative value this must be updated to the positive equivalent.

On this page:

Related information

  • No labels

Safety is everything.