# Pupillometry ![Musician wearing headset during concert][1] ## Description Pupillometry data were collected using Pupil Core headsets from Pupil Labs ([https://pupil-labs.com/products/core/][2]). Data include pupillometry, eye gaze, and video recordings without audio. One eye tracking headset was worn by each performer for during the morning experiment and the third set of evening concert music of the concert. ## Collection Strategy ### Setup HP Laptops running Pupil Capture (for recording) and Pupil Player (for post-processing). The laptops were connected via a shared (cabled) network. One of the laptops received triggers from the OptiTrack motion capture system via a connected arduino and ran a Python script to note the timestamps of received triggers. Musicians wore the Pupil Cores onstage. The computers that collected the recordings were set up along the side of the stage. ### Method Each performer wore a Pupil Core headset that tracked gaze and pupil size from both eyes (1st violinist, violist, cellist) or just the left eye (2nd violinist). During the morning experiment, the eye cameras were adjusted to get a correct model of the eye and calibrated prior to recording. Calibration was done by having the performers follow visual targets projected onto a large screen at the back of the stage. During the concert, it was not possible to run a calibration before recording, so this will be done retrospectively using the recorded data. ### Syncing #### Pupil Core data The Pupil Groups and Time Sync plugins, which are run within the Pupil Capture software, allow for time-synching of recording start and stop times across the four recording computers as long as they are on a shared network. (Note that firewalls and Wi-Fi must be switched off on all computers). Computer “Presentation 1” was set as the Clock Master in Time Sync settings. #### Pupil Core and OptiTrack motion capture Computer “Presentation 1” ran a Python script that documented the timestamps of incoming TTL triggers, which were sent by OptiTrack and received via an arduino. The procedure for recording was to initiate the Pupil Core recordings, run the script, then start the OptiTrack recording. Trigger times are stored alongside other Pupil Core data in a txt file. ## Data ### Calibration ![Concert Calibration][3] Calibration was performed before the morning experiment but will be done retrospectively for the concert data as it was not possible to calibrate prior to the concert recordings. ### Quality Pupil data are of satisfactory quality. The cellist’s pupil data is substantially noisier than the others’ because he had to wear the Pupil Core on top of his glasses. ### File Information - Format mp4 (world camera video) and npy, pldata, csv, intrinsics, json (files for processing in Pupil Player) - Settings 120 Hz; Pupil Groups and Time Sync (plugins) turned on - Naming Files are named with device identifier, instrument, and trial identifier. Example P1_violin2_static_baseline_pupil_positions.csv This data is consented for openly sharing and has no copyright associated with it. [1]: https://www.uio.no/ritmo/english/news-and-events/events/musiclab/2021/dsq/photos/ritmo/20211026_p1024060.jpg "Musician wearing headset during concert" [2]: https://pupil-labs.com/products/core/ "Pupil Core" [3]: https://www.uio.no/ritmo/english/news-and-events/events/musiclab/2021/dsq/photos/ritmo/p1023979.jpg "Concert calibration"