Knowledge Base

The Experiment Log File

The Experiment log file is started at the moment a GLP experiment is created. Changes made by the user that affect the data and results of an experiment can be traced back in the log file.

These changes are logged from the moment you actually start acquiring data. At that moment a snapshot is taken of the various settings in your experiment and this snapshot is logged. Thereafter, all changes that can affect your data are logged.

When a user makes changes to settings (for example, in the Trial List or Trial Control Settings) and/or leaving a Setting, the user is prompted to add a comment to the Experiment log file. A new snapshot is then taken when new data are acquired. When the user cancels this automatic pop-up or does not enter a comment, a line appears in the Experiment log file with user name, date and time but without a comment.

To Add a Comment to the Experiment Log File

1. Choose File > Add log comment (Ctrl+L).
2. Type in comments and click OK.

To View the Experiment Log File

Before you can view an experiment log file, you need to open the corresponding experiment. To view the experiment log file in EthoVision XT:

1. Choose File > GLP Log Files.
2. In the GLP log window, select the experiment log file radio button. If necessary, click on one of the html links to go to a specific part of the Experiment log file.

To Delete the Experiment Log File

You can only clear the contents of the Experiment log file, not delete it. You can only clear the Experiment log file when you have the user management right to Delete Trials and Clear Log.

1. Choose File > GLP Log Files.
2. Select Experiment log file and click the Clear Log button.

To Export the Experiment Log File

1. Choose File > GLP Log Files, and click the Export button, or in the Experiment Explorer, under Export, click GLP Log.
2. Select Experiment log file.
3. Browse to the folder where you want to export the log file to and click OK.

Notes

• In the case of large experiments, when the log file exceeds a size of 1 MB, it is split into multiple log files.
• The export format is HTML (*.html). The name of the export file is GLP-[Experiment name](n), where n is a progressive number.
• Experiment Settings, Arena Settings, Trial list, Trial Control Settings and Detection Settings are not stored in the log file until the first data are acquired. After that, only changes are logged.
• Logged Arena Settings include a screenshot of Arenas and their Calibrations. It also contains a screenshot of each Zone Group and its Zones.
• If your current experiment is not set for Quality Assurance, there is no Experiment log file present.
• The suggested export location is the experiment's Export Files folder.

Create a GLP Experiment from a Template

Aim

Create a new experiment with all the right default settings, but without tracks and an Experiment log file, based on an existing GLP experiment.

Prerequisites

• You must have the User Management right to delete trials and clear log.
• You have a GLP experiment that you want to use as a template, for example an experiment with specific arenas and zones.

Procedure

1. Choose File > New template experiment or press Ctrl+T.
2. In the Template option window, select Use a custom template.
3. Click Browse and select the existing GLP experiment you want to use as a template. Select the file with extension *.evxt and click OK.
4. Type in the name of the new experiment.
5. Select GLP experiment and click OK.

Notes

• Create a backup of the template and store it in a safe place.
• To open a GLP experiment, you need an EthoVision XT license that includes the Quality Assurance module.
• In a GLP experiment you cannot change or edit the zones already used in Acquisition.
• If your license includes the Quality Assurance module, you can still create or open non-GLP experiments. In that case User Management does not apply and no log file is kept.
• Multiple copies of the same version of EthoVision XT installed on the same computer share the General log file. Different versions of EthoVision XT installed on the same computer each have their own General log file.

Troubleshooting

Main Topics and Tasks

• Troubleshooting: Installation and License
• Troubleshooting: General
• Troubleshooting: Pylon Camera Software
• Troubleshooting: Camera
• Troubleshooting: Video Image
• Troubleshooting: Arenas and Zones
• Troubleshooting: Detection
• Troubleshooting: Data Acquisition
• Troubleshooting: External Data
• Troubleshooting: Track Editor
• Troubleshooting: Statistics
• Troubleshooting: Behavior Recognition
• Troubleshooting: Deep Learning
• Troubleshooting: Data Visualization
• Troubleshooting: Control of Hardware Devices
• Troubleshooting: DanioVision
• Troubleshooting: Live Mouse Tracker
• Troubleshooting: Import Trials
• Troubleshooting: Quality Assurance (GLP)

Troubleshooting: Installation and License

Issues: Installation

• Error message (ID 10020)
• Installation stops halfway
• Blue-screen crash during installation of Euresys Multicam
• The hardware key does not light up
• When I start EthoVision XT, I get the message: No license key found
• Installation of EthoVision XT fails, likely due to an error during installation of the Basler camera drivers
• I have realized that I installed the wrong camera driver software. What can I do?

Issues: License

• My EthoVision XT license has expired. What should I do?
• I am trying to upgrade my license, but the upgrade key is not being accepted
• I cannot start EthoVision XT with a floating license
• I purchased an add-on module but I cannot use it
• I purchased an add-on module. How do I update my license?
• I entered a license key but an error message shows a different one
• I need to create a Firewall rule to access the Noldus license server. Which port do I need to access?
• I cannot deactivate a license. The menu item Deactivate license is greyed out
• EthoVision XT is in Analysis mode, but there is no way to work with a full license
• Message: "Activation not complete"
• Message: "License already activated..."

Source: EthoVision XT 19 Help - EthoVision XT and Quality Assurance, Noldus Information Technology