Versions Compared

Version Old Version 18 New Version 19
Changes made by

Guy Avery (Deactivated)

Guy Avery (Deactivated)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Introduction

This section explains Rules: their purpose, the default choices and configuration.

Overview

Rules form the core intelligence of the system, permitting automatic decisions to be made based upon observed behaviour in the field. One of the great strengths of the ClearWay™ application is its ability to assist the operator by making decisions in response to sensed target movements. As a result, a continual watch can be placed upon all areas of interest, with the operator being alerted (or other actions initiated) only when particular criteria are met. The key factor in enabling such intelligent automated behaviour is the use of rules.

Rules consist of basic conditions, such as: 

  • ‘If a target enters this area then sound an alarm’ 

OR

  • ‘If a target is moving faster than 4 meters per second then follow it with a camera’.

Within ClearWay™ you can also combine two or more rules to apply very specific controls to particular regions. In addition to a set of adjustable default rules, you can also create any number of new rules using logical operators and other properties to achieve almost any desired outcome.


Panel
borderColorsilver
borderWidth1

On this page:

Table of Contents
maxLevel3
indent10px

Carriageway Wizard Rules  

When Adding a Carriageway, the Carriageway Wizard offers the opportunity to create the carriageway complete with a selection of default rules (see Configure Rules). 

  1. The first page of the wizard requires the default rules to be selected if required: 
  2. The second page of the wizard allows each default rule to be individually configured. Rule conditions form the core of each rule. The automated decision to take or not take action is determined using the properties that are combined here, and later in the Configure Rules window. Determine the choice of properties through decided what behaviour to isolate and which rule will achieve this. 


Configure Rules

There are 6 default rules:

  1. Person Rule
  2. Slow Vehicle Rule
  3. Reversing Vehicle Rule
  4. Queue Rule
  5. Debris Rule
  6. Stopped Vehicle Rule

Each is configurable, and has the ability to be switched on and off, or deleted. To configure the rules:

  1. Under the Config tab, select the Carriageway in the Entity Tree.
  2. In the configuration panel, select the ☰ options button next to Actions. 
  3. Select Rules, and a Configure Rules window will appear.

Creating a Rule

To manually create a new rule without using the wizard:

  1. In the Configure Rules window, select New.
  2. Select Rule Type:
    1. Speed Rule
    2. Queue Rule
    3. Classification Rule (can be applied to any classification, but is predominantly used for identifying Persons)
    4. Reversing Rule
    5. Track Speed Rule

  3. Select Create Rule. The new rule is now configurable as above.

    Info

    Speed, Queue, Classification and Reversing Rules are Section Rules. This means that every half second, each section is examined for evidence of these rules being broken.

    A Track Speed Rule is a Track Rule. This means that each track is individually examined as to whether it breaks this rule.

    Speed Rules and Track Speed Rules are different. A Speed Rule checks multiple tracks over time against speed parameters; i.e. looking for traffic, whereas a Track Speed Rule checks individual tracks against speed parameters. For an individual track to trigger an alarm we must be satisfied that the track is real and the rule is definitely broken, so a high break count is set. Therefore, a Track Speed Rule is therefore more suited to a Stopped Vehicle Rule.

Advanced

  1. Advanced:
    1. Break Allowance (s): alters the number of times that the rule can be broken before the defined Action is triggered. The default value of 1 will trigger an alarm at the first instance. Default: 1s or 1 hit.
    2. Use Allowance Curve: this option works in conjunction with the Break Allowance. When this option is enabled, the break count is permitted to go down as well as up. The break count will be incremented when a target is breaking the rule and then decremented when it is not. Additionally, you can set the Allowance Increment and Allowance Decrement values so that you can weight the rate at which a target increases and decreases its break count. The alarm will only be activated once the Break Allowance value is reached. This option is useful in situations where you expect targets to momentarily break rules but not to continue doing so and so prevent false alarms. Default: Disabled.
    3. Allowance Increment (s): (used only when Use Allowance Curve is enabled) Defines the amount by which the break count should be incremented every time a target breaks the rule. Default: 1s or 1 hit.
    4. Allowance Decrement (s): (used only when Use Allowance Curve is enabled) Defines the amount by which the break count should be decremented every time a target ceases to break the rule. Default: 1s or 1 hit.
    5. Relay: defines the Id of the relay that should be activated when the rule is broken. Choose ‘0’ to disable. Default: 0.
    6. Trace Logging: outputs more information about what causes the rule to break. Mainly used for carriageways with more convoluted rules. Default: Disabled.
    7. Count Coasted Tracks: select this to count coasted tracks towards the break allowance. De-select for them to be ignored. Default: Enabled.
  2. Classification Filters:
    1. Classification: optionally dedicate the rule to objects of a particular type as differentiated during the tracking process. When set to Any, the track must be classified but can be any classification. To include every track regardless of classification you must set this to Any and also select Include Unclassified. Default: Any.
    2. Classification Probability (%): allows you to optionally define a confidence level which must be matched or exceeded for a given track (of the type selected within the Classification option discussed above) before it can be considered within the rule. The use of this option provides an opportunity to filter out potential nuisance alarms. The main probability value is created during the tracking and classification process and is displayed against each entry within the Tracks tab. When this option is set to zero, the requested Classification type will be accepted at any level of probability (as determined by the tracker), rendering this filter inactive. Default: 0%.
    3. Include Unclassified: select this to include unclassified tracks as rule targets alongside the Classification filter. Default: Enabled.
  3. Alarm Suppression by Nearby Queue: this option will suppress this rule and alarm if there is a nearby queue. Either on a different carriageway, the same carriageway or both. This option is useful to reduce false alarms in one carriageway when there  is  heavy or queuing traffic in the other.
  4. Queue Detection Distance (m): how far to check for queues. This is a straight line distance from the alarm location to the nearest queue. Default: 0 m.
    5. Queue Source Filter: this is the carriageway filter which specifies on which carriageway to look for queues. Default: Other Carriageways

    .


Testing a Rule

Rules must be available to be tested to ensure that the correct alarms will be triggered when a rule is broken. In the Configure Rules window, there is a function for this exact task.

  1. Select the rule you wish to test. Then, select Test. 
  2. The Rule Test window will appear. Choose the Section and Lane you wish the alarm to be tested in, then select OK.
  3. On returning to the PPI Display, the alarm notifications will be visible (and if enabled, audible.)

Related information

Filter by label (Content by label)
showLabelsfalse
cqllabel in ("rule","rules","alarm") and space = "TUN"