Difference: DocsSectionsBuildingExperiments (8 vs. 9)

Revision 927 Sep 2011 - Main.MarjoleinVanDerWaal

Line: 1 to 1
 
META TOPICPARENT name="BrainStreamDocs"

Building Experiments

Line: 21 to 21
 
  1 fnc3      
mrk2,mrk3 EVENT fnc4      
Changed:
<
<
Table 1: Actions table

The first column of the Actions table, the marker column, contains the names of all markers that elicit the execution of certain actions. If actions for the same marker are listed in different rows of the table, the marker name only needs to be specified in the first row. For example, in table 1, the actions for marker mrk1 are specified in two different rows, and the marker column can remain empty for the second of these rows. Multiple markers can be specified, separated by commas. Any of the markers from this list will trigger the execution of the associated actions. For example, in table 1, function fnc4 will be executed whenever either marker mrk2 or mrk3 arrives. The marker column can also contain a reference to another table (see Plug-ins).
>
>
Table 1: Actions table

The first column of the Actions table, the marker column, contains the names of all markers that elicit the execution of certain actions. If actions for the same marker are listed in different rows of the table, the marker name only needs to be specified in the first row. For example, in table 1, the actions for marker mrk1 are specified in two different rows, and the marker column can remain empty for the second of these rows. Multiple markers can be specified, separated by commas. Any of the markers from this list will trigger the execution of the associated actions. For example, in table 1, function fnc4 will be executed whenever either marker mrk2 or mrk3 arrives. The marker column can also contain a reference to another table (see Plug-ins).
  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.
Line: 65 to 65
  The first three columns of the Dictionary table are fixed. In the marker column the marker names are specified. The second column specifies the marker type. The marker can for example be a stimulus or a response marker. The value column specifies the number with which the marker is represented outside BrainStream.
Changed:
<
<
The substitute and datasource columns are optional. More information about the substitute column can be found in the Plug-in section. If multiple data sources are used in the experiment, the datasource column specifies for which data source the dictionary information is meant. If only one datasource is involved, this column can be left out and BrainStream will apply the definitions to the single data source.
>
>
The substitute and datasource columns are optional. More information about the substitute column can be found in the Plug-in? section. If multiple data sources are used in the experiment, the datasource column specifies for which data source the dictionary information is meant. If only one datasource is involved, this column can be left out and BrainStream will apply the definitions to the single data source.
 
marker type value substitute datasource
tone stimulus 10    
Line: 78 to 78
 

Preventing conflicts with plug-in tables

Changed:
<
<
BrainStream supports the use of Plug-in tables. An example of a plug-in table is the plug-in for bad channel detection. Alternatively, it is possible to build your own plug-in table. Any plug-in itself consists of an Action, DataSelection and Dictionary table.
>
>
BrainStream supports the use of plug-in tables. An example of a plug-in table is the plug-in for bad channel detection. Alternatively, it is possible to build your own plug-in table. Any plug-in itself consists of an Action, DataSelection and Dictionary table.
 
Changed:
<
<
When BrainStream is started, all experiment definition tables that are used in the experiment - including the plug-in 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 shoud not conflict. For example, you should prevent double definitions of marker names or numbers.
>
>
When BrainStream is started, all experiment definition tables that are used in the experiment - including the plug-in 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 shoud 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