Jump to content

BCI2000 Glossary: Difference between revisions

From BCI2000 Wiki
Mellinger (talk | contribs)
No edit summary
 
Mellinger (talk | contribs)
Line 1: Line 1:
==Sample Block==
==Sample Block==
BCI2000 processes data in chunks, which are called ''Sample Blocks'', or ''Data Blocks''.
BCI2000 processes data in chunks, which are called ''Sample Blocks'', or ''Data Blocks''.
[[State variables]] are saved with each sample, but may only change once per sample block.
[[#State|State variables]] are saved with each sample, but may only change once per sample block.
Sample block size is configured through the [[User Reference:Parameters|''SampleBlockSize'' parameter]]; often, ADC hardware imposes restrictions on sample block size.
Sample block size is configured through the [[User Reference:Parameters|''SampleBlockSize'' parameter]]; often, ADC hardware imposes restrictions on sample block size.



Revision as of 15:38, 7 November 2007

Sample Block

BCI2000 processes data in chunks, which are called Sample Blocks, or Data Blocks. State variables are saved with each sample, but may only change once per sample block. Sample block size is configured through the SampleBlockSize parameter; often, ADC hardware imposes restrictions on sample block size.

The physical duration of a sample block is the inverse of the screen update rate, and determined by the ratio of sampling rate to sample block size.

Core Module

One of Data Acquisition, Signal Processing, and User Application Module. These are called core modules because they are involved in on-line processing, as opposed to the Operator Module, which controls operation, and passively displays data sent by core modules, but is not actively involved in processing.

Parameter

A system-wide setting that is constant during a run. Parameters may be of varying type (numeric, string, etc.) and shape (single-valued, list, matrix).

State

A system-wide variable that may change during data processing, and is saved to file together with the current sample block.

Module

A single executable that may act as Operator Module or one of the Core Modules.

Operator Module

The experimenter's user interface, from which the system is configured, started, and stopped.