Difference: DocsSectionsReservedNames (1 vs. 8)

Revision 811 Nov 2014 - Main.PhilipVanDenBroek

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

Reserved marker and variable names

Line: 11 to 11
  The following markers have special meaning and will be inserted by BrainStream in certain situations. These marker names may not be used for other markers. However, users can define their own actions for these markers.
Changed:
<
<
BS_INIT : at startup, BrainStream inserts this marker; it will always be the first processed marker. It may be useful to associate functions that initialize your experiment with this marker, for example the initialization of certain variables.
BS_EXIT : at shutdown, BrainStream inserts this marker; it will always be the last processed marker. It may be useful to associate functions that finalize your experiment with this marker, for example saving certain variables.
BS_QUIT : this marker triggers alternative shutdown, but still guarantees a normal closing of acquisition related items. It can be used if you want to skip the actions defined for BS_EXIT.
BS_ABORT : marker triggers immediate shutdown. Do not define user actions for this marker.
BS_ACQFAILURE : marker triggers restart of acquisition after possible failure (WARNING: under construction)
>
>
BS_INIT : at startup, BrainStream inserts this marker; it will always be the first processed marker. It may be useful to associate functions that initialize your experiment with this marker, for example the initialization of certain variables.
BS_END : at shutdown, BrainStream inserts this marker; it will always be the last processed marker. It may be useful to associate functions that finalize your experiment with this marker, for example saving certain variables (Note: former BS_EXIT).
BS_ABORT : this marker triggers alternative shutdown, but still guarantees a normal closing of acquisition related items. It can be used if you want to skip the actions defined for BS_END (Note: former BS_QUIT).
 
Line: 30 to 30
 
trial information about selected data
data requested raw data, trial information, samplerate
BRAINSTREAM used by BrainStream internally
Changed:
<
<
Acq information required for acquiring data (read-only)
>
>
in specifies incoming module variables
out specifies outgoing module variables
 
trace_vars Keeps a list of traced variables (output in logfile)
brainstreamversion the version of BrainStream that was used to run the experiment

Revision 714 Nov 2011 - Main.MarjoleinVanDerWaal

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

Reserved marker and variable names

Line: 18 to 18
 

Reserved variable names

Users can create any number of user defined variables. The names must not be equal to any of the reserved names in use by BrainStream. These reserved variable names are listed below:

Changed:
<
<
markermight get confused with marker column in exp.def.table
funcs
might get confused with marker column in exp.def.table
feval
might get confused with marker column in exp.def.table
client
might get confused with marker column in exp.def.table
looptick
might get confused with marker column in exp.def.table
name
name of marker (and assoicated event)
time
time of execution referred to number of acquired samples
hdracquisition/file header info
trialinformation about selected data
datarequested raw data, trial information, samplerate
BRAINSTREAMused by BrainStream internally
Acqinformation required for acquiring data (read-only)
trace_varsKeeps a list of traced variables (output in logfile)
brainstreamversionthe version of BrainStream that you used to run your experiment
>
>
Reserved variable name Why it is reserved
marker might get confused with marker column in exp.def.table
funcs might get confused with function column in exp.def.table
feval might get confused with feval column in exp.def.table
client might get confused with client column in exp.def.table
looptick might get confused with looptick column in exp.def.table
name name of marker (and assoicated event)
time time of execution referred to number of acquired samples
hdr acquisition/file header info
trial information about selected data
data requested raw data, trial information, samplerate
BRAINSTREAM used by BrainStream internally
Acq information required for acquiring data (read-only)
trace_vars Keeps a list of traced variables (output in logfile)
brainstreamversion the version of BrainStream that was used to run the experiment
 
<---End1--->

Revision 614 Nov 2011 - Main.MarjoleinVanDerWaal

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

Reserved marker and variable names

Changed:
<
<
Generate current PDF
>
>
Generate current PDF
 
Line: 28 to 28
 
    • Set DENYTOPICVIEW =
-->
Changed:
<
<
META TOPICMOVED by="MarjoleinVanDerWaal" date="1317202953" from="BrainStream.DocsSectionsReserved" to="BrainStream.DocsSectionsReservedNames"
>
>
META TOPICMOVED by="MarjoleinVanDerWaal" date="1321266999" from="BrainStream.DocsSectionsReservedNames" to="BrainStreamDocs.DocsSectionsReservedNames"

Revision 510 Oct 2011 - Main.MarjoleinVanDerWaal

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

Reserved marker and variable names

Added:
>
>
Generate current PDF
 

Reserved marker names

Revision 430 Sep 2011 - Main.MarjoleinVanDerWaal

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

Reserved marker and variable names

Line: 20 to 20
 
markermight get confused with marker column in exp.def.table
funcs
might get confused with marker column in exp.def.table
feval
might get confused with marker column in exp.def.table
client
might get confused with marker column in exp.def.table
looptick
might get confused with marker column in exp.def.table
name
name of marker (and assoicated event)
time
time of execution referred to number of acquired samples
hdracquisition/file header info
trialinformation about selected data
datarequested raw data, trial information, samplerate
BRAINSTREAMused by BrainStream internally
Acqinformation required for acquiring data (read-only)
trace_varsKeeps a list of traced variables (output in logfile)
brainstreamversionthe version of BrainStream that you used to run your experiment

<---End1--->
Added:
>
>
<-- 
  • Access control
    • Set DENYTOPICVIEW =
-->
 
META TOPICMOVED by="MarjoleinVanDerWaal" date="1317202953" from="BrainStream.DocsSectionsReserved" to="BrainStream.DocsSectionsReservedNames"

Revision 328 Sep 2011 - Main.MarjoleinVanDerWaal

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

Reserved marker and variable names

Line: 20 to 20
 
markermight get confused with marker column in exp.def.table
funcs
might get confused with marker column in exp.def.table
feval
might get confused with marker column in exp.def.table
client
might get confused with marker column in exp.def.table
looptick
might get confused with marker column in exp.def.table
name
name of marker (and assoicated event)
time
time of execution referred to number of acquired samples
hdracquisition/file header info
trialinformation about selected data
datarequested raw data, trial information, samplerate
BRAINSTREAMused by BrainStream internally
Acqinformation required for acquiring data (read-only)
trace_varsKeeps a list of traced variables (output in logfile)
brainstreamversionthe version of BrainStream that you used to run your experiment

<---End1--->
Added:
>
>
META TOPICMOVED by="MarjoleinVanDerWaal" date="1317202953" from="BrainStream.DocsSectionsReserved" to="BrainStream.DocsSectionsReservedNames"

Revision 228 Sep 2011 - Main.MarjoleinVanDerWaal

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

Reserved marker and variable names

Line: 17 to 18
 Users can create any number of user defined variables. The names must not be equal to any of the reserved names in use by BrainStream. These reserved variable names are listed below:

markermight get confused with marker column in exp.def.table
funcs
might get confused with marker column in exp.def.table
feval
might get confused with marker column in exp.def.table
client
might get confused with marker column in exp.def.table
looptick
might get confused with marker column in exp.def.table
name
name of marker (and assoicated event)
time
time of execution referred to number of acquired samples
hdracquisition/file header info
trialinformation about selected data
datarequested raw data, trial information, samplerate
BRAINSTREAMused by BrainStream internally
Acqinformation required for acquiring data (read-only)
trace_varsKeeps a list of traced variables (output in logfile)
brainstreamversionthe version of BrainStream that you used to run your experiment
Added:
>
>
<---End1--->

Revision 126 Sep 2011 - Main.MarjoleinVanDerWaal

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

Reserved marker and variable names

Reserved marker names

The following markers have special meaning and will be inserted by BrainStream in certain situations. These marker names may not be used for other markers. However, users can define their own actions for these markers.

BS_INIT : at startup, BrainStream inserts this marker; it will always be the first processed marker. It may be useful to associate functions that initialize your experiment with this marker, for example the initialization of certain variables.
BS_EXIT : at shutdown, BrainStream inserts this marker; it will always be the last processed marker. It may be useful to associate functions that finalize your experiment with this marker, for example saving certain variables.
BS_QUIT : this marker triggers alternative shutdown, but still guarantees a normal closing of acquisition related items. It can be used if you want to skip the actions defined for BS_EXIT.
BS_ABORT : marker triggers immediate shutdown. Do not define user actions for this marker.
BS_ACQFAILURE : marker triggers restart of acquisition after possible failure (WARNING: under construction)

Reserved variable names

Users can create any number of user defined variables. The names must not be equal to any of the reserved names in use by BrainStream. These reserved variable names are listed below:

markermight get confused with marker column in exp.def.table
funcs
might get confused with marker column in exp.def.table
feval
might get confused with marker column in exp.def.table
client
might get confused with marker column in exp.def.table
looptick
might get confused with marker column in exp.def.table
name
name of marker (and assoicated event)
time
time of execution referred to number of acquired samples
hdracquisition/file header info
trialinformation about selected data
datarequested raw data, trial information, samplerate
BRAINSTREAMused by BrainStream internally
Acqinformation required for acquiring data (read-only)
trace_varsKeeps a list of traced variables (output in logfile)
brainstreamversionthe version of BrainStream that you used to run your experiment
 
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