Configuring System Profiles

System profiles enable the operator to easily change the tracking parameters for the entire system at the click of a button. Currently the profiles will only change the behaviour of the trackers and the regional tracking parameters, however this is expected to be expanded in future versions to include alarm zones and rules.

A typical use of the system profile would be to de-sensitise the tracking during bad weather in order to reduce false alarms. It provides a system level configuration change which the operator can easily switch on and off. System profile settings can be applied to one or more trackers and regional parameters providing a very flexible solution.

The profile settings provide a positive or negative offset from the standard settings, not absolute values. This means it easy to adjust each tracker slightly differently for the same selected profile.

Configurable Parameters

The parameters which can be configured through a system profile are:

	Parameter	Configured Item

	Parameter	Configured Item
1	Threshold Delta	Tracker Parameters
2	STC Gain	Tracker Parameters
3	STC Range	Tracker Parameters
4	Min Plot Size in Range	Regional Tracking Parameters
5	Min Plot Size in Azimuth	Regional Tracking Parameters
6	Min Plot Amplitude for ATI	Regional Tracking Parameters
7	Min Plot Amplitude for Tracking	Regional Tracking Parameters
8	Min Plot Weight for ATI	Regional Tracking Parameters

On this page:

These settings appear in each set of tracking parameters and tracker configurations. This allows you to make changes on per-object basis, enabling each profile to be very flexible and ensures you only apply changes to the required parts of the configuration.

Only the currently actively used regional tracking parameters are updated when a system profile is changed. Other regional settings which are not assigned to a tracker are ignored.

When a profile is applied the modified settings are NOT reflected in the tracker or regional tracking parameters objects in Sentinel. All the systems settings reflect the defaults. So for example if a system profile was configured for a delta of +2 on a threshold of 18 this would give an active threshold of 20. With the same profile active, if the user changes the threshold to 20 this would result in an active threshold of 22. This change may not be immediately obvious to the user if they were not aware that a system profile was enabled.

Sensitivity Profile Settings Example

How to Use System Profiles

Enabling System Profiles

To enable System Profiles:

Navigate to the Sentinel configuration settings and find the system profiles option:
1. Main Menu -> Config-> Sentinel -> "Show System Profiles"
Edit the settings and enable the option.
Save the settings when complete.

Selecting System Profiles

Configured system profiles appear on the quick command menu. Selecting the Profiles button will expand a menu which shows the profile options.

A profile can be enabled at any time by selecting the appropriate button. To clear the selected profile, the user can select None. Only one profile (or none) can be active at any time.

When a profile is selected, the UI will display a message indicating it has been applied and the top title bar in Sentinel will show the currently selected profile:

Configuring Profiles and Profile Settings

Adding the System Profile Menu

You can add System Profile buttons as a cascading menu. The first step is to decide what buttons you want at the top level and then whether any of these buttons require sub-options. An example might be where you have profiles for extreme weather conditions. So you might have a top level button entitled "Weather" and this has two sub-options; "Storm" and "Heavy Rain". As illustrated here:

Or you could simple put the profile buttons "Storm" and "Heavy Rain" at the top level. They would be index 1 & 2 respectively and they would both have a parent index of zero.

Once you have decided on your menu structure, you need to add it to the main configuration XML file. The profile menu is part of the GlobalConfig which is part of the Piccadilly module configuration. You can safely insert the menu XML as the last element of the GlobalConfig. Using the first example of having a "Weather" top level button with a sub menu of "Storm" and "Heavy Rain" the XML would look like this:

System Profile Menu Configuration

  ...
  <SystemProfiles>
    <SystemProfile yaxlib:realtype="Witness.Framework.Core.Common.SystemProfileOption">
      <Index>1</Index>
      <ParentIndex>0</ParentIndex>
      <Name>Weather</Name>
    </SystemProfile>
    <SystemProfile yaxlib:realtype="Witness.Framework.Core.Common.SystemProfileOption">
      <Index>2</Index>
      <ParentIndex>1</ParentIndex>
      <Name>Storm</Name>
    </SystemProfile>
    <SystemProfile yaxlib:realtype="Witness.Framework.Core.Common.SystemProfileOption">
      <Index>3</Index>
      <ParentIndex>1</ParentIndex>
      <Name>Heavy Rain</Name>
    </SystemProfile>
  </SystemProfiles>
</GlobalConfig>

Assuming System Profiles are enabled, when the software is restarted, these menu options should appear in the Quick Command menu of the left-hand side of the screen. You are now ready to add the system profile settings to the tracker.

Adding the Tracker Parameter System Profile Settings

The tracking parameter settings for each profile are stored as a list per tracker. This provides the flexibility to only add the relevant profiles for the trackers that need them. If a tracker does not have the selected profile it will just use the normal configured settings Like the profile menu configuration, these settings are part of the Piccadilly module. The XML should be added within the main Tracker parameters configuration - so it would look like this:

<Tracker Id="1" TrackType="CpTrackAndBloodHound" ShowTracks="True" yaxlib:realtype="Witness.Tracker.Spx.CpTracker">
  <Params Verbose="1" Id="1">
    ...
  </Params>
  <TrackerProfileParameters>
     <TrackerProfileParameter>
          <Index>2</Index>
          <ThresholdDelta>2</ThresholdDelta>
          <STCActiveRangeWorld>20</STCActiveRangeWorld>
          <STCGainAtRange0>0.6</STCGainAtRange0>
     </TrackerProfileParameter>
     <TrackerProfileParameter>
          <Index>3</Index>
          <ThresholdDelta>4</ThresholdDelta>
          <STCActiveRangeWorld>60</STCActiveRangeWorld>
          <STCGainAtRange0>0.4</STCGainAtRange0>
     </TrackerProfileParameter>
  </TrackerProfileParameters>
  <AutoStart>True</AutoStart>
    ...
</Tracker>

There are two profiles configured in this example; in this case they match the Storm and Heavy Rain profiles (Indexes 2 and 3 respectively) which we configured in the System Profile Menu.

Adding the Area Tracking Parameter System Profile Settings

Like the tracking parameter settings, the regional tracking profile settings need to be added to each tracking parameters object. By default, this only applies to the Default and Partial Exclusion settings. However if you've added your own tracking parameters then you'll need to update these as required.

The XML for system profiles needs to be added to the main parameters configuration. It can be placed before the closing TrackerRegion tag. It should look like this:

<TrackerRegion Id="1" Name="Default" yaxlib:realtype="Witness.Tracker.Spx.TrackerRegionParams">
   <AssocMask>15</AssocMask>
   ...
   <UniqueId>60626a9c-987c-4287-b618-d84042a2af49</UniqueId>
   <TrackerRegionSystemProfileParameters>
      <TrackerRegionSystemProfileParameter yaxlib:realtype="Witness.Tracker.Spx.TrackerRegionSystemProfileParams">
         <Index>2</Index>
         <MinPlotRangeSize>0</MinPlotRangeSize>
         <MinPlotAzimuthSize>0</MinPlotAzimuthSize>
         <MinPlotAmplitudeATI>4</MinPlotAmplitudeATI>
         <MinPlotAmplitudeTrack>2</MinPlotAmplitudeTrack>
         <MinPlotWeightATI>3</MinPlotWeightATI>
       </TrackerRegionSystemProfileParameter>
      <TrackerRegionSystemProfileParameter yaxlib:realtype="Witness.Tracker.Spx.TrackerRegionSystemProfileParams">
         <Index>3</Index>
         <MinPlotRangeSize>0</MinPlotRangeSize>
         <MinPlotAzimuthSize>0</MinPlotAzimuthSize>      
         <MinPlotAmplitudeATI>3</MinPlotAmplitudeATI>
         <MinPlotAmplitudeTrack>1</MinPlotAmplitudeTrack>
         <MinPlotWeightATI>2</MinPlotWeightATI>
       </TrackerRegionSystemProfileParameter>
   </TrackerRegionSystemProfileParameters>
</TrackerRegion>

In line with the other examples on this page, we have illustrated the two configured profiles, Storm and Heavy Rain (Indexes 2 and 3 respectively) being added to the Default tracking parameters.