___________________________________________________________________________________________________________________ *Headphone Check Procedure* ___________________________________________________________________________________________________________________ Script Author: Katja Borchert, Ph.D. (katjab@millisecond.com) for Millisecond Software, LLC Date: 12-30-2020 last updated: 02-23-2022 by K. Borchert (katjab@millisecond.com) for Millisecond Software, LLC Script Copyright © 02-23-2022 Millisecond Software ___________________________________________________________________________________________________________________ BACKGROUND INFO ___________________________________________________________________________________________________________________ This script implements the Headphone Check Procedure by Woods et al (2017). The Headphone Check Procedure is intended to be easy over headphones but difficult over loudspeakers due to phase-cancellation. This procedure can thus be used online for screening purposes for procedures that require headphone usage. Reference //Headphone Check: Woods, K.J.P., Siegel, M.H., Traer, J, & McDermott, J. H. (2017). Attention, Perception, and Psychophysics, 79, 2064–2072 https://doi.org/10.3758/s13414-017-1361-2 https://github.com/mcdermottLab/HeadphoneCheck ___________________________________________________________________________________________________________________ TASK DESCRIPTION ___________________________________________________________________________________________________________________ Participants listen to 3 tones and have to decide which of the tones is the quietest. ___________________________________________________________________________________________________________________ DURATION ___________________________________________________________________________________________________________________ the default set-up of the script takes appr. 3 minutes to complete ___________________________________________________________________________________________________________________ DATA FILE INFORMATION ___________________________________________________________________________________________________________________ The default data stored in the data files are: (1) Raw data file: 'headphonecheck_raw*.iqdat' (a separate file for each participant)* build: The specific Inquisit version used (the 'build') that was run computer.platform: the platform the script was run on (win/mac/ios/android) date, time: date and time script was run subject, group: with the current subject/groupnumber session: with the current session id blockcode, blocknum: the name and number of the current block (built-in Inquisit variable) trialcode, trialnum: the name and number of the currently recorded trial (built-in Inquisit variable) Note: trialnum is a built-in Inquisit variable; it counts all trials run; even those that do not store data to the data file. countTestTrials: test trial counter index: randomly selected itemcounter for the test soundfile testSound: the played test soundfile correctResponse: the correct response for the played test soundfile response: the participant's response (first, second, third) correct: accuracy of response: 1 = correct response; 0 = otherwise latency: the response latency (in ms); measured from: offset of sound (2) Summary data file: 'headphonecheck_summary*.iqdat' (a separate file for each participant)* inquisit.version: Inquisit version run computer.platform: the platform the script was run on (win/mac/ios/android) startDate: date script was run startTime: time script was started subjectid: assigned subject id number groupid: assigned group id number sessionid: assigned session id number elapsedTime: time it took to run script (in ms); measured from onset to offset of script completed: 0 = script was not completed (prematurely aborted); 1 = script was completed (all conditions run) numberCorrectResponses: number of correct responses propCorrect: proportion correct responses headphoneCheckPass: 1 = soundCheck passed (proportion correct >= parameters.passCriterium) 0 = soundCheck failed * separate data files: to change to one data file for all participants (on Inquisit Lab only), go to section "DATA" and follow further instructions ___________________________________________________________________________________________________________________ EXPERIMENTAL SET-UP ___________________________________________________________________________________________________________________ Participants work through 1. Sound Calibration: set volume so that the calibration sound can be heard comfortably 2. Test: 6 trials - each trial randomly selects one of the 6 provided soundfiles - participants are asked to play the soundfiles are are asked to select a button that corresponds to the soundfile that was the 'quietest' ___________________________________________________________________________________________________________________ STIMULI ___________________________________________________________________________________________________________________ downloaded from: https://github.com/mcdermottLab/HeadphoneCheck/tree/master/assets ___________________________________________________________________________________________________________________ INSTRUCTIONS ___________________________________________________________________________________________________________________ provided by Millisecond Software - The instructions are based on the instructions provided by the Behavioural Laterality Project (Parker et al, 2020) as well as information provided at https://github.com/mcdermottLab/HeadphoneCheck //Behavioural Laterality Battery: Adam J. Parker , Zoe V. J. Woodhead , Paul A. Thompson & Dorothy V. M. Bishop (2020): Assessing the reliability of an online behavioural laterality battery: A pre-registered study, Laterality, DOI: 10.1080/1357650X.2020.1859526 To link to this article: https://doi.org/10.1080/1357650X.2020.1859526 https://gorilla.sc/openmaterials/104636 ___________________________________________________________________________________________________________________ EDITABLE CODE ___________________________________________________________________________________________________________________ check below for (relatively) easily editable parameters, stimuli, instructions etc. Keep in mind that you can use this script as a template and therefore always "mess" with the entire code to further customize your experiment. The parameters you can change are: