Track Recorder

Introduction

These are the settings that control the recording and storing of track data in the system database. Tracks and all the individual track sightings can be recorded in real time as they are detected and tracked by the software. This is a powerful feature that enables detailed analysis of the system not only to improve performance but also analyse incidents. Witness supports easy to use queries that allow users to quickly retrieve and display historical track data so operators and engineers can see exactly why incidents occurred and to review what happened on the site.

Contents



Track Recorder

Clean Tracks Period (days): The period of time at which tracks expire and are cleaned from the database.

Track Minimum Sightings: The minimum number of sightings a track requires to be recorded and displayed. Given the radar rotate every 0.25 seconds, and each rotation has the potential for sighting a track, consecutive sightings can be calculated over time.

Batch Period (s): The time intervals between tracks data being transferred to the database in accumulated batches. 

Track Recording Mode: The type of tracks to record:

None: No tracks are recorded.

Incident: Only tracks which are been responsible for breaking a rule are recorded.

Save All: Records all tracks.

Channel Filter: Provides an optional channel filter so tracks are only recorded if they come through specific channels:

All: All channels are recorded.

Debris: Only tracks from the debris channel are recorded.

Other: When selected you will be able to enter the numeric Id of the channel from which you want to record tracks.

On large systems, the number of recorded tracks can be significant, and therefore we recommend between five to ten days as a maximum. Longer storage periods can be achieved by using the Incident Only recording mode.

In order to use the Playback track queries, track recording must be enabled, either Incident or Save All.


Related Information

Safety is everything.