ℹ️ Storing results from the experiment in external logfiles

Now we have the task running, with config files feeding the task. No experiment without collecting data, so we need to store some values in the results.

There are multiple paths of logging data, but we will focus on storing it to disk in this example. The framework uses the UXF framework, EDIA uses that when using `Experiment.instance.addtotrialresults' in your script.

If you have run the project in the editor, you now have a new folder called logfiles next to the folder of the Unity project.

• Show

We will have a look at them one by one.

trial_results.csv

This would be the main file where all results from the trials are logged into.

• Show file

A few key thing to know:

• By default the framework adds high level experiment related keys to it, like session number, block, start_time, etc.

• By default all the settings from the config files are added

  <aside>

  ⚠️ Except the entires that user a “_” character as a prefix in the key value. I.e. “_key”

  </aside>

• When the UXF tracker is enabled for the XR Rig, references to the tracker files per trial are included.

  • Show

• You can add a <key,value> by using the Experiment.Instance.AddToTrialResults().

We used:

  Experiment.Instance.AddToTrialResults("selection", _selectedStimulus.ToString());
  Experiment.Instance.AddToTrialResults("correct", isCorrect.ToString());

Take a look at the trialresults.csv file in a more view-friendly matter:

trial_results

As you can see, the selection and the correct values are logged per trial.

./other

Experiment related logfiles are stored in here. These are:

• executionOrder.csv This stores the main statemachine timestamps.
  • Show
• markerLog.csv This stores the markers including timestamp that are called in the experiment with Experiment.Instance.StoreMarker("some marker"); Handy for storing a moment in time with a label.

./session_info

Session related logfiles are stored in here. These are:

• Log.csv An export of the debug.log messages from the Unity engine. Handy for debugging on builds.
• participant_details.csv The participant details provided in the session-info.json file.
• settings.json Session settings