Data Collection

Every time you run an experiment in EventIDE, a built-in data file called the Base Report is automatically created. This file is an internal CSV-formatted log with high-speed writing, built-in crash protection, and no need for manual file handling. You can send data to the Base Report using either the Reporter element or by assigning values to the default Report proxy variable in your code.

In most behavioral experiments, data is collected in a structured table format—each row representing a trial, and each column representing a variable (e.g. trial number, reaction time, stimulus ID). EventIDE streamlines this workflow using the Reporter element, which automatically collects and logs selected variables without writing code.

To use the Reporter element:

1. Insert the Reporter element into the last event in your trial loop.

2. In the Property Panel, click the button next to Data Designer to open the visual configuration tool.

   

3. Click Select variables and choose from the list of proxy variables or global variables.

   1. Expand structured variables (e.g. colors, points) to select individual fields.

   2. Recompile the Header snippet to ensure newly declared variables are shown.

4. Reorder columns by dragging headers in the preview area.

5. Set layout options: choose column or row format, add/remove headers, and set delimiters (e.g. semicolon, comma, tab).

6. Review the preview of the output at the bottom of the Data Designer.

7. Back in the Property Panel, configure:

   1. Recording Schedule – choose when data is logged (e.g. at event offset, experiment end).

   2. Recording Destination – save to Base Report or a new file.

   3. Run the experiment and review the resulting data in the Data Report tab.

Each eye-tracker element in EventIDE (including virtual trackers like the Mouse Tracker) can log its data into a dedicated log file. These logs are configured individually using the Log Designer, available in the Property Panel of each eye tracker element.

Configuring Eye-Tracking Logs

1. Add a Tracking Element

   Add a relevant eye-tracker element from Eye Trackers category or the Mouse Tracker element from Mouse Touch Joystick category. Eye-tracking elements work in the global scope, so you do not need to place them in a specific event—they operate throughout the experiment once added.

   
   

2. Open the Log Designer

   Select the eye-tracker or Mouse Tracker element in the Elements Panel. In the Property Panel, click Open Log Designer.

   

   
   

3. Choose Logged Fields

   By default, all available data fields are preselected (these depend on the tracker model). You can remove some fields to exclude them from the log. You may also reorder columns by dragging headers.

   

   
   

4. Log Formatting Options

   Select whether to include column headers and experiment info in the log file. Choose the delimiter for the log file (semicolon, comma, tab, etc.)

   
   

5. Preview Log Output

   A preview of the formatted log appears at the bottom of the Log Designer window.

   
   

After setup, the Tracker Log file will automatically be listed in the Data Report ribbon tab. From there, you can view, export, or auto-export it just like any other report file.

Tip: You can create multiple eye-tracker logs in a single experiment—each configured independently for different devices or layers of analysis.

EventIDE supports a wide range of bio-signal acquisition hardware for EEG, ECG, EMG, and other physiological signals. Data can be streamed, processed, and recorded in real time, with full customization of sampling, analysis, and output format.

Typical Signal Processing Pipeline

1. Signal Acquisition

   • Add an element from the Signal Acquisition category (e.g. NI Port, MC Analog Port, etc.).

   • Configure input channels, sampling frequency, and buffer size in the Property Panel.

   • For full list of supported hardware refer to Signal Acquisition Category of the Element Library.

   

   
   

2. Signal Processing (Optional)

   Add real-time processors from the Signal Processing category:

   • PSD Analyzer – computes Power Spectral Density.

   • Phase Analyzer – estimates instantaneous signal phases.

   • Coherence Analyzer – calculates real-time magnitude-squared coherence between two input signals.

   • Pattern Detector – detects pre-defined signal patterns.

   • Oscillation Detector – detects regular oscillatory patterns in the signal.

   • Mixed Signal – computes the average of multiple signals and optionally subtracts a reference channel.

   • Single Channel Analyzer – analyzes and plots a single real-time signal from any acquisition element.

   • Multi Channel Analyzer – computes base statistics and plots multiple input signals in a vertically stacked view.

   • Other filters, extractors, and visualizers are also available.

   
   

3. Signal Logging

   Add a Signal File Writer element from the Signal Processing category to log processed or raw data. Supported file formats include: EDF, EDF+, and CSV. Configure the Signal File Writer in the Property Panel:

   • Select input signal channels.

   • Set output sampling rate and buffer size.

   • Choose output file format and log settings.

   

After configuration, the Signal File will also appear in the Data Report ribbon tab, where you can preview, export, or auto-export the recorded signal data.

If you wish to log custom variables (e.g. task parameters, computed values) as discrete-time signals, use the Proxy Variable Signal element:

• Select one or more proxy or global variables as signal inputs in the Properties Panel.

• Configure a sampling rate and buffer size.

• Use the Signal File Writer element to log these data as a time series, in synchrony with other recorded signals.

  

Example use case: Log changes in trial difficulty, participant accuracy, or task condition indicators alongside physiological signals.

These elements assist in logging, visualizing, or exporting additional data streams:

You can combine these tools to visualize or log supplementary data streams alongside your core trial data.

For fully custom logging, use the default proxy variable Report (a string) or create your own file handles in code snippets:

Basic row logging:

Report = TrialNumber + ";" + StimulusIndex + ";" + RT;

After the snippet executes, this line is appended to the Base Report.

Multiple lines in one snippet:

Report=Report+”\nTrial Number,StimulusIndex,RT”; // adds a new line with headers
Report=Report+”\n”+TrialNumber+”,”+StimulusIndex+”,”+RT; // adds a new line of separate data

Each assignment appends text to the report. The final string is written to file after the snippet finishes executing.

All collected data can be reviewed and exported using the Data Report ribbon tab. Available tools include:

• View Latest – Opens a viewer with all report files from the last run. You can export one or multiple reports.

• Export Latest – Export the most recent report to CSV or Excel. Excel export is only available if Excel is installed.

• Run History – Tracks all experiment runs and associated data reports. Open the Runs History viewer to inspect or export past reports. The application prompts monthly to clean up older runs; you may lock important reports to prevent deletion.

• Auto-Export – Automatically export data to a selected folder and format. Set this in the Data Report tab by toggling Auto-Export on and choosing a file type and destination.