menu_book

Knowledge Base

Documentation, guides, and resources for Noldus products.

EthoVision XT 18 - THC - Trial and Hardware Control - Analysis Of Trial Control Data (Continued)

Last updated: Jul 30, 2026

Batch Analysis

To run different analyses with different combinations of these filters, do the following:

  1. Click Batch.
  2. Select the profiles from the lists and click Add.
  3. Repeat the previous step for other combinations.
  4. Click Calculate.
  5. Select the combination of profiles from the lists on the toolbar to view the results.

Export Trial Control Data

You can export Trial Control data just like the other dependent variables.

  1. Choose Analysis > Export > Raw Data.
  2. Select the following:
    • Track & dependent variables. To export events and intervals defined in the Analysis profile. For example, actions and conditions and intervals in between. This option also includes hardware-based actions and conditions, not the actual communication signals.
    • Hardware log. To export the communication signals between EthoVision XT and the hardware device.
  3. Click Start Export.

Exported Raw Data File

In the exported raw data file, each Trial Control event or Trial Control state defined in the Analysis Profile is stored in a column.

A Trial Control event is exported as 1 in the row corresponding to the time when the event occurs. In the other rows, it is exported as 0.

A Trial Control state interval is exported as 1 in the rows corresponding to the time included in the interval. If the interval occurs in multiple instances during the trial, you will see multiple segments of 1.

For more information about exporting track data, see Export Tracks in the EthoVision XT Help.

Hardware Log File

When you select Hardware log in the export screen, hardware events are exported to a separate file. The data are organized in columns as follows:

  • Time is the time when the signal value is read or the action is taken. Note: This is the time elapsed since the start of the trial, not the start of tracking. For lickometers, values are updated about every 2 s.
  • Device ID is the name of the physical device that the event refers to.
  • Command/Signal is the type of data (Command, or Signal).
  • Name is the name of the command or signal.
  • Value is the value of the signal at that time.

Each row of the file contains one of the two:

  • Rows marked with Signal. The value of the signal since the last time the device was read (for example, the number of licks or the duration of licks since the last reading). Duration of licks is expressed in milliseconds.
  • Rows marked with Command. The command (for example, Drop pellet).

The hardware log file is one per trial, no matter how many arenas and devices are used. If you re-do a trial, the log files recorded with the previous instance of the trial are deleted.

In order to be logged, hardware devices must be connected to the computer and configured in EthoVision XT.

Notice that the Time in the Hardware log file is the time since the start of the trial, while the time in the Track data file is the time since the start of tracking.

Example: If you have defined a command like Drop pellet as a Trial Control event, to find a specific Drop pellet event in the data file, take note of the Time in the Hardware log file for that event and locate that time in the Time trial column in the Track data file.

For Pellet dispensers: Number of drops is the feedback signal sent by the device to EthoVision. Usually it is recorded 0.04 s after the actual Drop pellet command.

Choose Hardware log if you want to export communication data between EthoVision and the hardware device, even when the device was not used during the trial.

If you select both Track data and Hardware log, data are exported in separate files when choosing the Text format, and in one file when choosing the Excel format. In the Excel file, Track data and Hardware log data are stored in separate sheets.

Source: EthoVision XT 18 - THC - Trial and Hardware Control, Noldus Information Technology

Have a technical question?

Our support team can help you with installation, configuration, or compatibility questions.

Noldus is here to assist you throughout the whole process.

shopping_bag
check_circle

Thank you!

We'll get back to you shortly.

error

Please correct the following errors:

error

error

error

error

By clicking Submit, you consent to Noldus processing your data as described in our privacy policy.