User Reference:Data File Formats - Revision history

Mellinger: /* See also */

2010-01-21T15:07:01Z

Mellinger: /* GDF File Format */

2009-06-04T09:23:44Z

GDF File Format

← Older revision		Revision as of 09:23, 4 June 2009
Line 59:		Line 59:

	*Currently, BCI2000 supports Version 2.10 of the GDF format specification.		*Currently, BCI2000 supports Version 2.10 of the GDF format specification.
	*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.
	*Besides GDF events, BCI2000 state variables will also be mapped to additional signal channels the same way as for EDF.		*Besides GDF events, BCI2000 state variables will also be mapped to additional signal channels the same way as for EDF.
	*Since version 2.0, GDF provides additional header space for metadata which is organized as a sequence of tag/length/value structures. BCI2000 uses such a structure--tagged with a "BCI2000" tag--to store parameters. Within the GDF data field, the same human readable format is used as it applies to [[Technical_Reference:Parameter_File\|BCI2000 parameter files]], i.e. a sequence of [[Technical_Reference:Parameter_Definition\|parameter definition lines]].		*Since version 2.0, GDF provides additional header space for metadata which is organized as a sequence of tag/length/value structures. BCI2000 uses such a structure--tagged with a "BCI2000" tag--to store parameters. Within the GDF data field, the same human readable format is used as it applies to [[Technical_Reference:Parameter_File\|BCI2000 parameter files]], i.e. a sequence of [[Technical_Reference:Parameter_Definition\|parameter definition lines]].

Mellinger: /* EDF File Format */

2009-06-04T09:23:18Z

EDF File Format

← Older revision		Revision as of 09:23, 4 June 2009
Line 41:		Line 41:
	EDF (''European Data Format'') is a standard for biosignal data especially popular in the area of sleep research.		EDF (''European Data Format'') is a standard for biosignal data especially popular in the area of sleep research.
	*EDF is limited to 16 bit data.		*EDF is limited to 16 bit data.
	*BCI2000 state variables will be mapped to additional signal channels ~~that contain a single sample for each data block~~.		*BCI2000 state variables will be mapped to additional signal channels.
	*BCI2000 parameters cannot be represented in EDF format. Setting the <code>SaveAdditionalParameterFile</code> parameter to ''1'' will save a separate BCI2000 parameter file along with the EDF data file.		*BCI2000 parameters cannot be represented in EDF format. Setting the <code>SaveAdditionalParameterFile</code> parameter to ''1'' will save a separate BCI2000 parameter file along with the EDF data file.

Mellinger: /* GDF File Format */

2008-08-08T14:30:54Z

GDF File Format

← Older revision		Revision as of 14:30, 8 August 2008
Line 61:		Line 61:
	*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 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.
	*Besides GDF events, BCI2000 state variables will also be mapped to additional signal channels the same way as for EDF.		*Besides GDF events, BCI2000 state variables will also be mapped to additional signal channels the same way as for EDF.
	*Since version 2.0, GDF provides additional header space for metadata which is organized as a sequence of tag/length/value structures. BCI2000 uses such a structure tagged with a "BCI2000" tag to store parameters. Within the GDF data field, the same human readable format is used as it applies to [[Technical_Reference:Parameter_File\|BCI2000 parameter files]], i.e. a sequence of [[Technical_Reference:Parameter_Definition\|parameter definition lines]].		*Since version 2.0, GDF provides additional header space for metadata which is organized as a sequence of tag/length/value structures. BCI2000 uses such a structure--tagged with a "BCI2000" tag--to store parameters. Within the GDF data field, the same human readable format is used as it applies to [[Technical_Reference:Parameter_File\|BCI2000 parameter files]], i.e. a sequence of [[Technical_Reference:Parameter_Definition\|parameter definition lines]].

	Output in GDF file format is implemented by the [[User Reference:GDFFileWriter\|GDFFileWriter]] component.		Output in GDF file format is implemented by the [[User Reference:GDFFileWriter\|GDFFileWriter]] component.

Mellinger at 14:30, 8 August 2008

2008-08-08T14:30:06Z

← Older revision		Revision as of 14:30, 8 August 2008
Line 5:		Line 5:
	command line parameter to the source module, as in		command line parameter to the source module, as in

	<code>gUSBampSource --FileFormat-Null</code>		<code>gUSBampSource --FileFormat=Null</code>

	or		or

	<code>SignalGenerator --FileFormat-GDF</code>		<code>SignalGenerator --FileFormat=GDF</code>

	Typically, source modules are launched from batch files contained in the ''batch'' directory, and their command line parameters are specified there.		Typically, source modules are launched from batch files contained in the ''batch'' directory, and their command line parameters are specified there.
Line 22:		Line 22:

	==BCI2000 File Format==		==BCI2000 File Format==
	<code>--FileFormat-BCI2000</code>		<code>--FileFormat=BCI2000</code>

	Parameters, BCI2000 state variables, and brain signal data will be		Parameters, BCI2000 state variables, and brain signal data will be
Line 31:		Line 31:

	==Null File Format==		==Null File Format==
	<code>--FileFormat-Null</code>		<code>--FileFormat=Null</code>

	No information is recorded.		No information is recorded.
Line 37:		Line 37:

	==EDF File Format==		==EDF File Format==
	<code>--FileFormat-EDF</code>		<code>--FileFormat=EDF</code>

	EDF (''European Data Format'') is a standard for biosignal data especially popular in the area of sleep research.		EDF (''European Data Format'') is a standard for biosignal data especially popular in the area of sleep research.
Line 51:		Line 51:

	==GDF File Format==		==GDF File Format==
	<code>--FileFormat-GDF</code>		<code>--FileFormat=GDF</code>

	GDF is a general data format for biosignals which is popular in BCI		GDF is a general data format for biosignals which is popular in BCI

Mellinger: /* GDF File Format */

2008-08-08T14:28:46Z

GDF File Format

← Older revision		Revision as of 14:28, 8 August 2008
Line 61:		Line 61:
	*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 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.
	*Besides GDF events, BCI2000 state variables will also be mapped to additional signal channels the same way as for EDF.		*Besides GDF events, BCI2000 state variables will also be mapped to additional signal channels the same way as for EDF.
	*Since version 2.0, GDF provides additional header space for metadata which is organized as a sequence of tag/length/value structures. BCI2000 uses such a structure tagged with a "BCI2000" tag to store parameters. Within the GDF data field, the same human readable format is used as it applies to �[[Technical_Reference:Parameter_File\|BCI2000 parameter files]], i.e. a sequence of [[Technical_Reference:Parameter_Definition\|parameter definition lines]].		*Since version 2.0, GDF provides additional header space for metadata which is organized as a sequence of tag/length/value structures. BCI2000 uses such a structure tagged with a "BCI2000" tag to store parameters. Within the GDF data field, the same human readable format is used as it applies to [[Technical_Reference:Parameter_File\|BCI2000 parameter files]], i.e. a sequence of [[Technical_Reference:Parameter_Definition\|parameter definition lines]].

	Output in GDF file format is implemented by the [[User Reference:GDFFileWriter\|GDFFileWriter]] component.		Output in GDF file format is implemented by the [[User Reference:GDFFileWriter\|GDFFileWriter]] component.

Mellinger: /* GDF File Format */

2008-08-08T14:28:14Z

GDF File Format

← Older revision		Revision as of 14:28, 8 August 2008
Line 61:		Line 61:
	*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 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.
	*Besides GDF events, BCI2000 state variables will also be mapped to additional signal channels the same way as for EDF.		*Besides GDF events, BCI2000 state variables will also be mapped to additional signal channels the same way as for EDF.
	*BCI2000 parameters ~~cannot be represented in~~ GDF format. ~~Setting the <code>SaveAdditionalParameterFile</code> parameter to ''1'' will save~~ a ~~separate BCI2000~~ parameter ~~file along with the GDF data file~~.		*Since version 2.0, GDF provides additional header space for metadata which is organized as a sequence of tag/length/value structures. BCI2000 uses such a structure tagged with a "BCI2000" tag to store parameters. Within the GDF data field, the same human readable format is used as it applies to �[[Technical_Reference:Parameter_File\|BCI2000 parameter files]], i.e. a sequence of [[Technical_Reference:Parameter_Definition\|parameter definition lines]].

	Output in GDF file format is implemented by the [[User Reference:GDFFileWriter\|GDFFileWriter]] component.		Output in GDF file format is implemented by the [[User Reference:GDFFileWriter\|GDFFileWriter]] component.

Mellinger: /* GDF File Format */

2008-08-08T14:13:20Z

GDF File Format

← Older revision		Revision as of 14:13, 8 August 2008
Line 58:		Line 58:
	introduces an event table, and provides standardized encoding of events.		introduces an event table, and provides standardized encoding of events.

	*Currently, BCI2000 supports Version 1.25 of the GDF format specification.		*Currently, BCI2000 supports Version 2.10 of the GDF format specification.
	*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 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.
	*Besides GDF events, BCI2000 state variables will also be mapped to additional signal channels the same way as for EDF.		*Besides GDF events, BCI2000 state variables will also be mapped to additional signal channels the same way as for EDF.
Line 66:		Line 66:

	====References====		====References====
	*A. Schlögl et al, ''GDF: A General Data Format for Biosignal Data: Version 1.25'', http://~~bci~~.~~tugraz.at~~/~~~schloegl~~/~~matlab~~/~~eeg/gdf4/TR_GDF.pdf~~		*A. Schlögl et al, ''GDF: A General Data Format for Biosignal Data: Version 2.10'', http://arxiv.org/abs/cs.DB/0608052
	*A. Schlögl, ''BIOSIG'', http://biosig.sf.net/, 2003-~~2007~~.		*A. Schlögl, ''BIOSIG'', http://biosig.sf.net/, 2003-2008.

	==See also==		==See also==

Mellinger: /* GDF File Format */

2008-02-27T10:49:40Z

GDF File Format

← Older revision		Revision as of 10:49, 27 February 2008
Line 62:		Line 62:
	*Besides GDF events, BCI2000 state variables will also be mapped to additional signal channels the same way as for EDF.		*Besides GDF events, BCI2000 state variables will also be mapped to additional signal channels the same way as for EDF.
	*BCI2000 parameters cannot be represented in GDF format. Setting the <code>SaveAdditionalParameterFile</code> parameter to ''1'' will save a separate BCI2000 parameter file along with the GDF data file.		*BCI2000 parameters cannot be represented in GDF format. Setting the <code>SaveAdditionalParameterFile</code> parameter to ''1'' will save a separate BCI2000 parameter file along with the GDF data file.

			Output in GDF file format is implemented by the [[User Reference:GDFFileWriter\|GDFFileWriter]] component.

	====References====		====References====

Mellinger: /* EDF File Format */

2008-02-27T10:49:06Z

EDF File Format

← Older revision		Revision as of 10:49, 27 February 2008
Line 43:		Line 43:
	*BCI2000 state variables will be mapped to additional signal channels that contain a single sample for each data block.		*BCI2000 state variables will be mapped to additional signal channels that contain a single sample for each data block.
	*BCI2000 parameters cannot be represented in EDF format. Setting the <code>SaveAdditionalParameterFile</code> parameter to ''1'' will save a separate BCI2000 parameter file along with the EDF data file.		*BCI2000 parameters cannot be represented in EDF format. Setting the <code>SaveAdditionalParameterFile</code> parameter to ''1'' will save a separate BCI2000 parameter file along with the EDF data file.

			Output in EDF format is implemented by the [[User Reference:EDFFileWriter\|EDFFileWriter]] component.

	====References====		====References====

← Older revision		Revision as of 15:07, 21 January 2010
Line 70:		Line 70:

	==See also==		==See also==
	[[User Reference:DataIOFilter]]		[[User Reference:DataIOFilter]], [[User Reference:Matlab MEX Files#save_bcidat]]

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