Difference: DocsSectionsGlossary (1 vs. 19)

Revision 1921 Nov 2011 - Main.MarjoleinVanDerWaal

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

Glossary

Line: 31 to 31
  BCI Brain-computer interface
Changed:
<
<
Block Experiments are divided into different functional blocks. Every block can have a different purpose, e.g. one block for training, one for online feedback, etc.
>
>
Block Experiments are divided into different functional blocks. Each block can have a different purpose, e.g. one block for training, one for online feedback, etc.
  Block file (.blk) To initialize your experiment in BrainStream, you need to compose at least one block file. Each block has its own block file, which contains or refers to all information needed to initialize the particular block.

Revision 1814 Nov 2011 - Main.MarjoleinVanDerWaal

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

Glossary

Changed:
<
<
Generate current PDF
>
>
Generate current PDF
  A - B - C - D - E - F - G - H - I - J - K - L - M - N - O - P - Q - R - S - T - U - V - W - X - Y - Z

Revision 1714 Nov 2011 - Main.MarjoleinVanDerWaal

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

Glossary

Line: 52 to 52
  Data selection The selection of data segments from the data stream source.
Changed:
<
<
!DataSelection table The DataSelection table specifies which markers trigger data selection.
>
>
DataSelection table The DataSelection table specifies which markers trigger data selection.
  Debug A run mode which allows step-wise execution of programmed code. For example, when debug mode is enabled and a break point is set in Matlab, the experiment will pause at the breakpoint.
Line: 226 to 226
 
  • Access control
    • Set DENYTOPICVIEW =
--> \ No newline at end of file
Added:
>
>
META TOPICMOVED by="MarjoleinVanDerWaal" date="1321266634" from="BrainStream.DocsSectionsGlossary" to="BrainStreamDocs.DocsSectionsGlossary"

Revision 1621 Oct 2011 - Main.MarjoleinVanDerWaal

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

Glossary

Line: 179 to 179
  Structure A Matlab type variable that manages to keep a collection of (closely related) variables as sub-fields of its own.
Changed:
<
<
Subject: Participant in an experiment.
>
>
Subject Participant in an experiment.
 
Line: 198 to 198
  User defined variable A global variable that is defined by the user. It can be used to exchange information between different events.
Changed:
<
<
User state See global variables
>
>
User state See global variables
 

Revision 1520 Oct 2011 - Main.MarjoleinVanDerWaal

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

Glossary

Line: 198 to 198
  User defined variable A global variable that is defined by the user. It can be used to exchange information between different events.
Added:
>
>
User state See global variables
 

V

Revision 1420 Oct 2011 - Main.MarjoleinVanDerWaal

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

13 Glossary

>
>

Glossary

  Generate current PDF
Changed:
<
<
>
>
A - B - C - D - E - F - G - H - I - J - K - L - M - N - O - P - Q - R - S - T - U - V - W - X - Y - Z
 

A

Deleted:
<
<
ActiView: Software responsible for acquiring, saving and optional transmitting data from BioSemi's Active2 EEG amplifier.
 
Changed:
<
<
Acquisition: The process of collecting data/information from a device.
>
>
Acquisition The process of collecting data/information from a device.
 
Changed:
<
<
Acquisition computer: The computer responsible for managing the data acquisition.
>
>
Acquisition computer The computer responsible for managing the data acquisition.
 
Changed:
<
<
Audio Midi Setup:See MIDI
>
>
Action Actions can be one of the following: modifying variables, retrieving or storing variables from the global variables (get, put) or from disk (load, save), or executing functions.
 
Changed:
<
<
Action: An action can be one of the following: modify, get or load, function, put or save. See corresponding items in this glossary.
>
>
Actions table The Actions table specifies the actions that should be executed for each marker.
 
Changed:
<
<
Application (of BrainStream):
>
>
ActiView Software responsible for acquiring, saving and optional transmitting data from BioSemi's Active2 EEG amplifier.
 
Changed:
<
<
Argument: Functions can be given extra information as input to start with, these are called arguments.
>
>
Argument A variable on which a function operates.

Audio Midi Setup See MIDI

 

B

Deleted:
<
<
Block: Every session is divided into different functional blocks. Every 'block' can have a different purpose, e.g. one block for training, one for online feedback, etc.
 
Changed:
<
<
Block file: To initiate your experiment in BrainStream, you need to compose an initialization run file(s), also called a block file. Every block has a separate file, which contains or refers to all information needed to initiate the particular block.
>
>
BCI Brain-computer interface

Block Experiments are divided into different functional blocks. Every block can have a different purpose, e.g. one block for training, one for online feedback, etc.

 
Changed:
<
<
Brainstream: BrainStream is a Matlab-based toolbox that allows you to run and analyse EEG experiments in a modular way. For a more elaborate description see the introduction of the documentation
>
>
Block file (.blk) To initialize your experiment in BrainStream, you need to compose at least one block file. Each block has its own block file, which contains or refers to all information needed to initialize the particular block.

Brainstream BrainStream is a Matlab-based toolbox that allows you to run and analyze BCI experiments in a modular way.

 

C

Changed:
<
<
Common block file: A special type of block file. Common block files contain or refer to information that is needed in all blocks of the experiment. For example, a common block file might contain information that is specific to the lab in which the experiment takes place.
>
>
Common block file A special type of block file. Common block files contain or refer to information that is needed in all blocks of the experiment. For example, a common block file might contain information that is specific to the lab in which the experiment takes place.
 
Changed:
<
<
Constants (in user-defined functions): User functions can take additional (only constant) arguments besided the obligatory first event argument.
>
>
Constants (in user defined functions) User defined functions can take constants as input arguments after the obligatory first argument 'event'.
 

D

Changed:
<
<
Data segment: A limited amount of data from the data stream source.
>
>
Data segment A limited amount of data from the data stream source.

Data selection The selection of data segments from the data stream source.

 
Changed:
<
<
Data selection: The amount of data the user selects from the data stream source.
>
>
!DataSelection table The DataSelection table specifies which markers trigger data selection.
 
Changed:
<
<
Dictionary: Defines interface between source dependent marker information (type and value) and marker names used in BrainStream.
>
>
Debug A run mode which allows step-wise execution of programmed code. For example, when debug mode is enabled and a break point is set in Matlab, the experiment will pause at the breakpoint.
 
Changed:
<
<
Debug: A run mode which allows step-wise execution of programmed code.For example, when setting break points in Matlab and enabled debug mode, the experiment will stop running and Matlab waiting for you to check the code and continue the experiment by pressing 'F5' on the keyboard.
>
>
Decimation The technique of reducing the number of samples of a signal by first low-pass filtering (in order to remove aliasing effects) and then downsampling the signal.
 
Changed:
<
<
Decimation: The technique of reducing the number of samples of a signal by first low-pass filtering (in order to remove aliasing effects) and then downsampling the signal.
>
>
Default variables The value that a variable will take if its content is not otherwise specified.
 
Changed:
<
<
Default variables: Variables for which no content is defines will take the default value.
>
>
Dictionary table The Dictionary table translates between the marker names used in BrainStream and the source dependent marker information (type and value).
 

E

Deleted:
<
<
Event: Markers become events when received. Events have rich structure and can be regarded objects with data (optional), variables, and actions with different moments of execution relative to the onset of the event. Every subsequent same marker in the data stream instantiates a new event.
 
Changed:
<
<
Experiment: Most BCI experiments involve measurement of several different subjects. Also, BCI experiments can consist of multiple measurements using the same subject each time (i.e. 'sessions'). Every session is divided into different functional blocks. Every 'block' can have a different purpose, e.g. one block for training, one for online feedback, etc. Every block consists of a set of several 'sequences'. Every sequence is self-paced meaning that the participant can push a button to start the next sequence. A sequence is defined as a succession of certain stimuli (e.g. a sequence of tones to generate an auditory evoked potential or a sequence of different motor imagery tasks). These stimuli can be named 'tones', 'trials', 'stimuli', 'epochs', etc. If you take these definitions into account, the hierarchical structure of a common BCI experiment summarizes to 'Experiment' --> 'Subject' --> 'Session' --> 'Block' --> 'Sequence' --> 'Stimulus'. These definitions will be used throughout this documentation. Moreover, this hierarchical structure can serve as a template to arrange locations for data storage.
>
>
Event Every marker in the data stream instantiates a new event. During an event, one or more actions can be executed at one or more different timepoints.
 
Changed:
<
<
Experiment definition file: The file that defines the actions for the markers involved in the experiment. This file can also be regarded: the collection of tables that together define the entire experiment.
>
>
Event structure a Matlab structure variable that contains all information associated with an event, for example the actions that should be executed, the variables that are required for the actions and the data that is selected during the event.
 
Changed:
<
<
Experiment definition table: One that defines actions for some markers involved in the experiment. A collection of tables together define the entire experiment, see experiment definition file.
>
>
Experiment All blocks together form the experiment.
 
Changed:
<
<
Experiment file: If experiments involve execution of several blocks, references to those blocks can be put together in a single text file, in which every .blk file is denoted in one row. The text file has to be saved with the extension .exp.
>
>
Experiment definition file (.edt or .xls) A file that contains all experiment definition tables.

Experiment definition table One of the tables that define the experiment. Includes the Actions, DataSelection, and Dictionary tables.

Experiment file (.exp) Text file that contains references to all block files and common block files of the experiment.

 

F

Changed:
<
<
Field:

Fieldtrip: Fieldtrip is a Matlab software toolbox for MEG and EEG analysis that is being developed at the Centre for Cognitive Neuroimaging of the Donders Institute for Brain, Cognition and Behaviour together with collaborating institutes. For more information see http://fieldtrip.fcdonders.nl/

>
>
FieldTrip FieldTrip is a Matlab software toolbox for MEG and EEG analysis that is being developed at the Centre for Cognitive Neuroimaging of the Donders Institute for Brain, Cognition and Behaviour together with collaborating institutes. For more information see http://fieldtrip.fcdonders.nl/
 
Changed:
<
<
Function:A function generates and delivers output with respect to the received input.
>
>
Function A function takes input arguments and transforms them into output.
 

G

Changed:
<
<
'Get' statement: Use this statement to retrieve a copy of the current content of a user variable from the global variables. The name of the variable will showup as a field in the event structure.
>
>
'Get' statement Statement to retrieve a copy of the current content of a user defined variable from the global variables. The name of the variable will be copied into a field of the event structure.
 
Changed:
<
<
Global variables: All variables defined as headers (except marker, time, function and client) in experiment definition tables. Their content is maintained by BrainStream and can be retrieved (get) or updated (put).
>
>
Global variables Variables of which the content is maintained throughout the block.
 
Changed:
<
<
Graphical User Interface (GUI): User friendly interface that can be used to start experiments with feedback about performance and currently executed actions.
>
>
Graphical User Interface (GUI: User interface that can be used to start experiments and show feedback about performance and currently executed actions.
 
Line: 96 to 103
 

I

Added:
>
>
Initialization run file See block file
 

J

Line: 104 to 113
 

K

Changed:
<
<
Key: Users can define their own constants in the block file (see glossary). They should be added to an existing or new topic (see glossary) and assignments follow Matlab symantics.
>
>
Key In the block file, settings can be specified under keys. The keys should be added to an existing or new topic and assignments must follow Matlab semantics.
 

L

Changed:
<
<
'Load' statement: Instead of retrieving user variables from the global variables, it can also be retrieved from a previous executed block by specifying the load instead of the get action for corresponding variable. A previous block should of course have made content available via the save keyword for the same variable.
>
>
'Load' statement Retrieves the content of user defined variables from disk. The content must be stored on disk with a save statement for the same variable in a previously executed block.
 

M

Changed:
<
<
Markers: Specify some specific timepoint in the data stream which trigger BrainStream to execute possible defined actions (process data, update/modify information, give feedback). The way marker information is provided to BrainStream depends on the datasource in use. Therefore, a dictionary serves to translate markers into marker names which can then be processed independent of the utilized data source.

Matlab: http://www.mathworks.com/products/matlab/ : MATLABŪ is a high-level language and interactive environment that enables you to perform computationally intensive tasks faster than with traditional programming languages such as C, C++, and Fortran.

>
>
Markers Specify a timepoint in the data stream and may trigger BrainStream to execute certain actions or select data.
 
Changed:
<
<
Midi: Midi (Musical Instrument Digital Interface) is a protocol which allows communication between different computers interface. Midi transmits event messages and thus no media signal such as audio.
>
>
Matlab MATLABŪ is a high-level language and interactive environment that enables you to perform computationally intensive tasks faster than with traditional programming languages such as C, C++, and Fortran.
 
Changed:
<
<
MMM Lab: The lab of the Music, Mind, Machine group at Radboud Universiteit, Nijmegen.
>
>
MIDI (Musical Instrument Digital Interface) A protocol which allows for communication between different computers. MIDI transmits event messages and thus no media signal such as audio.
 
Changed:
<
<
Modify: BrainStream actually executes something when it encounters one of the following actions: modify, get or load, functions, put or save. The modify action permits users to directly change content of a global variable, which is especially useful for simple modifications. That is, you do not first need to retrieve a copy from the global variables (get action), change its content, and then update it (put action). Note that modify actions will always be executed first (the order is: modify, get or load, functions, put or save).
>
>
MMM Lab The lab of the Music, Mind, Machine group at Radboud Universiteit, Nijmegen.
 
Changed:
<
<
Modules:
>
>
Modify The modify action permits users to directly change content of a global variable from the Actions table. For a modify action, the variable does not have to be retrieved from the global variables (get action), changed, and updated again (put action).
 
Line: 139 to 146
 

P

Changed:
<
<
>
>
Path A path refers to the location of a folder on a hard drive. In many programs, such as Matlab, the path specifies the folders in which the programs searches for files (e.g. functions).
 
Changed:
<
<
Path: A path refers to the location of a folder on a drive. In many programs, such as Matlab, a path can be set in which the programs searches for definitions or functions to be used. By setting the path, these functions and definitions become easily accessible.

'Put' statement: Use this statement to update content of a user variable to the global variables. The name of the variable should exist as a field in the event structure.

>
>
'Put' statement This statement updates the content of a user defined variable to the global variables. The name of the variable should exist as a field in the event structure.
 
Line: 156 to 161
 

S

Changed:
<
<
'Save' statement: Instead of updating user variables to the global variables, it can also be stored to disk via the save instead of the put keyword for corresponding variable. A subsequent/future block can then retrieve this information via a load keyword on corresponding variable.
>
>
'Save' statement This statement stores the content of a user defined variable to disk. A future block can retrieve this content via a load statement on the corresponding variable.

Screen Sharing A feature that allows you to access and control another remote computer by showing its screen content and directing your mouse/keyboard inputs to this device.

 
Changed:
<
<
Screen Sharing: A feature that allows you to access and control another remote computer by just showing its screen content and directing your mouse/keyboard inputs to this device.
>
>
Sequence A sequence is defined as a succession of certain stimuli (e.g. a sequence of tones to generate an auditory evoked potential or a sequence of different motor imagery tasks). Multiple sequences form a block.
 
Changed:
<
<
Sequence: Every block consists of a set of several 'sequences'. Every sequence is self-paced meaning that the participant can push a button to start the next sequence. A sequence is defined as a succession of certain stimuli (e.g. a sequence of tones to generate an auditory evoked potential or a sequence of different motor imagery tasks).
>
>
Server Computer running BrainStream.
 
Changed:
<
<
Server: Computer running BrainStream.
>
>
Sessions Multiple measurements with the same subject.
 
Changed:
<
<
Session: Multiple measurements using the same subject each time.
>
>
Stimulus A detectable change in the environment, for example a light flash or a tone. Multiple stimuli form a sequence.
 
Changed:
<
<
Stimuli: 'tones', 'trials', 'stimuli', 'epochs', etc.
>
>
Stimulus computer The computer responsible for generating or presenting the stimuli to the subject.
 
Changed:
<
<
Stimulus computer: The computer responsible for generating or managing the stimuli.
>
>
String Textual information enclosed by quotes.
 
Changed:
<
<
String: Some textual information enclosed by quotes.
>
>
Structure A Matlab type variable that manages to keep a collection of (closely related) variables as sub-fields of its own.
 
Changed:
<
<
Structure: A Matlab type variable that manages to keep a collection of (closely related) variables as sub-fields of its own.
>
>
Subject: Participant in an experiment.
 

T

Changed:
<
<
Terminal:
>
>
Time point (of actions) Moment in time relative to the onset of a marker.
 
Changed:
<
<
Time point: e.g. DATA, EVENT
>
>
Topic In the block file, keys that define settings must be organized under topics.
 
Changed:
<
<
Topic: Users can define their own constants in the block file. They should be added to an existing or new topic and assignments follow Matlab symantics.

Trunk: The trunk is the main line of a program development in a group-shared repository.

>
>
Trunk The trunk is the main line of a program development in a group-shared repository.
 

U

Changed:
<
<
User-defined functions: Users can write their own MATLAB functions which can be called within an Experiment when an event occurs.
>
>
User defined function Users can write their own Matlab functions which can be called during the Experiment.
 
Changed:
<
<
User variable: A variable that is defined by the user. It can be used to exchange information between different events.
>
>
User defined variable A global variable that is defined by the user. It can be used to exchange information between different events.
 

V

Changed:
<
<
Variables:

Verbosity level:

>
>
Variable A symbolic name given to some quantity or information. The content of a variable can change.
 
Line: 208 to 211
 

X

Deleted:
<
<
X11:
 

Y

Revision 1310 Oct 2011 - Main.MarjoleinVanDerWaal

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

13 Glossary

Added:
>
>
Generate current PDF
 

Revision 1220 Sep 2011 - Main.MarjoleinVanDerWaal

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

13 Glossary

Added:
>
>
 

A

ActiView: Software responsible for acquiring, saving and optional transmitting data from BioSemi's Active2 EEG amplifier.
Line: 20 to 22
  Argument: Functions can be given extra information as input to start with, these are called arguments.
Added:
>
>
 

B

Block: Every session is divided into different functional blocks. Every 'block' can have a different purpose, e.g. one block for training, one for online feedback, etc.
Changed:
<
<
Block file: To initiate your experiment in BrainStream, you need to compose an initialization run file(s), also called a block file. Every block has a separate file, which contains or refers to all information needed to initiate the particular block.
>
>
Block file: To initiate your experiment in BrainStream, you need to compose an initialization run file(s), also called a block file. Every block has a separate file, which contains or refers to all information needed to initiate the particular block.
 
Changed:
<
<
Brainstream: BrainStream is a Matlab-based toolbox that allows you to run and analyse EEG experiments in a modular way. For a more elaborate description see the introduction of the documentation.
>
>
Brainstream: BrainStream is a Matlab-based toolbox that allows you to run and analyse EEG experiments in a modular way. For a more elaborate description see the introduction of the documentation

 

C

Added:
>
>
Common block file: A special type of block file. Common block files contain or refer to information that is needed in all blocks of the experiment. For example, a common block file might contain information that is specific to the lab in which the experiment takes place.
  Constants (in user-defined functions): User functions can take additional (only constant) arguments besided the obligatory first event argument.
Added:
>
>
 

D

Data segment: A limited amount of data from the data stream source.
Line: 43 to 54
  Default variables: Variables for which no content is defines will take the default value.
Added:
>
>
 

E

Event: Markers become events when received. Events have rich structure and can be regarded objects with data (optional), variables, and actions with different moments of execution relative to the onset of the event. Every subsequent same marker in the data stream instantiates a new event.
Line: 54 to 67
  Experiment file: If experiments involve execution of several blocks, references to those blocks can be put together in a single text file, in which every .blk file is denoted in one row. The text file has to be saved with the extension .exp.
Added:
>
>
 

F

Field:

Line: 62 to 77
  Function:A function generates and delivers output with respect to the received input.
Added:
>
>
 

G

'Get' statement: Use this statement to retrieve a copy of the current content of a user variable from the global variables. The name of the variable will showup as a field in the event structure.
Line: 69 to 86
  Graphical User Interface (GUI): User friendly interface that can be used to start experiments with feedback about performance and currently executed actions.
Added:
>
>
 

H

Added:
>
>
 

I

Added:
>
>
 

J

Added:
>
>
 

K

Key: Users can define their own constants in the block file (see glossary). They should be added to an existing or new topic (see glossary) and assignments follow Matlab symantics.

Added:
>
>
 

L

Added:
>
>
  'Load' statement: Instead of retrieving user variables from the global variables, it can also be retrieved from a previous executed block by specifying the load instead of the get action for corresponding variable. A previous block should of course have made content available via the save keyword for the same variable.
Added:
>
>
 

M

Markers: Specify some specific timepoint in the data stream which trigger BrainStream to execute possible defined actions (process data, update/modify information, give feedback). The way marker information is provided to BrainStream depends on the datasource in use. Therefore, a dictionary serves to translate markers into marker names which can then be processed independent of the utilized data source.
Line: 95 to 125
  Modules:
Added:
>
>
 

N

Added:
>
>
 

O

Added:
>
>
 

P

Line: 107 to 143
  'Put' statement: Use this statement to update content of a user variable to the global variables. The name of the variable should exist as a field in the event structure.
Added:
>
>
 

Q

Added:
>
>
 

R

Added:
>
>
 

S

'Save' statement: Instead of updating user variables to the global variables, it can also be stored to disk via the save instead of the put keyword for corresponding variable. A subsequent/future block can then retrieve this information via a load keyword on corresponding variable.
Line: 130 to 172
  Structure: A Matlab type variable that manages to keep a collection of (closely related) variables as sub-fields of its own.
Added:
>
>
 

T

Terminal:

Line: 140 to 184
  Trunk: The trunk is the main line of a program development in a group-shared repository.
Added:
>
>
 

U

User-defined functions: Users can write their own MATLAB functions which can be called within an Experiment when an event occurs.

User variable: A variable that is defined by the user. It can be used to exchange information between different events.

Added:
>
>
 

V

Variables:

Verbosity level:

Added:
>
>
 

W

Added:
>
>
 

X

Added:
>
>
  X11:
Added:
>
>
 

Y

Added:
>
>
 

Z

<---End1--->

Revision 1120 Jul 2011 - Main.PhilipVanDenBroek

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

13 Glossary

Line: 100 to 100
 

O

P

Added:
>
>
  Path: A path refers to the location of a folder on a drive. In many programs, such as Matlab, a path can be set in which the programs searches for definitions or functions to be used. By setting the path, these functions and definitions become easily accessible.

'Put' statement: Use this statement to update content of a user variable to the global variables. The name of the variable should exist as a field in the event structure.

Revision 1010 Nov 2009 - Main.MarianneSeverens

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

13 Glossary

Line: 6 to 6
 

A

Changed:
<
<
ActiView: Software responsible for acquiring, saving and optional transmitting data from BioSemi? 's Active2 EEG amplifier.
>
>
ActiView: Software responsible for acquiring, saving and optional transmitting data from BioSemi's Active2 EEG amplifier.
  Acquisition: The process of collecting data/information from a device.

Acquisition computer: The computer responsible for managing the data acquisition.

Changed:
<
<
Audio Midi Setup:See MIDI
>
>
Audio Midi Setup:See MIDI
  Action: An action can be one of the following: modify, get or load, function, put or save. See corresponding items in this glossary.
Changed:
<
<
Application (of BrainStream):
>
>
Application (of BrainStream):
  Argument: Functions can be given extra information as input to start with, these are called arguments.

B

Block: Every session is divided into different functional blocks. Every 'block' can have a different purpose, e.g. one block for training, one for online feedback, etc.
Changed:
<
<
Block file: To initiate your experiment in BrainStream, you need to compose an initialization run file(s), also called a block file. Every block has a separate file, which contains or refers to all information needed to initiate the particular block.
>
>
Block file: To initiate your experiment in BrainStream, you need to compose an initialization run file(s), also called a block file. Every block has a separate file, which contains or refers to all information needed to initiate the particular block.
 
Changed:
<
<
Brainstream: BrainStream is a Matlab-based toolbox that allows you to run and analyse EEG experiments in a modular way. For a more elaborate description see the introduction of the documentation.
>
>
Brainstream: BrainStream is a Matlab-based toolbox that allows you to run and analyse EEG experiments in a modular way. For a more elaborate description see the introduction of the documentation.
 

C

Constants (in user-defined functions): User functions can take additional (only constant) arguments besided the obligatory first event argument.
Line: 35 to 35
  Data selection: The amount of data the user selects from the data stream source.
Changed:
<
<
Dictionary: Defines interface between source dependent marker information (type and value) and marker names used in BrainStream.
>
>
Dictionary: Defines interface between source dependent marker information (type and value) and marker names used in BrainStream.
  Debug: A run mode which allows step-wise execution of programmed code.For example, when setting break points in Matlab and enabled debug mode, the experiment will stop running and Matlab waiting for you to check the code and continue the experiment by pressing 'F5' on the keyboard.
Line: 50 to 50
  Experiment definition file: The file that defines the actions for the markers involved in the experiment. This file can also be regarded: the collection of tables that together define the entire experiment.
Changed:
<
<
Experiment definition table: One that defines actions for some markers involved in the experiment. A collection of tables together define the entire experiment, see experiment definition file.
>
>
Experiment definition table: One that defines actions for some markers involved in the experiment. A collection of tables together define the entire experiment, see experiment definition file.
  Experiment file: If experiments involve execution of several blocks, references to those blocks can be put together in a single text file, in which every .blk file is denoted in one row. The text file has to be saved with the extension .exp.
Line: 65 to 65
 

G

'Get' statement: Use this statement to retrieve a copy of the current content of a user variable from the global variables. The name of the variable will showup as a field in the event structure.
Changed:
<
<
Global variables: All variables defined as headers (except marker, time, function and client) in experiment definition tables. Their content is maintained by BrainStream and can be retrieved (get) or updated (put).
>
>
Global variables: All variables defined as headers (except marker, time, function and client) in experiment definition tables. Their content is maintained by BrainStream and can be retrieved (get) or updated (put).
  Graphical User Interface (GUI): User friendly interface that can be used to start experiments with feedback about performance and currently executed actions.
Line: 83 to 83
  'Load' statement: Instead of retrieving user variables from the global variables, it can also be retrieved from a previous executed block by specifying the load instead of the get action for corresponding variable. A previous block should of course have made content available via the save keyword for the same variable.

M

Changed:
<
<
Markers: Specify some specific timepoint in the data stream which trigger BrainStream to execute possible defined actions (process data, update/modify information, give feedback). The way marker information is provided to BrainStream depends on the datasource in use. Therefore, a dictionary serves to translate markers into marker names which can then be processed independent of the utilized data source.
>
>
Markers: Specify some specific timepoint in the data stream which trigger BrainStream to execute possible defined actions (process data, update/modify information, give feedback). The way marker information is provided to BrainStream depends on the datasource in use. Therefore, a dictionary serves to translate markers into marker names which can then be processed independent of the utilized data source.
  Matlab: http://www.mathworks.com/products/matlab/ : MATLABŪ is a high-level language and interactive environment that enables you to perform computationally intensive tasks faster than with traditional programming languages such as C, C++, and Fortran.
Line: 91 to 91
  MMM Lab: The lab of the Music, Mind, Machine group at Radboud Universiteit, Nijmegen.
Changed:
<
<
Modify: BrainStream actually executes something when it encounters one of the following actions: modify, get or load, functions, put or save. The modify action permits users to directly change content of a global variable, which is especially useful for simple modifications. That is, you do not first need to retrieve a copy from the global variables (get action), change its content, and then update it (put action). Note that modify actions will always be executed first (the order is: modify, get or load, functions, put or save).
>
>
Modify: BrainStream actually executes something when it encounters one of the following actions: modify, get or load, functions, put or save. The modify action permits users to directly change content of a global variable, which is especially useful for simple modifications. That is, you do not first need to retrieve a copy from the global variables (get action), change its content, and then update it (put action). Note that modify actions will always be executed first (the order is: modify, get or load, functions, put or save).
  Modules:
Line: 100 to 100
 

O

P

Changed:
<
<
Path: A path refers to the location of a folder on a drive. In many programs, such as Matlab, a path can be set in which the programs searches for definitions or functions to be used. By setting the path, these functions and definitions become easily accessible.
>
>
Path: A path refers to the location of a folder on a drive. In many programs, such as Matlab, a path can be set in which the programs searches for definitions or functions to be used. By setting the path, these functions and definitions become easily accessible.
  'Put' statement: Use this statement to update content of a user variable to the global variables. The name of the variable should exist as a field in the event structure.
Line: 115 to 115
  Sequence: Every block consists of a set of several 'sequences'. Every sequence is self-paced meaning that the participant can push a button to start the next sequence. A sequence is defined as a succession of certain stimuli (e.g. a sequence of tones to generate an auditory evoked potential or a sequence of different motor imagery tasks).
Changed:
<
<
Server: Computer running BrainStream.
>
>
Server: Computer running BrainStream.
  Session: Multiple measurements using the same subject each time.
Line: 133 to 133
  Time point: e.g. DATA, EVENT
Changed:
<
<
Topic: Users can define their own constants in the block file. They should be added to an existing or new topic and assignments follow Matlab symantics.
>
>
Topic: Users can define their own constants in the block file. They should be added to an existing or new topic and assignments follow Matlab symantics.
  Trunk: The trunk is the main line of a program development in a group-shared repository.

U

Changed:
<
<
User-defined functions: Users can write their own MATLAB functions which can be called within an Experiment when an event occurs.
>
>
User-defined functions: Users can write their own MATLAB functions which can be called within an Experiment when an event occurs.
 
Changed:
<
<
User variable: A variable that is defined by the user. It can be used to exchange information between different events.
>
>
User variable: A variable that is defined by the user. It can be used to exchange information between different events.
 

V

Variables:
Line: 156 to 156
 

Z

<---End1--->
Added:
>
>
<-- 
  • Access control
    • Set DENYTOPICVIEW =
-->

Revision 902 Nov 2009 - Main.JoernHorschig

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

13 Glossary

Line: 12 to 12
  Acquisition computer: The computer responsible for managing the data acquisition.
Changed:
<
<
Audio Midi Setup:
>
>
Audio Midi Setup:See MIDI
  Action: An action can be one of the following: modify, get or load, function, put or save. See corresponding items in this glossary.
Line: 25 to 25
  Block file: To initiate your experiment in BrainStream, you need to compose an initialization run file(s), also called a block file. Every block has a separate file, which contains or refers to all information needed to initiate the particular block.
Changed:
<
<
Brainstream:
>
>
Brainstream: BrainStream is a Matlab-based toolbox that allows you to run and analyse EEG experiments in a modular way. For a more elaborate description see the introduction of the documentation.
 

C

Constants (in user-defined functions): User functions can take additional (only constant) arguments besided the obligatory first event argument.
Line: 37 to 37
  Dictionary: Defines interface between source dependent marker information (type and value) and marker names used in BrainStream.
Changed:
<
<
Debug:
>
>
Debug: A run mode which allows step-wise execution of programmed code.For example, when setting break points in Matlab and enabled debug mode, the experiment will stop running and Matlab waiting for you to check the code and continue the experiment by pressing 'F5' on the keyboard.

Decimation: The technique of reducing the number of samples of a signal by first low-pass filtering (in order to remove aliasing effects) and then downsampling the signal.

  Default variables: Variables for which no content is defines will take the default value.
Line: 48 to 50
  Experiment definition file: The file that defines the actions for the markers involved in the experiment. This file can also be regarded: the collection of tables that together define the entire experiment.
Added:
>
>
Experiment definition table: One that defines actions for some markers involved in the experiment. A collection of tables together define the entire experiment, see experiment definition file.
 Experiment file: If experiments involve execution of several blocks, references to those blocks can be put together in a single text file, in which every .blk file is denoted in one row. The text file has to be saved with the extension .exp.

F

Line: 51 to 55
 Experiment file: If experiments involve execution of several blocks, references to those blocks can be put together in a single text file, in which every .blk file is denoted in one row. The text file has to be saved with the extension .exp.

F

Added:
>
>
  Field:
Changed:
<
<
Function:
>
>
Fieldtrip: Fieldtrip is a Matlab software toolbox for MEG and EEG analysis that is being developed at the Centre for Cognitive Neuroimaging of the Donders Institute for Brain, Cognition and Behaviour together with collaborating institutes. For more information see http://fieldtrip.fcdonders.nl/

Function:A function generates and delivers output with respect to the received input.

 

G

'Get' statement: Use this statement to retrieve a copy of the current content of a user variable from the global variables. The name of the variable will showup as a field in the event structure.
Line: 78 to 85
 

M

Markers: Specify some specific timepoint in the data stream which trigger BrainStream to execute possible defined actions (process data, update/modify information, give feedback). The way marker information is provided to BrainStream depends on the datasource in use. Therefore, a dictionary serves to translate markers into marker names which can then be processed independent of the utilized data source.
Changed:
<
<
Matlab:
>
>
Matlab: http://www.mathworks.com/products/matlab/ : MATLABŪ is a high-level language and interactive environment that enables you to perform computationally intensive tasks faster than with traditional programming languages such as C, C++, and Fortran.
 
Changed:
<
<
Midi:
>
>
Midi: Midi (Musical Instrument Digital Interface) is a protocol which allows communication between different computers interface. Midi transmits event messages and thus no media signal such as audio.
 
Changed:
<
<
MMM Lab:
>
>
MMM Lab: The lab of the Music, Mind, Machine group at Radboud Universiteit, Nijmegen.
  Modify: BrainStream actually executes something when it encounters one of the following actions: modify, get or load, functions, put or save. The modify action permits users to directly change content of a global variable, which is especially useful for simple modifications. That is, you do not first need to retrieve a copy from the global variables (get action), change its content, and then update it (put action). Note that modify actions will always be executed first (the order is: modify, get or load, functions, put or save).
Line: 93 to 100
 

O

P

Changed:
<
<
Path:
>
>
Path: A path refers to the location of a folder on a drive. In many programs, such as Matlab, a path can be set in which the programs searches for definitions or functions to be used. By setting the path, these functions and definitions become easily accessible.
  'Put' statement: Use this statement to update content of a user variable to the global variables. The name of the variable should exist as a field in the event structure.
Line: 126 to 133
  Time point: e.g. DATA, EVENT
Changed:
<
<
Topic: Users can define their own constants in the block file (see glossary). They should be added to an existing or new topic and assignments follow Matlab symantics.
>
>
Topic: Users can define their own constants in the block file. They should be added to an existing or new topic and assignments follow Matlab symantics.
 
Changed:
<
<
Trunk:
>
>
Trunk: The trunk is the main line of a program development in a group-shared repository.
 

U

Changed:
<
<
User-defined functions:
>
>
User-defined functions: Users can write their own MATLAB functions which can be called within an Experiment when an event occurs.
 
Changed:
<
<
User variable: A variable that is defined by the user. It can be used to exchange information between different events.
>
>
User variable: A variable that is defined by the user. It can be used to exchange information between different events.
 

V

Variables:

Revision 829 Oct 2009 - Main.JeroenGeuze

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

13 Glossary

Line: 121 to 121
 Structure: A Matlab type variable that manages to keep a collection of (closely related) variables as sub-fields of its own.

T

Added:
>
>
  Terminal:
Added:
>
>
Time point: e.g. DATA, EVENT
 Topic: Users can define their own constants in the block file (see glossary). They should be added to an existing or new topic and assignments follow Matlab symantics.

Trunk:

Revision 728 Oct 2009 - Main.MoniekLijster

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

13 Glossary

Line: 37 to 37
  Dictionary: Defines interface between source dependent marker information (type and value) and marker names used in BrainStream.
Added:
>
>
Debug:
 Default variables: Variables for which no content is defines will take the default value.

E

Revision 623 Oct 2009 - Main.MarianneSeverens

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

13 Glossary

Line: 142 to 143
 

Y

Z

Added:
>
>
<---End1--->
 \ No newline at end of file

Revision 506 Sep 2009 - Main.PhilipVanDenBroek

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

13 Glossary

A

Changed:
<
<
ActiView: Software responsible for acquiring/saving/transmitting data from BioSemi? 's Active2 EEG amplifier.
>
>
ActiView: Software responsible for acquiring, saving and optional transmitting data from BioSemi? 's Active2 EEG amplifier.
  Acquisition: The process of collecting data/information from a device.
Line: 39 to 39
 Default variables: Variables for which no content is defines will take the default value.

E

Changed:
<
<
Event:
>
>
Event: Markers become events when received. Events have rich structure and can be regarded objects with data (optional), variables, and actions with different moments of execution relative to the onset of the event. Every subsequent same marker in the data stream instantiates a new event.
  Experiment: Most BCI experiments involve measurement of several different subjects. Also, BCI experiments can consist of multiple measurements using the same subject each time (i.e. 'sessions'). Every session is divided into different functional blocks. Every 'block' can have a different purpose, e.g. one block for training, one for online feedback, etc. Every block consists of a set of several 'sequences'. Every sequence is self-paced meaning that the participant can push a button to start the next sequence. A sequence is defined as a succession of certain stimuli (e.g. a sequence of tones to generate an auditory evoked potential or a sequence of different motor imagery tasks). These stimuli can be named 'tones', 'trials', 'stimuli', 'epochs', etc. If you take these definitions into account, the hierarchical structure of a common BCI experiment summarizes to 'Experiment' --> 'Subject' --> 'Session' --> 'Block' --> 'Sequence' --> 'Stimulus'. These definitions will be used throughout this documentation. Moreover, this hierarchical structure can serve as a template to arrange locations for data storage.
Line: 57 to 57
  Global variables: All variables defined as headers (except marker, time, function and client) in experiment definition tables. Their content is maintained by BrainStream and can be retrieved (get) or updated (put).
Changed:
<
<
Graphical User Interface (GUI):
>
>
Graphical User Interface (GUI): User friendly interface that can be used to start experiments with feedback about performance and currently executed actions.
 

H

Line: 66 to 66
 

J

K

Changed:
<
<
Key:
>
>
Key: Users can define their own constants in the block file (see glossary). They should be added to an existing or new topic (see glossary) and assignments follow Matlab symantics.
 

L

Changed:
<
<
'Load' statement:
>
>
'Load' statement: Instead of retrieving user variables from the global variables, it can also be retrieved from a previous executed block by specifying the load instead of the get action for corresponding variable. A previous block should of course have made content available via the save keyword for the same variable.
 

M

Changed:
<
<
Markers:
>
>
Markers: Specify some specific timepoint in the data stream which trigger BrainStream to execute possible defined actions (process data, update/modify information, give feedback). The way marker information is provided to BrainStream depends on the datasource in use. Therefore, a dictionary serves to translate markers into marker names which can then be processed independent of the utilized data source.
  Matlab:
Line: 80 to 81
  MMM Lab:
Changed:
<
<
Modify:
>
>
Modify: BrainStream actually executes something when it encounters one of the following actions: modify, get or load, functions, put or save. The modify action permits users to directly change content of a global variable, which is especially useful for simple modifications. That is, you do not first need to retrieve a copy from the global variables (get action), change its content, and then update it (put action). Note that modify actions will always be executed first (the order is: modify, get or load, functions, put or save).
  Modules:
Line: 91 to 92
 

P

Path:
Changed:
<
<
'Put' statement:
>
>
'Put' statement: Use this statement to update content of a user variable to the global variables. The name of the variable should exist as a field in the event structure.
 

Q

R

S

Changed:
<
<
'Save' statement:
>
>
'Save' statement: Instead of updating user variables to the global variables, it can also be stored to disk via the save instead of the put keyword for corresponding variable. A subsequent/future block can then retrieve this information via a load keyword on corresponding variable.
 
Changed:
<
<
Screen Sharing:
>
>
Screen Sharing: A feature that allows you to access and control another remote computer by just showing its screen content and directing your mouse/keyboard inputs to this device.
  Sequence: Every block consists of a set of several 'sequences'. Every sequence is self-paced meaning that the participant can push a button to start the next sequence. A sequence is defined as a succession of certain stimuli (e.g. a sequence of tones to generate an auditory evoked potential or a sequence of different motor imagery tasks).
Changed:
<
<
Server:
>
>
Server: Computer running BrainStream.
  Session: Multiple measurements using the same subject each time.

Stimuli: 'tones', 'trials', 'stimuli', 'epochs', etc.

Changed:
<
<
Stimulus computer:
>
>
Stimulus computer: The computer responsible for generating or managing the stimuli.
 
Changed:
<
<
String:
>
>
String: Some textual information enclosed by quotes.
 
Changed:
<
<
Structure:
>
>
Structure: A Matlab type variable that manages to keep a collection of (closely related) variables as sub-fields of its own.
 

T

Terminal:
Changed:
<
<
Topic:
>
>
Topic: Users can define their own constants in the block file (see glossary). They should be added to an existing or new topic and assignments follow Matlab symantics.
  Trunk:

U

User-defined functions:
Changed:
<
<
User variable:
>
>
User variable: A variable that is defined by the user. It can be used to exchange information between different events.
 

V

Variables:

Revision 404 Sep 2009 - Main.PhilipVanDenBroek

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

13 Glossary

A

Changed:
<
<
ActiView:
>
>
ActiView: Software responsible for acquiring/saving/transmitting data from BioSemi? 's Active2 EEG amplifier.
 
Changed:
<
<
Acquisition:
>
>
Acquisition: The process of collecting data/information from a device.
 
Changed:
<
<
Acquisition computer:
>
>
Acquisition computer: The computer responsible for managing the data acquisition.
  Audio Midi Setup:
Changed:
<
<
Action:
>
>
Action: An action can be one of the following: modify, get or load, function, put or save. See corresponding items in this glossary.
  Application (of BrainStream):
Changed:
<
<
Argument:
>
>
Argument: Functions can be given extra information as input to start with, these are called arguments.
 

B

Block: Every session is divided into different functional blocks. Every 'block' can have a different purpose, e.g. one block for training, one for online feedback, etc.
Line: 27 to 27
 Brainstream:

C

Changed:
<
<
Constants (in user-defined functions):
>
>
Constants (in user-defined functions): User functions can take additional (only constant) arguments besided the obligatory first event argument.
 

D

Changed:
<
<
Data segment:
>
>
Data segment: A limited amount of data from the data stream source.
 
Changed:
<
<
Data selection:
>
>
Data selection: The amount of data the user selects from the data stream source.
 
Changed:
<
<
Dictionary:
>
>
Dictionary: Defines interface between source dependent marker information (type and value) and marker names used in BrainStream.
 
Changed:
<
<
Default variables:
>
>
Default variables: Variables for which no content is defines will take the default value.
 

E

Event:

Experiment: Most BCI experiments involve measurement of several different subjects. Also, BCI experiments can consist of multiple measurements using the same subject each time (i.e. 'sessions'). Every session is divided into different functional blocks. Every 'block' can have a different purpose, e.g. one block for training, one for online feedback, etc. Every block consists of a set of several 'sequences'. Every sequence is self-paced meaning that the participant can push a button to start the next sequence. A sequence is defined as a succession of certain stimuli (e.g. a sequence of tones to generate an auditory evoked potential or a sequence of different motor imagery tasks). These stimuli can be named 'tones', 'trials', 'stimuli', 'epochs', etc. If you take these definitions into account, the hierarchical structure of a common BCI experiment summarizes to 'Experiment' --> 'Subject' --> 'Session' --> 'Block' --> 'Sequence' --> 'Stimulus'. These definitions will be used throughout this documentation. Moreover, this hierarchical structure can serve as a template to arrange locations for data storage.

Changed:
<
<
Experiment definition file:
>
>
Experiment definition file: The file that defines the actions for the markers involved in the experiment. This file can also be regarded: the collection of tables that together define the entire experiment.
  Experiment file: If experiments involve execution of several blocks, references to those blocks can be put together in a single text file, in which every .blk file is denoted in one row. The text file has to be saved with the extension .exp.
Line: 53 to 53
 Function:

G

Changed:
<
<
'Get' statement:
>
>
'Get' statement: Use this statement to retrieve a copy of the current content of a user variable from the global variables. The name of the variable will showup as a field in the event structure.
 
Changed:
<
<
Global variables:
>
>
Global variables: All variables defined as headers (except marker, time, function and client) in experiment definition tables. Their content is maintained by BrainStream and can be retrieved (get) or updated (put).
  Graphical User Interface (GUI):
Line: 80 to 80
  MMM Lab:
Added:
>
>
Modify:
 Modules:

N

Revision 303 Sep 2009 - Main.MoniekLijster

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

13 Glossary

Line: 36 to 36
  Dictionary:
Added:
>
>
Default variables:
 

E

Event:
Line: 78 to 80
  MMM Lab:
Changed:
<
<
Modules of functions:
>
>
Modules:
 

N

Revision 202 Sep 2009 - Main.MarianneSeverens

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

13 Glossary

Line: 7 to 7
 

A

ActiView:
Added:
>
>
Acquisition:
 Acquisition computer:

Audio Midi Setup:

Line: 15 to 17
  Application (of BrainStream):
Added:
>
>
Argument:
 

B

Block: Every session is divided into different functional blocks. Every 'block' can have a different purpose, e.g. one block for training, one for online feedback, etc.
Line: 28 to 32
 

D

Data segment:
Added:
>
>
Data selection:
 Dictionary:

E

Line: 40 to 46
 Experiment file: If experiments involve execution of several blocks, references to those blocks can be put together in a single text file, in which every .blk file is denoted in one row. The text file has to be saved with the extension .exp.

F

Added:
>
>
Field:
 Function:

G

Line: 100 to 108
  Stimulus computer:
Added:
>
>
String:

Structure:

 

T

Terminal:
Line: 115 to 127
 

V

Variables:
Added:
>
>
Verbosity level:
 

W

X

Revision 131 Aug 2009 - Main.MoniekLijster

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

13 Glossary

A

ActiView:

Acquisition computer:

Audio Midi Setup:

Action:

Application (of BrainStream):

B

Block: Every session is divided into different functional blocks. Every 'block' can have a different purpose, e.g. one block for training, one for online feedback, etc.

Block file: To initiate your experiment in BrainStream, you need to compose an initialization run file(s), also called a block file. Every block has a separate file, which contains or refers to all information needed to initiate the particular block.

Brainstream:

C

Constants (in user-defined functions):

D

Data segment:

Dictionary:

E

Event:

Experiment: Most BCI experiments involve measurement of several different subjects. Also, BCI experiments can consist of multiple measurements using the same subject each time (i.e. 'sessions'). Every session is divided into different functional blocks. Every 'block' can have a different purpose, e.g. one block for training, one for online feedback, etc. Every block consists of a set of several 'sequences'. Every sequence is self-paced meaning that the participant can push a button to start the next sequence. A sequence is defined as a succession of certain stimuli (e.g. a sequence of tones to generate an auditory evoked potential or a sequence of different motor imagery tasks). These stimuli can be named 'tones', 'trials', 'stimuli', 'epochs', etc. If you take these definitions into account, the hierarchical structure of a common BCI experiment summarizes to 'Experiment' --> 'Subject' --> 'Session' --> 'Block' --> 'Sequence' --> 'Stimulus'. These definitions will be used throughout this documentation. Moreover, this hierarchical structure can serve as a template to arrange locations for data storage.

Experiment definition file:

Experiment file: If experiments involve execution of several blocks, references to those blocks can be put together in a single text file, in which every .blk file is denoted in one row. The text file has to be saved with the extension .exp.

F

Function:

G

'Get' statement:

Global variables:

Graphical User Interface (GUI):

H

I

J

K

Key:

L

'Load' statement:

M

Markers:

Matlab:

Midi:

MMM Lab:

Modules of functions:

N

O

P

Path:

'Put' statement:

Q

R

S

'Save' statement:

Screen Sharing:

Sequence: Every block consists of a set of several 'sequences'. Every sequence is self-paced meaning that the participant can push a button to start the next sequence. A sequence is defined as a succession of certain stimuli (e.g. a sequence of tones to generate an auditory evoked potential or a sequence of different motor imagery tasks).

Server:

Session: Multiple measurements using the same subject each time.

Stimuli: 'tones', 'trials', 'stimuli', 'epochs', etc.

Stimulus computer:

T

Terminal:

Topic:

Trunk:

U

User-defined functions:

User variable:

V

Variables:

W

X

X11:

Y

Z

 
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