User Reference:GDFFileWriter - Revision history

Mellinger: /* SavePrmFile */

2011-06-07T14:40:05Z

SavePrmFile

← Older revision		Revision as of 14:40, 7 June 2011
Line 9:		Line 9:
	Determines whether a BCI2000 [[Technical Reference:Parameter File\|parameter file]] is saved along with the GDF file.		Determines whether a BCI2000 [[Technical Reference:Parameter File\|parameter file]] is saved along with the GDF file.
	As of version 2.1, GDF is able to represent BCI2000 parameters, and parameter information is no longer lost if ''SavePrmFile'' is switched off.		As of version 2.1, GDF is able to represent BCI2000 parameters, and parameter information is no longer lost if ''SavePrmFile'' is switched off.
			This parameter is optional, and will not appear in the parameter configuration dialog by default. To use it, specify <tt>--SavePrmFile=1</tt> on the command line when starting up the source module.

	{{EDFGDFParams\|format=GDF}}		{{EDFGDFParams\|format=GDF}}

Mellinger: /* EventCodes */

2009-06-05T08:07:53Z

EventCodes

← Older revision		Revision as of 08:07, 5 June 2009
Line 37:		Line 37:
	\|}		\|}

	In addition to GDF events, BCI2000 state variables will ~~also~~ be mapped to additional signal channels the same way as for EDF.		In addition to GDF events, BCI2000 state variables will be mapped to additional signal channels the same way as for EDF.

	==States==		==States==

Mellinger: /* EventCodes */

2009-06-05T08:06:33Z

EventCodes

← Older revision		Revision as of 08:06, 5 June 2009
Line 17:		Line 17:

	The ''EventCodes'' parameter is a two-column matrix, with each row associating a [[User Reference:Expression Syntax\|boolean expression]] with a hexadecimal event code as defined in the [[User Reference:Data File Formats#GDF File Format\|GDF File Format]].		The ''EventCodes'' parameter is a two-column matrix, with each row associating a [[User Reference:Expression Syntax\|boolean expression]] with a hexadecimal event code as defined in the [[User Reference:Data File Formats#GDF File Format\|GDF File Format]].
	The expression is evaluated for each data block. Whenever its value switches from "false" to "true", the GDF event code from the second column is entered into the GDF event table; whenever its value switches back from "true" to "false", the same event code is entered into the table but with the ~~terminating~~ bit set (bitmask 0x8000).		The expression is evaluated for each data block. Whenever its value switches from "false" to "true", the GDF event code from the second column is entered into the GDF event table; whenever its value switches back from "true" to "false", the same event code is entered into the table but with the most significant bit set to 1 (bitmask 0x8000).

	The default value of the ''EventCodes'' parameter defines the most common mappings between BCI2000 states and GDF event codes:		The default value of the ''EventCodes'' parameter defines the most common mappings between BCI2000 states and GDF event codes:

Mellinger: /* EventCodes */

2009-06-05T08:05:02Z

EventCodes

← Older revision		Revision as of 08:05, 5 June 2009
Line 14:		Line 14:

	====EventCodes====		====EventCodes====
	BCI2000 does not prescribe the ~~semantics~~ of its state variables. GDF, on the other hand, associates a fixed set of events with certain numeric codes. Thus, a general mapping of BCI2000 states onto GDF events is not possible. Instead, GDF events are created via a user-defined set of mapping rules in the <code>EventCode</code> parameter, which also has a set of rules predefined for the most important cases.		BCI2000 does not prescribe the meaning of its state variables. GDF, on the other hand, associates a fixed set of events with certain numeric codes. Thus, a general mapping of BCI2000 states onto GDF events is not possible. Instead, GDF events are created via a user-defined set of mapping rules in the <code>EventCode</code> parameter, which also has a set of rules predefined for the most important cases.

	The ''EventCodes'' parameter is a two-column matrix, with each row associating a [[User Reference:Expression Syntax\|boolean expression]] with a hexadecimal event code as defined in the [[User Reference:Data File Formats#GDF File Format\|GDF File Format]].		The ''EventCodes'' parameter is a two-column matrix, with each row associating a [[User Reference:Expression Syntax\|boolean expression]] with a hexadecimal event code as defined in the [[User Reference:Data File Formats#GDF File Format\|GDF File Format]].

Mellinger: /* Parameters */

2008-08-19T11:25:54Z

Parameters

← Older revision		Revision as of 11:25, 19 August 2008
Line 11:		Line 11:

	{{EDFGDFParams\|format=GDF}}		{{EDFGDFParams\|format=GDF}}
			Since GDF version 2.0, the equipment ID field has been 8-byte numeric rather than string-valued. Consequently, the EquipmentID parameter is treated as an integer value, and written into the numeric field. If the parameter string evaluates to 0 -- e.g., because it begins with a letter rather than a digit -- its first 8 bytes are copied into the numeric equipment ID field in a byte-wise manner. Remaining bytes are padded with zero bytes if the parameter's string representation contains fewer than 8 characters.

	====EventCodes====		====EventCodes====

Mellinger: /* Parameters */

2008-08-19T11:17:15Z

Parameters

← Older revision		Revision as of 11:17, 19 August 2008
Line 6:		Line 6:
	==Parameters==		==Parameters==
	{{StorageParams\|remark=}}		{{StorageParams\|remark=}}
			====SavePrmFile====
			Determines whether a BCI2000 [[Technical Reference:Parameter File\|parameter file]] is saved along with the GDF file.
			As of version 2.1, GDF is able to represent BCI2000 parameters, and parameter information is no longer lost if ''SavePrmFile'' is switched off.

	{{EDFGDFParams\|format=GDF}}		{{EDFGDFParams\|format=GDF}}

Mellinger: /* EventCodes */

2008-08-08T14:11:19Z

EventCodes

← Older revision		Revision as of 14:11, 8 August 2008
Line 13:		Line 13:

	The ''EventCodes'' parameter is a two-column matrix, with each row associating a [[User Reference:Expression Syntax\|boolean expression]] with a hexadecimal event code as defined in the [[User Reference:Data File Formats#GDF File Format\|GDF File Format]].		The ''EventCodes'' parameter is a two-column matrix, with each row associating a [[User Reference:Expression Syntax\|boolean expression]] with a hexadecimal event code as defined in the [[User Reference:Data File Formats#GDF File Format\|GDF File Format]].
	The expression is evaluated for each data block~~; whenever~~ its value switches from "false" to "true", the GDF event code from the second column is entered into the GDF event table.		The expression is evaluated for each data block. Whenever its value switches from "false" to "true", the GDF event code from the second column is entered into the GDF event table; whenever its value switches back from "true" to "false", the same event code is entered into the table but with the terminating bit set (bitmask 0x8000).

	The default value of the ''EventCodes'' parameter defines the most common mappings between BCI2000 states and GDF event codes:		The default value of the ''EventCodes'' parameter defines the most common mappings between BCI2000 states and GDF event codes:
Line 21:		Line 21:
	\|-		\|-
	\|TargetCode!=0\|\|0x0300\|\|trial begin		\|TargetCode!=0\|\|0x0300\|\|trial begin
	\|-
	~~\|TargetCode==0\|\|0x8300\|\|trial end~~
	\|-		\|-
	\|TargetCode==1\|\|0x030c\|\|cue up		\|TargetCode==1\|\|0x030c\|\|cue up

Mellinger: /* EventCodes */

2008-02-27T10:50:56Z

EventCodes

← Older revision		Revision as of 10:50, 27 February 2008
Line 35:		Line 35:
	\|}		\|}

	~~Besides~~ GDF events, BCI2000 state variables will also be mapped to additional signal channels the same way as for EDF.		In addition to GDF events, BCI2000 state variables will also be mapped to additional signal channels the same way as for EDF.

	==States==		==States==

Mellinger at 19:45, 8 November 2007

2007-11-08T19:45:41Z

← Older revision		Revision as of 19:45, 8 November 2007
Line 2:		Line 2:
	The ''GDFFileWriter'' component writes out data in the [[User Reference:Data File Formats#GDF File Format\|GDF File Format]].		The ''GDFFileWriter'' component writes out data in the [[User Reference:Data File Formats#GDF File Format\|GDF File Format]].

	In addition to the parameters provided by the [[User Reference:EDFFileWriter\|EDFFileWriter]], the ''GDFFileWriter'' provides an option to define mappings between [[Glossary#State\|state variables]] and GDF events.		In addition to the parameters provided by the [[User Reference:EDFFileWriter\|EDFFileWriter]], the ''GDFFileWriter'' provides an option to define mappings between [[BCI2000 Glossary#State\|state variables]] and GDF events.

	==Parameters==		==Parameters==

Mellinger: /* See also */

2007-11-08T17:55:19Z

← Older revision		Revision as of 17:55, 8 November 2007
Line 42:		Line 42:
	==See also==		==See also==
	[[User Reference:DataIOFilter]], [[User Reference:Data File Formats]]		[[User Reference:DataIOFilter]], [[User Reference:Data File Formats]]

			[[Category:Filters]][[Category:Data Storage]]