Technical Reference:System Design - Revision history

Mellinger: /* Inter-Core Communication */

2008-10-18T14:16:28Z

Inter-Core Communication

← Older revision		Revision as of 14:16, 18 October 2008
Line 74:		Line 74:

	==Inter-Core Communication==		==Inter-Core Communication==
	~~===Introduction===~~
	Unlike the bidirectional communication between core modules and the		Unlike the bidirectional communication between core modules and the
	operator		operator

2008-10-18T14:16:16Z

Core-Operator Communication

← Older revision		Revision as of 14:16, 18 October 2008
Line 34:		Line 34:

	==Core-Operator Communication==		==Core-Operator Communication==
	~~===Introduction===~~
	The same communication protocol is used between each of the three core		The same communication protocol is used between each of the three core
	modules		modules

2008-05-10T11:18:26Z

State Vector Messages

← Older revision		Revision as of 11:18, 10 May 2008
Line 86:		Line 86:
	===State Vector Messages===		===State Vector Messages===
	A [[BCI2000 Glossary#State Vector\|State Vector]] is a data structure consisting of a series of ''StateVectorLength''		A [[BCI2000 Glossary#State Vector\|State Vector]] is a data structure consisting of a series of ''StateVectorLength''
	subsequent bytes, representing an overall system state that is saved into a data file along with each ~~block~~ of data.		subsequent bytes, representing an overall system state that is saved into a data file along with each sample of data.
	~~The state~~ vector is always transmitted before the		State vector data is always transmitted before the brain signal or control signal.
	brain signal or control signal.

	===Brain Signal Messages===		===Brain Signal Messages===

2008-01-09T17:21:09Z

Overview

← Older revision		Revision as of 17:21, 9 January 2008
Line 15:		Line 15:
	together as		together as
	''core modules''.		''core modules''.
	[[Image:BCI2000 SysDes_Modules.png\|center\|thumb\|~~300px~~\|Fig. 1 The functional modules and their interfaces]]		[[Image:BCI2000 SysDes_Modules.png\|center\|thumb\|591px\|Fig. 1 The functional modules and their interfaces]]

	In a binary distribution, the four modules correspond to executables.		In a binary distribution, the four modules correspond to executables.

2007-11-22T12:58:28Z

Overview

← Older revision		Revision as of 12:58, 22 November 2007
Line 3:		Line 3:
	use, the signal processing they perform, the feedback they provide, or		use, the signal processing they perform, the feedback they provide, or
	the underlying training and operation paradigm, they all need the same four		the underlying training and operation paradigm, they all need the same four
	elements: ~~EEG~~ data collection, signal processing, an output device and manual or		elements: data collection, signal processing, an output device and manual or
	automatic parameterization and configuration. Therefore, it seems to be a		automatic parameterization and configuration. Therefore, it seems to be a
	natural choice to partition the system into four modules with respect to		natural choice to partition the system into four modules with respect to
Line 26:		Line 26:
	\| Operator \|\| Operat.exe \|\|		\| Operator \|\| Operat.exe \|\|
	\|-		\|-
	\| ~~EEG source~~ \|\| gUSBamp.exe \|\| data acquisition from the gUSBamp g.tec amplifier		\| Source \|\| gUSBamp.exe \|\| data acquisition from the gUSBamp g.tec amplifier
	\|-		\|-
	\| Signal Processing \|\| ARSignalProcessing.exe \|\| auto-regressive spectral estimation		\| Signal Processing \|\| ARSignalProcessing.exe \|\| auto-regressive spectral estimation

2007-11-22T10:42:48Z

State Messages

← Older revision		Revision as of 10:42, 22 November 2007
Line 58:		Line 58:

	===State Messages===		===State Messages===
	~~The~~ core modules and the operator module use messages containing [[BCI2000 Glossary#State\|States]] to		As a generalization of event markers, the core modules and the operator module use messages containing [[BCI2000 Glossary#State\|States]] to
	communicate in the system initialization phase,		communicate in the system initialization phase,
	as well as during system performance and		as well as during system performance and

2007-11-08T19:39:17Z

← Older revision		Revision as of 19:39, 8 November 2007
Line 64:		Line 64:

	===Visualization Messages===		===Visualization Messages===
	[[Glossary#Visualization\|Visualization]] messages are sent from core modules to the operator module, which in turn displays their content to the operator user.		[[BCI2000 Glossary#Visualization\|Visualization]] messages are sent from core modules to the operator module, which in turn displays their content to the operator user.
	These messages may contain signal data for graphical display, or text to be displayed in a log window.		These messages may contain signal data for graphical display, or text to be displayed in a log window.
	A core module may also configure details of the display sending configuration messages.		A core module may also configure details of the display sending configuration messages.
Line 85:		Line 85:

	===State Vector Messages===		===State Vector Messages===
	A [[Glossary#State Vector\|State Vector]] is a data structure consisting of a series of ''StateVectorLength''		A [[BCI2000 Glossary#State Vector\|State Vector]] is a data structure consisting of a series of ''StateVectorLength''
	subsequent bytes, representing an overall system state that is saved into a data file along with each block of data.		subsequent bytes, representing an overall system state that is saved into a data file along with each block of data.
	The state vector is always transmitted before the		The state vector is always transmitted before the

2007-11-08T19:38:34Z

Parameter Messages

← Older revision		Revision as of 19:38, 8 November 2007
Line 54:		Line 54:

	===Parameter Messages===		===Parameter Messages===
	These messages transport [[Glossary#Parameter\|Parameters]] carrying configuration information.		These messages transport [[BCI2000 Glossary#Parameter\|Parameters]] carrying configuration information.
	The operator module receives parameter messages from core modules, which enable it to display parameters in a configuration dialog, and to save parameters to, and load them from a [[Technical Reference:Parameter File\|parameter file]].		The operator module receives parameter messages from core modules, which enable it to display parameters in a configuration dialog, and to save parameters to, and load them from a [[Technical Reference:Parameter File\|parameter file]].

2007-11-08T19:38:24Z

State Messages

← Older revision		Revision as of 19:38, 8 November 2007
Line 58:		Line 58:

	===State Messages===		===State Messages===
	The core modules and the operator module use messages containing [[~~BCI2000Glossary~~#State\|States]] to		The core modules and the operator module use messages containing [[BCI2000 Glossary#State\|States]] to
	communicate in the system initialization phase,		communicate in the system initialization phase,
	as well as during system performance and		as well as during system performance and

2007-11-08T19:38:13Z

State Messages

← Older revision		Revision as of 19:38, 8 November 2007
Line 58:		Line 58:

	===State Messages===		===State Messages===
	The core modules and the operator module use messages containing [[~~Glossary~~#State\|States]] to		The core modules and the operator module use messages containing [[BCI2000Glossary#State\|States]] to
	communicate in the system initialization phase,		communicate in the system initialization phase,
	as well as during system performance and		as well as during system performance and