Polybench® Reference
Triggers an event containing data captured from the Data input with a user EventCode if the Trigger input becomes 1.0 or greater.

Event Data Trigger


Use this operator to insert events markers into a signal. The events may contain additional data that is captured from the top input. The event marker creation is controlled by a signal trigger.

Operator ports

Input S: Floating point values

Input Trigger: Floating point values

Input Data: Floating point values

Output S: Floating point values


Find more information about changing properties here: link

type: See description
A free-format code that will be added as Data Event to the signal when the trigger input is 1.0 or greater. The code may contain variables, and the special variable $IN[n]$.

Read more about variables here: link. Please note that variables are not always updated synchronously with data processing. This means that in some cases a variable may not yet contain the value that you expect it to have, at the time you trigger an event.

You may use the special variable $IN[n]$, where n is the channel number (1..N), meaning the value of the nth channel of the regular input signal at the moment of triggering. If you specify a channel that does not exist, or you don't have a floating point signal connected to the input (but another kind of signal), then $IN[n]$ will be substituted by xxxxx.
If you make an error in the syntax of the variable, you will see ?????. Please note that n must be a value, and cannot be a variable itself.

type: See description
The way the captured value is represented in the event marker, e.g.: '.1' for one digit and a decimal point, or ',3' for a time value with three digits and a decimal comma.

For more information about Number Format codes, please refer to link.

type: Word or phrase
The name of the object in the project. This name must not contain '.' or '$' characters.

Every object has the Caption property. This property is very important, because it is the name by which Polybench recognizes this object.
It is allowed to give multiple objects the same name, as long as the objects are of the same type. In that case, a reference to this caption includes all the objects with the same caption.
In Polybench, every object can be addressed by an Address specifier, which starts with the dollar sign, for example: $My Page.My Object. 'My Page' would be the Caption of a page, and 'My Object' the Caption of an object on that page.

type: See description
Optional documentation of this object.

It is good practice to write in short notes why you have used this object, and why its properties are set the way they are set. If this object is an operator, the Documentation text is displayed below the operator symbol.

Variable Parameters

Find more information about Variable Parameters here: link

type: See description
A free-format code that will be added as Data Event to the signal when the trigger input is 1.0 or greater.


For more information about the eventing concept of Polybench, see link.

The Event Data Trigger allows you to add an event marker with captured values to the signal. The signal runs unchanged through the operator, until a trigger on the bottom-input generates a new event marker that is then tagged to the signal.

At that moment, the input values of the top input (Data) are captured and are included in the new event marker. Some other operators are able to read those captured values, for example the Event Information (link) or the Marker Viewer (link).

To trigger the creation of an event marker with captured values, the bottom input should detect a signal with a value greater than 1.0. The first time that happens, will trigger the event.

The event marker will be attached to the sample that flew through the Event Data Trigger operator, at the moment the triggering took place. The data event will stay attached to the sample until it is filtered out.

Note that you can connect only one channel to the Trigger (bottom) input of the Event Data Trigger, because all signal channels share the same event marker.

The EventCode can be changed in the properties dialog, but also using the Variable Parameter EventCode, so that you can change the EventCode from within an application.


Example: Event Data Trigger Demo
Demonstrates how an Event Data Trigger captures values from a noise signal on three channels. A Marker Viewer table shows the markers including the captured values they contain.