Paradigm File Format in BESA

General remarks

A paradigm description file (“PDG file”) contains the information which is relevant for describing an experimental setup in terms of the stimulation and response events that occurred. To describe the experimental paradigm, three terms are introduced:

1. An attribute is used to group trigger events into a certain class. For example, in an auditory experiment, triggers could be grouped according to an attribute “modality” to distinguish stimulation and response, and another attribute “side” to distinguish left and right.
2. An attribute value defines how a trigger event is classified in the class defined by an attribute. For example, the trigger with the code 1 could be a tone stimulus, and the trigger with the code 2 could be the subject’s response. That means that for the “modality” attribute, trigger 1 would receive an attribute value “tone”, whereas trigger 2 would receive an attribute value “response”.
3. A condition defines which trigger events form the set of events that should be averaged. For example, this could simply be all trigger events with the modality “tone”, or all trigger events which have the modality “response”, and follow a trigger event with the modality “tone”.

The PDG file is written in ASCII format and can thus be viewed and edited in any text editor. It is subdivided into a maximum of 9 sections:

1. [Attributes] Attributes which are used to group the trigger events. This section is mandatory.
2. [Values] A table of attribute values which are defined for the triggers used in the experiment.
3. [Names] Names of conditions which are defined in detail in section 8
4. [Epochs] For each condition, averaging epochs, baseline epochs, and some other epochs are defined
5. [Thresholds] Threshold settings used for artifact rejection
6. [Averaging] Defines which conditions are selected for averaging
7. [Filter] Filter settings for averaging
8. [TimeFrequency] Settings for time-frequency analysis
9. [Selections] Each condition is written here as a statement using Boolean logic
10. [ArtifactScan] The artifact scan results are written here

Most sections can be omitted; their entries are then filled with default values. The default settings are given in the detailed description (see below). The most relevant sections for describing an experiment are Attributes, Values, and Selections.

Connection to BESA paradigm editing tool: Sections 1 and 2 define entries in the “Trigger” tab. Sections 3 and 9 define entries in the “Condition” tab. Section 4 defines entries in the “Epoch” tab. Sections 5 and 10 define entries in the “Artifact” tab. Section 6 defines entries in the “Average” tab. Section 7 defines entries in the “Filter” tab. Section 8 defines entries in the “Coherence” tab (if available).

All values can be edited in the respective tabs of the paradigm editing tool.

Detailed description of the sections

Attributes

This section is mandatory. It holds the attributes which are used to group the trigger events. The first attribute is always the trigger code (“code”). Attributes are separated by a tabulator. By default, the ERP module defines a second attribute “name” which can take trigger names as attribute values.

Example:

[Attributes]
code	name	modality