Experimental Response and Synchronization Systems

In an EEG experiment, a visual stimulus may be presented by one computer, the participant’s response recorded by a separate response device, and EEG, eye tracking or physiology acquired by different systems. Each device has its own clock, buffering and transport path.

A reliable design therefore needs either a common timing reference or measured and documented latency for each component.

Dedicated response pads can provide predictable measured latency—the delay between a physical event and the time at which the system records it—, multiple buttons, external event markers and, in some models, compatibility with MRI environments.

Evaluation should consider not only average speed but also latency variability, the way event timing is marked and how the device integrates with the rest of the data stream.

Timing infrastructure becomes essential whenever behavioural events must be aligned with physiological or neural data at known latency.

A hardware trigger is a digital event marker sent at a precisely defined moment—for example when a stimulus appears or a button is pressed. These markers can be written directly into an EEG or physiology acquisition system. Software synchronization layers can align timestamped streams from multiple devices over a network.

Lab Streaming Layer (LSL) is an open software framework that timestamps data streams from different devices, estimates differences between their clocks and aligns the streams on a common time base. [1] Display refresh, audio latency, USB buffering and device firmware can still require independent validation.

Stimulus software, response devices, triggers, sampling rates and data export should be tested as a complete system before participants are recorded. Experimental software such as PsychoPy supports controlled stimulus and behavioural task construction, while hardware and software synchronization methods connect those events to physiological recordings. [2]

In multi-device laboratories, interoperability, documented latencies and empirical timing validation are core parts of data quality.

Timing can be implemented with dedicated response devices, hardware event triggers, network-based synchronization, or combinations of these methods. Validation devices can be added when display or audio onset must be measured directly.