Difference: DocsSectionsBuildingExperiments (32 vs. 33)

Revision 3318 Nov 2014 - Main.PhilipVanDenBroek

Line: 1 to 1
 
META TOPICPARENT name="WebHome"
<---Start1--->

Building Experiments

Line: 48 to 48
 
trial EVENT next_trial eeg 0 num_acquired_trials <= 10
trial EVENT next_sequence eeg 0 num_acquired_trials > 10
Changed:
<
<
Table 4: Trigger table
>
>
Table 3: Trigger table
 
Changed:
<
<
As long as the number of acquired trials doesn't exceed 10, a next_trial event is triggered by the trial event, otherwise a next_sequence event is triggered. If no conditional expression is specified, corresponding event will always be triggered. Optionally, a delay can be specified, which value is default referenced relatively against the events timepoint time that triggers it. If it should be referenced against actual moment of execution of the event, instead specify for the delay: 0,'now'. The datasource is only relevant if corresponding triggered event defines data (it has a DATA timepoint) in order to collect the correct data epochs. For example useful if a single marker triggers periodic data collection or a limited number of data epochs as determined by logic incorporated in the conditional expression.
>
>
As long as the number of acquired trials doesn't exceed 10, a next_trial event is triggered by the trial event, otherwise a next_sequence event is triggered. If no conditional expression is specified, corresponding event will always be triggered. Optionally, a delay can be specified, which value is default referenced relatively against the events timepoint time that triggers it. If it should be referenced against actual moment of execution of the event, instead specify for the delay: 0,'now'. The datasource is only relevant if corresponding triggered event defines data (it has a DATA timepoint) in order to collect the correct data epochs. For example useful if a single marker triggers periodic data collection or a limited number of data epochs as determined by logic incorporated in the conditional expression.
 
Line: 93 to 93
 

Preventing conflicts with imported tables

Changed:
<
<
BrainStream supports the use of imported tables. Alternatively, it is possible to build your own imported table.

When BrainStream is started, all experiment definition tables that are used in the experiment - including the imported tables - are combined in a process called table expansion. This means that all Action tables will be integrated into a single Action table, and the same is true for the DataSelection and Dictionary tables. Importantly, the information in the individual tables should not conflict. For example, you should prevent double definitions of marker names or numbers in the Dictionary tables.

>
>
BrainStream supports the use of imported tables. When BrainStream is started, all experiment definition tables that are used in the experiment - including the imported tables - are combined in a process called table expansion. This means that all Action tables will be integrated into a single Action table, and the same is true for the DataSelection and Dictionary tables. Importantly, the information in the individual tables should not conflict. For example, you should prevent double definitions of marker names or numbers in the Dictionary tables.
 
 
This site is powered by the TWiki collaboration platformCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback