Event File Format - Revision history

Mateusz at 14:05, 5 May 2021

2021-05-05T14:05:57Z

Mateusz at 14:05, 5 May 2021

2021-05-05T14:05:08Z

Robert: /* Additional Event Information */

2021-05-05T12:50:43Z

‎Additional Event Information

Robert at 12:49, 5 May 2021

2021-05-05T12:49:23Z

Jaehyun at 13:40, 13 February 2018

2018-02-13T13:40:42Z

Jaehyun at 15:32, 1 June 2017

2017-06-01T15:32:13Z

Robert at 14:07, 15 February 2017

2017-02-15T14:07:35Z

Andre: Changed level of "Overview" to a level 3 header.

2016-05-12T11:48:28Z

Changed level of "Overview" to a level 3 header.

Andre: Added extra level 2 header to push the contents box to the top of the page.

2016-05-12T11:44:22Z

Added extra level 2 header to push the contents box to the top of the page.

Harald at 15:05, 8 April 2016

2016-04-08T15:05:03Z

@@ Line 15: / Line 15: @@
 === File Header ===
-The header is comprised of abbreviated descriptions for each column. Each entry in the data line must be specified in the header line at the correct column position. The order of the data elements and their description in the header line can be chosen arbitrarily and the entries can be separated by commas, tabs and/or spaces. The Code and one of ''Tms'', ''Tmu'' or ''Tsec'' is obligatory, other data elements can be omitted. The following codes are recognized by the ERP module:
+The header is comprised of abbreviated descriptions for each column. Each entry in the data line must be specified in the header line at the correct column position. The order of the data elements and their description in the header line can be chosen arbitrarily and the entries can be separated by commas, tabs and/or spaces. The Code and one of ''Tms'', ''Tmu'' or ''Tsec'' are obligatory, other data elements can be omitted. The following codes are recognized by the ERP module:
 * ''Code'' - event code (integer, see section [[#Event Codes|Event Codes]])
 * ''Tms'' - event time in milliseconds relative to the start of the data file or ''Tmu'' [in microseconds] or ''Tsec'' [in sec] (floating point value)

@@ Line 15: / Line 15: @@
 === File Header ===
-The header is comprised of abbreviated descriptions for each column. Each entry in the data line must be specified in the header line at the correct column position. The order of the data elements and their description in the header line can be chosen arbitrarily and the entries can be separated by commas, tabs and/or spaces. The last n data elements can be omitted, if they are neither Code nor one of ''Tms'', ''Tmu'' or ''Tsec''. The following codes are recognized by the ERP module:
+The header is comprised of abbreviated descriptions for each column. Each entry in the data line must be specified in the header line at the correct column position. The order of the data elements and their description in the header line can be chosen arbitrarily and the entries can be separated by commas, tabs and/or spaces. The Code and one of ''Tms'', ''Tmu'' or ''Tsec'' is obligatory, other data elements can be omitted. The following codes are recognized by the ERP module:
 * ''Code'' - event code (integer, see section [[#Event Codes|Event Codes]])
 * ''Tms'' - event time in milliseconds relative to the start of the data file or ''Tmu'' [in microseconds] or ''Tsec'' [in sec] (floating point value)

@@ Line 79: / Line 79: @@
 The event reaction time, event reaction code and event comment are represented by the comment in the main module as "''Comment (Rx,T____)''", where ''Comment'' is the event comment, ''x'' describes the reaction code and the underscored line will be filled with the reaction time. Reaction time and reaction code are only read if the event code specifies it as a trigger.
-A "New Segment" event can include time information that defines the starting time of the segment. This is defined in the ''TriNo'' column of the event file. The format is YYYY-MM-DDTHH:MM:SS, e.g. 2010-04-26T15:30:20.31 (note: seconds are a decimal number). If no time is defined, use a hyphen ('-'). See [[#Examples|below]]) for an example.
+A "New Segment" event can include time information that defines the starting time of the segment. This is defined in the ''TriNo'' column of the event file. The format is YYYY-MM-DDTHH:MM:SS, e.g. 2010-04-26T15:30:20.31 (note: seconds are a decimal number). If no time is defined, use a hyphen ('-'). See [[#Examples|Examples]] below.
 An "Average Segment" includes the prestimulus baseline interval in microseconds. This is defined in the ''TriNo'' column of the event file.

@@ Line 2: / Line 2: @@
 |title = Module information
 |module = BESA Research Basic or higher
-|version = 5.2 or higher
+|version = BESA Research 5.2 or higher
 }}

@@ Line 6: / Line 6: @@
 === Overview ===
 Event files (extension *.evt) contain triggers and events and can be loaded as an additional file to provide more information about the whole course of an EEG/MEG recording.
 An event file can be edited by opening it in any text editor, e.g. Notepad. It is also possible to create new event files from scratch which can be imported into the data file later.
@@ Line 13: / Line 14: @@
 === File Header ===
 The header is comprised of abbreviated descriptions for each column. Each entry in the data line must be specified in the header line at the correct column position. The order of the data elements and their description in the header line can be chosen arbitrarily and the entries can be separated by commas, tabs and/or spaces. The last n data elements can be omitted, if they are neither Code nor one of ''Tms'', ''Tmu'' or ''Tsec''. The following codes are recognized by the ERP module:
 * ''Code'' - event code (integer, see section [[#Event Codes|Event Codes]])
@@ Line 23: / Line 25: @@
 === Event Codes ===
 The event code Code must be one of the following integers:
@@ Line 71: / Line 74: @@
 | Average segment
 |}
 === Additional Event Information ===
 The event reaction time, event reaction code and event comment are represented by the comment in the main module as "''Comment (Rx,T____)''", where ''Comment'' is the event comment, ''x'' describes the reaction code and the underscored line will be filled with the reaction time. Reaction time and reaction code are only read if the event code specifies it as a trigger.
 A "New Segment" event can include time information that defines the starting time of the segment. This is defined in the ''TriNo'' column of the event file. The format is YYYY-MM-DDTHH:MM:SS, e.g. 2010-04-26T15:30:20.31 (note: seconds are a decimal number). If no time is defined, use a hyphen ('-'). See [[#Examples|below]]) for an example.
@@ Line 78: / Line 83: @@
 === Requirements ===
 The file is valid if the header line contains at least the entries Code and one of ''Tms'', ''Tmu'' and ''Tsec''. The header specifications are case insensitive.
 The file is invalid, if
-• there are ambiguities in the header
+* there are ambiguities in the header
-• there is a data type mismatch in the data line
+* there is a data type mismatch in the data line
-• an event time specifies an event which happened later than the end of the acquisition
+* an event time specifies an event which happened later than the end of the acquisition
 Each omitted data entry is set to 0 or empty string by default.
 A line with an invalid or unknown event code ''Code'' is skipped.
 === Examples ===
-Here are a couple of typical examples:<br>
 '''1) Simple trigger file'''
 {| style="border-spacing: 2px; border: 0px white;"
@@ Line 315: / Line 323: @@
 The file contains two average segments. The first, with a prestimulus interval of 100 ms, has a duration of 1100 ms. The second, with a prestimulus interval of 200 ms, has a length up to the end of the data file.
-−
 This example event file can be downloaded here: [[Media:EventFileExample6.evt|Example 6]]
 [[Category:ERP/ERF]] [[Category:Data Import/Export]]

@@ Line 88: / Line 88: @@
 === Examples ===
 Here are a couple of typical examples:<br>
-'''1.) Simple trigger file'''
+'''1) Simple trigger file'''
 {| style="border-spacing: 2px; border: 0px white;"
 | Tms
@@ Line 128: / Line 128: @@
 This example event file can be downloaded here: [[Media:EventFileExample1.evt|Example 1]]
-'''2.) Trigger file with reaction code and reaction time'''
+'''2) Trigger file with reaction code and reaction time'''
 {| style="border-spacing: 2px; border: 0px white;"
 | Tms
@@ Line 175: / Line 175: @@
 This example event file can be downloaded here: [[Media:EventFileExample2.evt|Example 2]]
-'''3.) Event file without triggers'''
+'''3) Event file without triggers'''
 {| style="border-spacing: 2px; border: 0px white;"
 | Tmu
@@ Line 212: / Line 212: @@
 This example event file can be downloaded here: [[Media:EventFileExample3.evt|Example 3]]
-'''4.) File including triggers and events'''
+'''4) File including triggers and events'''
 {| style="border-spacing: 2px; border: 0px white;"
 | Tms
@@ Line 273: / Line 273: @@
 This example event file can be downloaded here: [[Media:EventFileExample4.evt|Example 4]]
-'''5.) New Segments'''
+'''5) New Segments'''
 {| style="border-spacing: 2px; border: 0px white;"
 | Tms
@@ Line 296: / Line 296: @@
 This example event file can be downloaded here: [[Media:EventFileExample5.evt|Example 5]]
-'''6.) Average Segments'''
+'''6) Average Segments'''
 {| style="border-spacing: 2px; border: 0px white;"
 | Tms

← Older revision		Revision as of 14:07, 15 February 2017
Line 318:		Line 318:
	This example event file can be downloaded here: [[Media:EventFileExample6.evt\|Example 6]]		This example event file can be downloaded here: [[Media:EventFileExample6.evt\|Example 6]]

−	[[Category:ERP/ERF]]	+	[[Category:ERP/ERF]] [[Category:Data Import/Export]]