Changes

The second column (time) specifies at which timepoints, relative to the time of the incoming marker, the actions should be executed. The exact timing of execution can be specified in several ways. The action can be executed directly at marker onset, when a certain amount of data becomes available, some time after the marker, or when another marker arrives (see table 2). For example, table 1 specifies that functions fnc1 and fnc2 are executed at the onset of marker mrk1 whereas function fnc3 takes place one second after marker onset.

The second column (time) specifies at which timepoints, relative to the time of the incoming marker, the actions should be executed. The exact timing of execution can be specified in several ways. The action can be executed directly at marker onset, when a certain amount of data becomes available, some time after the marker, or when another marker arrives (see table 2). For example, table 1 specifies that functions fnc1 and fnc2 are executed at the onset of marker mrk1 whereas function fnc3 takes place one second after marker onset.

<table bgcolor="#ffffff" cellpadding="3" border="1"><tr><td> '''EVENT''' <br /> '''DATA''' <br /> a ''number'' <br /> another ''mrk'' <br /> </td> <td> Executed at marker onset <br /> Executed as data becomes available <br /> Executed ''number'' seconds ''after'' marker onset <br /> Executed at onset of marker ''mrk'' </td></tr></table>

<table bgcolor="#ffffff" cellpadding="3" class="wikitable"><tr><td> '''EVENT''' <br /> '''DATA''' <br /> a ''number'' <br /> another ''mrk'' <br /> </td> <td> Executed at marker onset <br /> Executed as data becomes available <br /> Executed ''number'' seconds ''after'' marker onset <br /> Executed at onset of marker ''mrk'' </td></tr></table>

<em>Table 2: Specifying time of action execution<br /></em>

<em>Table 2: Specifying time of action execution<br /></em>

<div id="SecTrigger"></div>

<div id="SecTrigger"></div>

=== Trigger table ===

=== Trigger table ===

While actions give meaning to the events, the Trigger table implements the logic of the experiment program flow. It defines how each event possibly triggers the execution of other events. Conditional expressions implement runtime dependent triggered events, made possible by allowing global variables to be used in these expressions. An example would be to either trigger the <tt>next_trial</tt> event or <tt>next_sequence</tt> event based on the current state of the <tt>num_acquired_trials</tt> variable. Table 3 demonstrates corresponding Trigger table.

While actions give meaning to the events, the Trigger table implements the logic of the experiment program flow. It defines how each event possibly triggers the execution of other events. Conditional expressions implement runtime dependent triggered events, made possible by allowing global variables to be used in these expressions. An example would be to either trigger the <tt>next_trial</tt> event or <tt>next_sequence</tt> event based on the current state of the <tt>num_acquired_trials</tt> variable. Table 3 demonstrates corresponding Trigger table.