Savoy Releases Patterns in Release 4.10.
Savoy has added a feature called Patterns to its complement of Video servers. A 'pattern'
refers to a region within a camera view. With this new capability, customers can specify
active regions within a camera view and to invoke particular functions whenever the camera
detects activity within the region defined by the pattern. The unique aspects of this feature
include the wide variety of functions that can be invoked from Savoy's Rule Engine, as well
as the ability to dynamically assign Patterns to cameras as described below.
Patterns can be created using the Savoy Console.
Savoy has added a feature called Patterns to its complement of Video servers. A 'pattern'
refers to a region within a camera view. With this new capability, customers can specify
active regions within a camera view and to invoke particular functions whenever the camera
detects activity within the region defined by the pattern. The unique aspects of this feature
include the wide variety of functions that can be invoked from Savoy's Rule Engine, as well
as the ability to dynamically assign Patterns to cameras as described below.
Patterns can be created using the Savoy Console.
- To create or modify a pattern, right click on a video image, select 'Server.../Patterns'
from the menu. A dialog box permits you to add/delete named patterns and to define
the active region by dragging the clicked mouse across the hatched image.
- When the server detects motion within the defined pattern, it generates an assertion
to the Rule Engine of the form 'PatternSet=name' where name is the name of the
Pattern. At regular 60 second intervals all Patterns which have been set within that
interval are cleared by the assertion 'PatternClear=name'. These assertions provide
the basis for constructing a wide variety of applications through the power of the
Rule Engine.
- When activity within a pattern invokes the rule engine, rules will fire to perform a wide
range of functions. Included in these are camera operations such as Pan/Tilt/Zoom
control, or selection of a camera preset. Rules could also sound alarms, or activate
an animation on the Control Panel.
- Other examples are dynamic connection to a remote Console through the 'Notify'
assertion. With this, operators could monitor many remote sites, connecting to them
only when a pattern region is activated.
Another function would be to transfer the video offsite, to a Repository. The
repository mat not be able to handle all of the video files, but could handle a
selection based on pattern activity.
- You can create any number of patterns and assign more than one to a given
camera. For example, one pattern could be mapped onto a doorway, while a second
could map to a sidewalk, each presenting unique assertions to the Rule Engine when
activity is detected.
- Under rules, Patterns can be dynamically assigned to a camera. For example, you
may only want to invoke a Pattern at certain times of the day, or under certain
emergency conditions. You can easily create many conceivable conditions under
which one or more Patterns should be invoked. In a rule, the 'then' side should
include the assertion 'Pattern=camera name' where 'camera' is the camera number
and 'name' is the Pattern name. For example, assert 'Pattern=5 Doorway' to assign
the Doorway Pattern to camera 5.
- PTZ Cameras have multiple 'presets' which lock the camera at a particular view.
Once positioned, it would be desireable to assign a Pattern for the system to
monitor. However, when the preset is changed, that Pattern is likely irrelevant, and a
differeent Pattern is required for the new preset view. This is easily accomplished
with rules that dynamically assign Patterns to the PTZ camera based on which preset
is selected.
 |
| |
 |
| |
 |
| |
 |
| |
 |
| |
 |
| |
 |
| |
 |
Observe many sites
across the country, a
city or campus using
the power of Savoy.
across the country, a
city or campus using
the power of Savoy.