Information for formatting files and file naming is provided on this page for both Electroencephalograph (EEG) and Electrocardiograph (ECG) data. If your questions are not answered on this page, email your question to info@abvsciences.com.

Information for Analysis of the Electroencephalogram (EEG)

Data Segmented by Participant and Condition

Data to be processed by the URDA-EEG system are required to follow a strict naming convention which each filename indicates the participant number and a condition/type number. The user number has 3-digits (with a prefix sb) such that each participant has a unique identifier. Similarly, the condition/type number has 3-digits (with a prefix tp) indicating the condition to which the data belong.
For example, some acceptable file names are:

sb001_tp001.edf
sb001_tp002.edf
sb002_tp001.edf
sb002_tp002.edf
sb003_tp001.edf
sb003_tp002.edf

The file naming convention indicates there are 3 different participants with each having two experimental conditions.

Data Segmented by Participant Only (a continuous record of data containing multiple conditions)

If the objective is to employ the MOST-EEG algorithm, then it is best to upload data that are unsegmented for each participant. Doing so provides for better noise and signal characterization by the algorithm. In this case, a separate segmentation file will be required.

Information for Analysis of the Electrocardiograph (ECG)

Filenames follow a similar convention for ECG cleaning as for EEG cleaning/analysis with the exception of a “_ecg” added to the file name. Currently, only URDA-ECG only supports ASCII file formats.

File naming for multiple datasets and conditions is as follows:

sb001_tp001_ecg.txt
sb001_tp002_ecg.txt
sb002_tp001_ecg.txt
sb002_tp002_ecg.txt
sb003_tp001_ecg.txt
sb003_tp002_ecg.txt

In this example, there are datasets from 3 different participants for 2 different conditions. If there is no need to segment conditions, then one data file “sb001_tp001_ecg.txt” will suffice.