Experiment Configurations
In this article:
EventIDE provides robust support for managing custom configurations, enabling you to tailor hardware settings, stimulus parameters, and interface behaviors without duplicating your experiment file. This functionality is ideal for preparing different experimental setups—such as switching between eye-tracking and mouse-based versions—while keeping the core logic of the experiment intact.
What Are Configurations?
A configuration in EventIDE defines a complete set of runtime parameters for a specific experimental context. These may include:
Selected input and output devices (e.g. eye tracker, joystick, EEG amplifier)
Display resolution and monitor settings
Stimulus parameters (e.g. contrast level, duration)
Communication protocols and data logging formats
Each configuration builds upon a shared Base Configuration, but can override or replace specific elements with alternative versions, depending on the desired setup.
Configuration Records
Each configuration may consist of multiple configuration records, which allow precise control over how the experiment is modified when the configuration is applied. Each record performs one of two actions:
Override property values of an element in the Base Configuration, using an identical copy with updated settings.
Replace an element with a homotypic element—a structurally equivalent element from the same category—allowing reconfiguration for different hardware or input modalities (e.g. replacing a mouse tracker with an eye tracker).
This mechanism provides high flexibility in adjusting hardware bindings and settings while preserving the overall experiment structure.
Managing Configurations
To add and manage experiment configurations, go to the Configurations ribbon tab and follow these steps:
Click Add Configuration in the ribbon bar. This will create a new configuration template displayed in the main window.
Follow the three-step interface to define a new configuration record:
Step 1: Select an element in the Base Configuration that you wish to replace.
Step 2: Choose a replacing element from the experiment that will take its place.
Step 3: Confirm the replacement and add the configuration record.
You can create multiple records within the same configuration, each targeting a different element. This allows you to build complex configuration profiles that modify several components simultaneously.
In the configuration editor:
To rename a configuration, double-click its name in the left panel.
To add a configuration description, use the text box located below the configuration records.
The currently active configuration is shown in the drop-down list in the ribbon bar. You can switch between configurations at any time. To prompt a selection window on experiment startup, toggle the "Select configuration on loading" option in the ribbon bar. This is useful if your experiment supports multiple hardware setups or testing environments.
By using configuration records and profiles in this way, you can flexibly adapt your experiment without duplicating or rewriting its structure.
Running Experiment with Configurations
When launching your experiment:
Select the desired configuration from the drop-down list in the Configurations tab.
EventIDE automatically applies all configuration records before the experiment starts.
You can switch configurations to support different environments (e.g. lab vs field), hardware setups, or user groups.
Best Practices for Configurations
Use configurations to create hardware-agnostic experiment files, which can adapt to various environments with minimal setup.
Apply configuration records selectively, targeting only those elements that differ across setups.
Keep the Base Configuration general, and layer specific changes through configuration records.
Use descriptive names for configurations, such as Eye-Tracking Setup, Mouse Demo, or VR Training.
Test each configuration independently to ensure device compatibility and stable runtime behavior.
With the configuration system in EventIDE, you can efficiently manage hardware variability, streamline setup changes, and ensure consistency across different versions of your experiment—all within a single, maintainable file.