Prepare inputs and open a recording

Required inputs

Keep the original recording and its matching timing file available. Check:

• the input format and actual sample rate;
• a sensor configuration matching the selected recorded channels and reference;
• the timing file <recording>.t and selected timing tag;
• a writable output location with sufficient free space;
• compatible earlier checkpoints if starting part-way through the pipeline.

Use MARKER to prepare events and condition codes before ERPERF. Missing timing files or tags stop processing; ERPERF does not silently reconstruct them from the recording’s trigger channel.

Start and inspect

Select ERPERF, open a recording, and inspect the channel selection and log. The log identifies the sensor configuration, timing tag and event counts. Unexpected counts should be resolved before filtering, epoching or grouping.

For batch processing, list the original recordings rather than a mixture of raw and derived files. Later-step runs still start from the recording identity and locate compatible prerequisites. Choose the range on Flow control.

New derived chains are written under erperf/<recording>/; a compatible legacy root-level chain may remain beside the raw file when reused. Do not move individual prerequisite files in isolation. See bundles and troubleshooting.