1. In the web browser, open your personal UW email inbox through Outlook. You can do this through MyUW if needed.
2. In the top right corner, click the circle with your profile picture/initials.
3. Click Open another mailbox
4. Enter speechmotor@waisman.wisc.edu and click Open

This experiment is part of the cerebellar battery run in 2022-2023. For controls and patients, it is in the FIRST session.

In this battery, participants come in for multiple sessions and do multiple experiments in a row. As such, this is a bare bones document on how to run the experiment. Procedures for consent, hearing screening, awareness surveys, general equipment set up, and payment are not included in this document. See the documents below for how these procedures are implemented in this multi-study session: 

1. Protocol for cerebellar battery: controls
2. For patients

This is a reaching experiment, with a separate interface computer. 

The lights should be OFF for this experiment so the participant can only see the cursor, not their actual hand. 

These should not have any occasion to change between studies, but it is good to check anyway. Note that you should run these checks on the REACHING computer which is on the cart (not Quiberon). 

Check sampling rate of tablet: 

1. Click on Windows start button
2. In the search at the bottom, type in Wacom tablet properties, and click on it when it appears
3. Double click on the Intuos4 XL under "Device"
4. Make sure it is in  to be in "Recognition Data" mode

Check refresh rate of monitor: 

1. Click on the Windows Start button
2. Type in settings, click when it appears
3. Go to System > Display > Advanced Display Settings
4. There should be two monitors in the dropdown to choose your display. Select Display 2: VG248
5. The refresh rate is at the bottom. It should be 144.001 Hz 

Start the experiment by typing in run_cerebReachAdapt_expt and hitting enter. Enter the required responses. Then place the pen on the tablet. 

Tell the participant: 

“The point of this experiment is to better understand how the brain controls reaching movements. We will be measuring how accurately you can reach to targets in different locations. Your data will be used as a normative baseline for future comparisons with neurological patients. So, please try your best to pay attention and follow all instructions.”

“In this experiment, you will be playing a game where you’ll be trying to make quick and accurate reaches to different target locations. For each trial, you will move the cursor to a home location in the center, which will be indicated with a circle. Then you'll make a quick reach to a target that appears somewhere on the screen. You should reach as quickly and accurately as you can, and slice through the targets rather than stopping at the target”

“Please take some time now to adjust the seat height and scoot in close to the work station. You will be making many reaches towards the edges of the tablet, and I want you to be able to do that without moving any parts of your body other than your arm. Keep the same posture throughout the experiment, and rest your other hand in your lap. Be sure to not swirl around in the chair.”

You will hold this pen at the red base with your dominant hand – maintain the same grip throughout the experiment.  (demonstrate)

There are no pre-planned breaks, but if you need to rest for a bit, just wait before moving the cursor to the center for the next trial.

“Do you have any questions?”

“I’ll give you a minute to get comfortable before turning out the lights.”

After they are comfortable, turn off the lights, then press SPACE to start the experiment

Tell the participant: “Move your hand to the start circle and wait for the target to appear. Your goal is to move your hand to the target. Reach through the target as accurately as possible in a quick straight line. Once you start moving, follow all the way through. If you hear a knocking sound, that means that you moved fast enough and far enough for a good trial.”

Throughout the experiment, you should monitor how they are performing their reaches. You may have to issue corrections. Common issues:

• When they get “Too Slow” message: “The too slow message means that you did not move fast enough for a valid trial. Remember to slice through the targets with your hand.” This is related to movement time, not reaction time 

• If participant gets “slice through the target" message: “Remember to move accurately through the target in a quick, straight line.”

• If they are picking up paddle: Please don’t pick up the paddle and just slide it along the table.

Instructions will appear on the screen for the participant. In this phase, the cursor will move as they move their hand, but the direction that it moves will not correspond to where they are reaching. Their goal in this section is to move your hand directly to the target, ignoring the cursor. They should still reach as accurately as possible in a quick straight line and slice through the target. Be sure to give them this instruction verbally to make sure they understand.

If they have any questions, answer them. Press space when they are ready to begin. 

There are three washout phases. Participants will see instructions on the screen before each phase. Answer any questions they may have. When they are ready to continue, press space. 

Washout without feedback: In this block they will no longer see the cursor. They should continue to move their hand directly through the target.

Washout with feedback: In this block they will see the cursor again. They should continue to move their hand directly for the target. 

Anti-rotation washout with feedback: In this phase, the cursor will move as they move their hand, but the direction that it moves will not correspond to where they are reaching. Their goal in this section is to move your hand directly to the target, ignoring the cursor. They should still reach as accurately as possible in a quick straight line and slice through the target. 

There is no restart script. This is a relatively short experiment, and can be restarted if necessary. 

This experiment is part of the cerebellar battery run in 2022-2023. For controls and patients, it is in the FIRST session. This is after cerebReachAdapt so you do not need to re-deliver general instructions on how to reach. 

In this battery, participants come in for multiple sessions and do multiple experiments in a row. As such, this is a bare bones document on how to run the experiment. Procedures for consent, hearing screening, awareness surveys, general equipment set up, and payment are not included in this document. See the documents below for how these procedures are implemented in this multi-study session: 

1. Protocol for cerebellar battery: controls
2. For patients

This is a reaching experiment, with a separate interface computer. 

The lights should be OFF for this experiment so the participant can only see the cursor, not their actual hand. 

These should not have any occasion to change between studies, but it is good to check anyway. Note that you should run these checks on the REACHING computer which is on the cart (not Quiberon). 

Check sampling rate of tablet: 

1. Click on Windows start button
2. In the search at the bottom, type in Wacom tablet properties, and click on it when it appears
3. Double click on the Intuos4 XL under "Device"
4. Make sure it is in  to be in "Recognition Data" mode

Check refresh rate of monitor: 

1. Click on the Windows Start button
2. Type in settings, click when it appears
3. Go to System > Display > Advanced Display Settings
4. There should be two monitors in the dropdown to choose your display. Select Display 2: VG248
5. The refresh rate is at the bottom. It should be 144.001 Hz 

Start the experiment by typing in run_cerebReachComp_expt and hitting enter. Enter the required responses. Then place the pen on the tablet. 

General instructions (not needed if running after cerebReachAdapt)

After they are comfortable, turn off the lights, then press SPACE to start the experiment

Tell the participant: “Move your hand into the start circle and wait for the target to appear. Once the target appears, reach in a smooth motion to hit the target. Make sure that you slice through the target without stopping. You will see a cursor representing your hand position during the reach.”

“The knock just means you reached far enough, but it doesn’t mean that you hit the target.”

Throughout the experiment, you should monitor how they are performing their reaches. You may have to issue corrections. Common issues:

• When they get “Too Slow” message: “The too slow message means that you did not move fast enough for a valid trial. Remember to slice through the targets with your hand.” This is related to movement time, not reaction time 

• When they get "Too Fast" message: Try to make a smooth sweeping movement through the target. 

• If participant gets “slice through the target" message: “Remember to move accurately through the target in a quick, straight line.”

• If they are picking up paddle: Please don’t pick up the paddle and just slide it along the table.

Instructions will appear on the screen for the participant. In this phase, they will continue reaching in a smooth motion to hit the target. They will not see the cursor representing their hand position and the target may move. 

Participants may anticipate the jump by starting slow and get messages about their movement speed. Encourage them to keep moving in one smooth sweep. 

There is no restart script. This is a relatively short experiment, and can be restarted if necessary. 

This is a straight production experiment with no auditory feedback manipulations or anything special. Participants will see words on the screen and read them out loud. They do not need headphones. The study is meant to record typical productions of word-initial vocieless stops. 

This experiment is part of the cerebellar battery being run at multiple sites. Participants will be coming for full-day visits. As such, they will likely have completed consent forms and participant histories at a different time, not after this individual experiment (at some future point there will be a document on how to wrangle a full- or multi-day participant visit at each site).

To run the experiment, type in the command run_cerebTypicalProduction_expt. When prompted, enter in the participant code and their height. 

The participant will see the instructions on the screen. 

The participants will first do a practice phase to get the first-time production of the word out of the way, and to get familiar with the words and the pacing of the experiment. You can also use this time to fine-tune the gain on the microphone.

At the end of practice, ask the participant: "The rest of the experiment will go just like that. Are you feeling okay to move onto the task, or would you like to practice again?"  Make sure that the speed is okay for them. 

If they would like to redo the practice, they can, but there is no benchmark they need to pass in order to move on. 

Note: if they are having a hard time with how fast the trials are going, you can type 'redo' when prompted, and then type 'yes' when asked if the participant would like slower trials. This will slow the trial down by 0.5 seconds, and then run through practice again with the slower pace. 

"We'll now continue with the main experiment, which will take 5-10 minutes. Do you have any questions before we start?"

If no questions, "Whenever you're ready, you may begin."

Things to keep an eye on:

• Monitor the amplitude level. You may need to adjust the microphone gain if the participant starts talking too loudly or too quietly. If the participant loses a lot of oomph in their voice, you can encourage them to take a break or drink some water. 

Note: there is no pause function in this script, only the automatic breaks (every 20 trials). 

• If running at UW: the data will be saved in C:\Users\Public\Documents\experiments\cerebTypicalProduction\acousticData\. Copy the participant's folder into: \\wcs-cifs\wc\smng\experiments\cerebTypicalProduction\acousticData 
• If NOT running at UW: the data will be saved into the folder generated by get_acoustSavePath('cerebTypicalProduction'). Copy the participant's folder into the path generated by get_acoustLoadPath('cerebTypicalProduction')

As of 9/26/2022 there is no restart script for this function. However, the entire experiment takes about 5 minutes so you can just rerun it. 

This is an unusual experiment in that it is not an altered auditory feedback study. In this study, participants will first see a word that they will use in that trial. They will then hear a series of clicks through the headphones. The clicks will start relatively slow but get faster through the trial. There will be a countdown for the first 3 clicks, so they can get used to the pace and prepare. Then the word will appear on the screen. At that point, they will repeat the word in time with the clicks. 

---

This experiment is conducted using PTB so there is not the usual duplicated experimenter display. Instructions to the experimenter are displayed in Matlab's command window. 

Special hardware requirements: 

• Open-back headphones, or headphones that do not excessively muffle normal auditory feedback.  
• A Scarlett with two input ports. Both Scarlett 2i2 and Scarlett Solo will support this experiment. On a Scarlett 2i2, both input ports are dual XRL+1/4". On a Scarlett Solo, the first input is XLR and the second is 1/4". 
• 1/4" to 1/4" (6.3 mm) male to male connector cord. This experiment will work with a single stereo cord or using one side of dual input/output cords. If you are using a dual-dual cord, be sure to connect the same side on each end (red to red or black to black). 

Before the experiment begins: 

1. Change out the headphones in the experiment room for open-back headphones. These headphones have a mesh on the back of the earpieces rather than solid plastic. 
2. Connect the fourth output port of the headphone amp to the second input port of the Focusrite using the 1/4" to 1/4" cord. (There will be one labeled "cerebPacedVot" near Burnham.) 
3. Turn the gain of the fourth output port to 50%. Turn the gain of the second input port to 50%. Note: This is NOT the volume that participants will hear the metronome at. That volume will be controlled by the second headphone amp (the one that goes to the participant). 

To test the connection between the headphone amp and the Focusrite, in the Matlab command window, type: 

test_outInputGain;

The metronome channel should run up to amplitude of between +/- 0.1 to 0.2 or so. If you get any warnings about either channel, check that the gain is set to 50% on both the headphone and the Focusrite ports. If your figure shows clipping in the line labeled channel 2, turn down the gain on the headphone side if possible. If not, turn the gain down on the Focusrite side if possible. Then run the test again. 

Setup diagram: 

Start the experiment by typing in run_cerebPacedVot_expt in the command window and hitting enter.

Hardware check

Volume check

Practice

"We'll now move onto the main experiment, which will take about 10 minutes. You will be doing the same task you just practiced for the rest of the experiment. Do you have any questions before we start?"

If no questions, "Whenever you're ready, you may begin."

Things to keep an eye on:

• Monitor the amplitude level. You may need to adjust the microphone gain if the participant starts talking too loudly or too quietly.
• Make sure the participant is not running out of breath midway through. 

This is a self-paced experiment, in that participants have to press the spacebar to start the next trial. So if participants need a little break, they can always stop at a trial. There is no additional pause function. 

"Great job! You are finished with the speaking portion of the experiment. I will be in to take off your headphones." 

1. Take in "experiment in progress" sign from hallway
2. Copy participant data from local drive to smng server (see PURPLE section below these numbered points)
3. If you completed a hearing screening, copy the results from the local drive to the smng server
   1. There are folders on the desktop called "audiometer results - local" and "audiometer results - server". Drag the participant's audiometer results file from the "local" to the "server" folder.
4. Fill out Lab Notebook, located in \\wcs-cifs\wc\smng\admin\
5. Fill out check register or the extra credit register, located in \\wcs-cifs\wc\smng\admin\
6. Erase participant's name from Experiment Running Sheet
7. Clean the participant's keyboard, mouse, desk, chair, and hearing screening headphones and clicker
8. Return the Experiment Running Sheet and the Checklist to the lab manager

The data will be saved in C:\Users\Public\Documents\experiments\cerebPacedVot\acousticData\. Copy the participant's folder into: \\wcs-cifs\wc\smng\experiments\cerebPacedVot\acousticData 

[[ Gotta figure out what to do for this experiment. RK]] 

This experiment is part of the cerebellar battery run in 2022-2023. 

• For controls, it is in the FIRST session (adaptation and compensation together). 
• For patients at UW, it is in the SECOND session (adaptation and compensation together). 
• For patients at UCSF, it is in the THIRD session (compensation only; adaptation is a separate experiment with MEG). 

In this battery, participants come in for multiple sessions and do multiple experiments in a row. As such, this is a bare bones document on how to run the experiment. Procedures for consent, hearing screening, awareness surveys, general equipment set up, and payment are not included in this document. See the documents below for how these procedures are implemented in this multi-study session: 

1. Protocol for cerebellar battery: controls
2. For patients

This experiment has the option to run just 'adapt' (adaptation experiment), just 'comp' (compensation experiment), or 'both' (adaptation followed by compensation). The adaptation experiment can also be run by itself with the option 'adapt_short', which has 80 trials instead of 200, and stops before the passage reading portion. At UW, we will use the option 'both'. At UCSF, session three will use 'comp'. 

You will need the RAINBOW PASSAGE for this experiment if you are doing the adaptation portion. (You don't need this if doing 'adapt_short'.) In the adaptation portion, participants do one run, then take a break to read the rainbow passage, and then do a second run. 

This experiment uses: 

1. Audapter
2. Focusrite Scarlett
3. Closed-back headphones
4. Microphone (head-mounted or stand) 
5. Rainbow passage (adaptation experiment only) 

Before running this experiment, you need to check the audio levels of the noise over the headphones, as well as the noise + participant speech (if at UW, see this document for more details.)

• Controls at UW: You will have to recheck the levels after running the previous experiment (pacedVOT)
• Patients at UW: this is the first experiment of session 2, so conduct the equipment checks as part of session preparation. 

Tell the participant: "In this experiment, you will be speaking and listening. When you see the word on screen, read it out loud, just like you would normally say it. You will be speaking into the microphone on the desk, and you will hear your own voice and some noise played back through these headphones. Do you have any questions?" 

• If adapt: "This experiment will have four different sections." 
• If adapt_short: "This experiment will have two different sections."
• If comp: "This experiment will have three different sections."
• If both: "This experiment will have six different sections." 

Type run_cerebAAF_expt into the command window and hit enter. You will be prompted to type in adapt, adapt_short, comp, or both. Type in the appropriate experiment for your site and hit enter. 

In all cases, the first task that will come up is an LPC order check. 

"For this first section, you will see one word at a time appear on the screen." 

Use the check_audapterLPC GUI to find an appropriate LPC for this participant. If you need to fix the vowel boundaries, use the Change OSTs button.

If you are running "adapt" or "both" or "adapt_short", the adaptation section will be next. 

Tell the participant: "This next speaking section lasts about 10 minutes. Read each word when it appears on screen." 

For adapt_short: After 80 trials, the experiment will conclude.

For both or adapt: Run first 160 trials. After trial 160, there will be a message on screen saying “Time for a break,” and the command window will say “Pausing experiment for passage reading.”

Tell the participant: "In this next section, you'll be reading a short passage. Please pick up the sheet of paper on the table in front of you titled 'The Rainbow Passage'. You'll be reading the text on this paper out loud. While you speak, you will hear your own voice and noise through the headphones. Do you have any questions before we start?

Great. When you are ready, let me know and I will start our recording system. When you hear the noise start through the headphones, you can go ahead and read the passage out loud.."

Follow the command window prompts to start the Audapter feedback and stop it once they’ve read the passage.

Tell the participant: There are a few more speaking trials with single words again.

Start the “adaptation run 2”.

If you are running "comp", this will be first. If you are running "both", this will be second. 

This experiment starts with duration training to get the participant saying the vowel at an optimal duration where feedback can be used, but is not too unnaturally slow. 

Tell the participant: 

Next, we will do some practice speaking trials where we will try to get you to talk at a particular speed. Read the words aloud as they appear, just as you did previously. Try to speak in a way that is a bit more stretched out than how you would normally talk, but still somewhat natural. For example, instead of saying “head” I might say “heeeead.” After you say each word, you will get some feedback about the speed of your speech. The computer may tell you to speak slower or faster. If you spoke at a good speed, you will see a green circle.

If the participant had trouble, give them some tips. This tasks is challenging for many people. Just remember that the most important part is that their vowel is long enough that they can hear their own vowel formants and compensate for them.

You should try to have them get 7 out of 10 or better. If they’ve got the gist but the automated system isn’t cooperating, you can tell them, “you’re doing great – just keep doing that and ignore what the computer says.”

If they got less than 7/10, choose redo. Once they got 7/10 or better, tell the participant: You’ll now be doing the same task with more trials. You will still get feedback about the speed of your speech. This section lasts about 10 minutes.

Choose move on.

As of 10/21/2022 RK is unaware of a restart script for this experiment. 

This experiment is part of the cerebellar battery run in 2022-2023. 

• Patients at UW: Both f0 and f1 are in session 2
• Controls at UW: Both f0 and f1 are in session 1
• Patients at UCSF: Both f0 and f1 are in session 2

In this battery, participants come in for multiple sessions and do multiple experiments in a row. As such, this is a bare bones document on how to run the experiment. Procedures for consent, hearing screening, awareness surveys, general equipment set up, and payment are not included in this document. See the documents below for how these procedures are implemented in this multi-study session: 

1. Protocol for cerebellar battery: controls
2. For patients

This is a perceptual experiment that first records tokens from the participant, and then uses those tokens as the basis of the perceptual stimuli. 

This code can run in either f0 mode (pitch perception) or f1 mode (formant perception). You will have to specify which one at the beginning of the experiment. 

Participant will need: 

1. Microphone (for recording initial tokens)
2. Headphones --- do not put the headphones on until after the participant is done recording tokens. 
3. Keyboard (for responses) 

Tell the participant: "In this experiment there will be two sections. In the first section, you will say {ba / bed} a few times and we will record your speech. In the second section, you will hear three different tokens and say which are most similar to each other. There will be a short pause between sections while I get things set up. Do you have any questions?" 

Type run_cerebJND_expt in the Matlab command window and press enter. 

You will be prompted to enter in either f0 or f1.

• If you are doing PITCH perception, type f0.
  • You will be prompted to enter which pitch shifting algorithm you want. [[ANNEKE: WHICH ALGORITHM TO USE IN WHAT CIRCUMSTANCES?]]
• If you are doing FORMANT perception, type f1. 

1. The participant will be prompted to say “ba” (f0) or "bed” (f1) for five trials. They can just talk normally. 
   
   
2. After they are done recording the tokens, you will get the option to either re-record (if you think that none of the trials were a good representative of the participant's "clean" speech), or choose the trial that you want to base the continuum on. 
   
   
3. If you “move on,” then the script will automatically trim each trial to the speech portion and play each through your computer’s default speakers. (If you want to listen with headphones, I recommend setting your Windows default sound output device to the desktop computer, and then plugging in headphones.)
   
   
4. If one of the trials seems like a good candidate for creating the continuum, enter that trial's number (1-5) in the command window and hit enter. 
   1. If you want to hear them all again, press 9
   2. If they all actually sound bad, press any number between 1 and 5, then type "yes", then type "redo" when given the option
      
      
5. Once you pick a trial that sounds okay, you will see a waveform showing you how the automatic trimming was done. You cannot change the trimming, but it might inform your decision of whether that’s a good trial or not. If it looks good, say Yes. The trimming should include the entire vowel. 
   
   
6. Now, you’ll be given a final choice about if you want to keep that as your final continuum basis, or if you want to record new speech tokens. (redo/move on)
7. Once you move on, the computer will begin generating tokens with slightly different f0 or f1. Tell the participant: "Okay, you can relax for a few minutes while we generate the sounds that will be used in the next section. This may take a couple of minutes." 

After the stimuli have been generated, you will move onto the actual perceptual section of the participant. Tell the participant: 

"In this section, you will hear three different tokens. Your task is to say if the second token is most like the FIRST token, or the LAST token. If the second token is most like the FIRST token, press F. If the second token is most like the THIRD token, press J. Do you have any questions?" 

Answer questions, then tell the participant: "First we will start with a practice round just so you can get used to the task." 

The practice phase has very large stimulus differences and will take about 1 minute (10 trials). 

If they are okay to move on, tell the participant: "We will now move onto the main section. The task may get very difficult and you might not be sure what is the right answer. That is okay, just take your best guess. This will take about 10 minutes." 

Start the main task. It maxes out at 100 trials or 32 reversals, whichever comes first.

As of 10/21/2022 there is no remedy for a crashed experiment. 

This experiment is part of the cerebellar battery run in 2022-2023. For controls and patients, it is in the SECOND session. 

In this battery, participants come in for multiple sessions and do multiple experiments in a row. As such, this is a bare bones document on how to run the experiment. Procedures for consent, hearing screening, awareness surveys, general equipment set up, and payment are not included in this document. See the documents below for how these procedures are implemented in this multi-study session: 

1. Protocol for cerebellar battery: controls
2. For patients

• closed back headphones
• microphone
• Audapter
• FocusRite

This study examines how speakers adapt their pitch in the upward opposite direction in response to downward pitch shifting of their own voice during production of the word "bod" and the vowel "ah".

The study consists of 4 sessions that are in a fixed order:

1. pitch shifting producing the word "bod", 2. control session producing the word "bod" (unperturbed feedback), 3. pitch shifting producing the vowel "ah", 4. control session producing the vowel "ah".

RESTART MATLAB

"In this experiment, there will be 4 sections. Brief breaks between all these sections are included while the experimenter initiates the next part. During each of the sections, you will be reading words off the computer screen and listening to your speech over the headphones."

Don’t hesitate to ask questions or raise concerns at any point."

Enter run_pitchAdaptTwoWords_expt in the command line and press "enter". 

Enter the ID of the participant and their height.

Before the start of the first session, there is a calibration phase where the f0 of the speaker is extracted and during which the correct pitch shift paradigm is selected (the pitch shift paradigm is only selected once and is not selected if this participant has already done session 1 or pitchComp ). f0 is calculated before each session.

"In this section, you will see a word appear on the screen. Read it out loud once, just like you would normally say it, only slightly longer. Try to keep the pitch of your voice constant. After you speak, there will be a short break while I calibrate our equipment. 

Do you have any questions?"

Calibration instructions

 

Check if the speaker is wearing the headphones. If not wearing:

"Please put the headphones on now." [make sure they are on correctly]

First two sessions, producing "bod":

"When you see the word "bod" appear on the screen, read it out loud, just like you would normally say it. Keep the pitch of your voice as constant as possible, so it sounds monotone."

Experimenter can show this by saying "bod" with no pitch fluctuations/monotone.

You will be speaking into the microphone, and you will hear your own voice played back to you through the headphones. There will be a break every 14 trials. If you need to take a break at some other time, like to cough or take a drink of water, you can press "p" on the keyboard. You will get some trials to practice."

"Do you have any questions before we start?"

Last two sections, producing "ah":

"On each trial, you will see the vowel "ah" appear on the screen, just like before. When you see the word on the screen, start reading the word out loud. Keep the pitch of your voice as constant as possible, so it sounds monotone. Keep producing the vowel until the word disappears from the screen. You will get prompted when the vowel is too short, you start too late or when your voice is not loud enough."

Experimenter can show this by saying "ah" with no pitch fluctuations/monotone.

Things to keep an eye on:

• Monitor the amplitude level. You may need to adjust the microphone gain if the participant starts talking too loudly or too quietly. You or the participant can press "p" to pause the study and talk to the participant or take an extra break.
• Monitor the upper and lower boundaries indicated by the red horizontal lines: The boundaries can be adjusted mid-session by pressing the button (b) on the display and entering a new percentage (right arrow in the figure below).
• Monitor if speakers starts the vowel consistently too late.  You can check this by monitoring the length of the vowel, indicated by the green vertical lines in the display figure. If the right line is frequently at the utmost right side of the figure, the production starts too late and you can adjust the length of the trial by pressing the button (e) on the display (left arrow in the figure). This way, it is avoided that the speaker hears their own actual voice without the feedback.
• If the speaker has difficulty producing the correct vowel length, you can adjust the time that the stimulus is shown on the screen. Make the stimulus presentation on the screen longer if the speaker makes the vowel consistently too short, so the speaker is forced to lengthen the vowel.

As of 10/24/2022 there is no restart script for this experiment. 

This experiment is part of the cerebellar battery run in 2022-2023. For controls, it is in the FIRST session. For patients, it is in the SECOND session. 

In this battery, participants come in for multiple sessions and do multiple experiments in a row. As such, this is a bare bones document on how to run the experiment. Procedures for consent, hearing screening, awareness surveys, general equipment set up, and payment are not included in this document. See the documents below for how these procedures are implemented in this multi-study session: 

1. Protocol for cerebellar battery: controls
2. For patients

This is a experiment examining compensation to upwards and downwards pitch shifting of the speaker's own voice. Three different pitch compensation studies test the ability to compensate for pitch shifting:

1. run_pitchComp_expt.m: the pitch is suddenly shifted up or downward 1 semitone in the window 200-500 ms after onset of the vocalization
2. run_pitchCompOnset_expt.m: the pitch is already shifted 1 semitone at the onset, but the perturbation is removed during the 200-500 ms window
3. run_pitchComp400_expt.m: the pitch is suddenly shifted up or downward 1 semitone in the window 200-500 ms after onset of the vocalization, and the perturbation is removed after 400 ms

The study requires a calibration part before the session starts, during with the f0 of the speaker is calculated and the correct shifting paradigm is selected. If the participant has already run the pitch adaptation version of this experiment (pitchAdaptRetest), the experiment will take the stored information about the algorithm and not run the calibration phase again. This calibration part is included in the pitch adaptation and compensation scripts: run_pitchAdaptRetest_expt.m, run_pitchAdaptTwoWords_expt and run_pitchComp_expt.m , run_pitchCompOnset_expt.m, run_pitchComp400_expt.m

The instructions for all three versions are identical.

• closed back headphones
• microphone
• Audapter
• FocusRite

Check whether the participant is wearing the headphones. If not:

"Please put the headphones on now." [make sure they are on correctly]

"On each trial, you will say the word “ah” like you just did. Start when the text prompt appears on the screen and keep going until the text prompt disappears. Try to keep the pitch of your voice at a constant, monotone level. So, try not to raise your pitch or lower your pitch. You will be given feedback on the screen if you say “ah” for less than the required time or speak too quietly. Just continue with the task and try to adjust your speech accordingly. Before the actual session starts, we will do some practice so you can get used to the task. You will have several breaks throughout the experiment.

Do you have any questions?

Practice trials:

After the practice trials, the experimenter can make

1) the trial duration (from onset to end of trial) longer if the speaker has difficulties to start on time, (default is 2 seconds)

2) the display time a bit longer than 1 second (the duration the word is on the screen): if the speaker takes a long time to start speaking, the recorded word is often too short. In this case, add the value of the time before onset (displayed in the command line during the study as: time before onset) to the duration of the display time (1.4 second is the default). So, if the speaker always starts to produce the word after 0.6 seconds, the new display time is 1.6 seconds.

The experiment starts after you press "enter".

What to monitor for:

• During the study, monitor for correct loudness in the figures that appear for each trial. In case the signal is too loud, adjust the microphone gain.
• Monitor the boundaries indicated by the red horizontal lines: The boundaries can be adjusted mid-session by pressing the button (b) on the display and entering a new percentage (see figure below).
• Monitor if speakers make the vowel consistently too short or starts too late to fit in the trial duration time.  You can check this by monitoring the length of the vowel, indicated by the green vertical lines in the display figure. If the right line is frequently at the utmost right side of the figure, the production started too late and you can adjust the length of the trial. Press the button (e) on the display to enter a new value (see left arrow in the figure below).This way, it is avoided that the speaker hears their own voice without the feedback after the trial.
• If the speaker has difficulty producing the correct vowel length, you can adjust the time that the stimulus is shown on the screen. Make the stimulus presentation on the screen longer if the speaker makes the vowel consistently too short, so the speaker is forced to lengthen the vowel.

As of 10/24/2022 there is no restart script for this experiment. 

This experiment is part of the cerebellar battery run in 2022-2023. For controls, it is in the SECOND session. For patients, it is in the THIRD session.

In this battery, participants come in for multiple sessions and do multiple experiments in a row. As such, this is a bare bones document on how to run the experiment. Procedures for consent, hearing screening, awareness surveys, general equipment set up, and payment are not included in this document. See the documents below for how these procedures are implemented in this multi-study session: 

1. For controls
2. For patients

"This experiment has one short section and then one long section.There will be breaks between sections while I set up the next part.

For this first section, you will see one word at a time appear on the screen. When you see the word on screen, read it out loud, just like you would normally say it. You will be speaking into the microphone on the desk, and you will hear your own voice and some noise played back through these headphones. Do you have any questions?"

MATLAB command: run_cerebTimeAdapt_expt

The first phase of this experiment both gets the participant used to how the study is going to go, and also records some initial tokens so that you can set the OST file (see this article for information on how OST files work). The OST file in this experiment has three OST transitions: 

1. 0 to status 2: detects the onset of the vowel 
2. 2 to status 4: detects the onset of /s/ in "best" 
3. 4 to status 6: detects the onset of silence, here the /t/ of "best" 

The participant should say the word like it is the answer to something, "Best." or "Best!" If they are saying it like it is an item in a list ("best..."), or like a question, encourage them to change how they say it by demonstrating. You may have to correct them again during the experiment. The key is that the vowel should not be too drawn out. 

The initial pretest phase has 9 trials. After the trials are over, the GUI audapter_viewer* will open with the trials. Use audapter_viewer to tweak the OST** file if necessary (see this article on how to use audapter_viewer). These segment transitions are quite robust so you will likely not need to change much; you may need to tweak parameters, but it is highly unlikely that you will need to tweak heuristics.

*See this guide on how to use audapter_viewer
**See this guide on how to set OSTs

Important notes about OST status setting

• For this experiment, the most important OST status is 2, which is the onset of the vowel.
  • This is the event that triggers the time warping event, so it should be accurate.
  • It is better to have it slightly late than too early.
  • The default heuristic looks for RMS intensity to surpass a certain threshold, so this should be fairly reliable, since the participant is not saying anything before the target word. 
• Status 6 is the next most important.
  • It must be reliably detecting the silence in the /t/ closure. It is better to err on the side of late than early. 
  • This event is important because the interval between status 2 and status 6 is what gets fed into the PCF file so that the time warping event does not end too soon.
  • The default heuristic looks for RMS intensity to go below a certain threshold, which should also be fairly reliable. However, it cannot be all the way at the end of the trial because the time warp event has to end before the end of the trial otherwise Matlab will crash. 
• Status 4 is not directly used in the experiment, but you should try to have it relatively accurate.
  • OST statuses must occur linearly, so if the tracking never hits status 4, status 6 will also never occur.
  • The default heuristic for this looks for a rise in the RMS ratio, i.e. high intensity in higher frequencies. 

When you are satisfied with the OST tracking, click "Continue/Exit". You will get a dialog asking if you want to save; click "Save and Exit". This will ensure that the new parameters are saved both into the OST file and into the experiment file for that participant. Then a dialog will pop up to make sure it is being saved in the right place. The automatically selected option should be the local folder for that participant/experiment; if it is not, you can find another folder instead. 

• If you changed the OST at all, you will automatically redo the practice. If this is the case, tell the participant, "We're going to try that one more time." If you need to provide any additional guidance, such as speaking more naturally, you can tell them that as well. 
• If you did not change the OSTs, you will be able to move onto the next phase. 

Segmentation (information for PCF) 

After the OSTs are set, another GUI will pop up for you to segment the most recent practice trials. There will be two user events (denoted by cyan lines): one corresponding to where OST status 2 was for that trial, and one corresponding to where OST status 6 was for that trial. They will be labeled as "vStart" and "tBurst" respectively. Click and drag on the lines to adjust these events to correspond with the actual location of the start of /E/ and the start of the /t/ burst for the trial, then press 'continue' to continue to the next trial. 

If you messed up on one of the events, you can click "previous" to go back to that trial (unless it was the last trial). 

The information about the interval between vStart and tBurst will be automatically fed into the PCF file (configures perturbation). 

(For more detailed instructions on how to use audioGUI, see this article.) 

When you are done with the last trial, a figure will pop up and you will be asked if you want to accept that duration of durHold. The dots in the figure should be roughly below the line. If not, click "no" and redo the practice phase again. 

"We'll now begin the main section, which will probably take about 10 minutes. Just like in the practice phase, you'll see a word on the screen, and then say that word like you normally would. Do you have any questions before we start?"

If no questions, "Whenever you're ready, you may begin."

Things to keep an eye on:

• The experiment controller screen will show you the OST statuses for each trial. Keep an eye on these. If they start looking consistently off, you can adjust the OSTs in the middle of the experiment. To do this, press 'a'. At the top of the next iteration of the trial loop, audapter_viewer will open again and you can adjust the statuses by looking at the last trials from the experiment. Because the statuses are relatively robust for this word, you will probably not have to do this, but if the speakers are particularly variable you may have to. 
• In addition, keep an eye on the participant's loudness. You may have to adjust the gain a bit over the course of the experiment. However, if their voice strength fades dramatically, they may need to take a bit of a break instead. 

If you need to pause for any reason (other than adjusting OSTs), press the 'p' key on the keyboard. The experiment will pause at the top of the next trial loop. 

1. Move the experiment data from the local computer to the server
   1. If running at UW: the data will be saved in C:\Users\Public\Documents\experiments\cerebTimeAdapt\acousticData\. Copy the participant's folder into: \\wcs-cifs\wc\smng\experiments\cerebTimeAdapt\acousticData
   2. If NOT running at UW: the data will be saved into the folder generated by get_acoustSavePath('cerebTimeAdapt'). Copy the participant's folder into the path generated by get_acoustLoadPath('cerebTimeAdapt')
2. (At UW) Fill out the Lab Notebook on the server, located at \\wcs-cifs\wc\smng\admin\ 

As of 10/14/2022 there is no restart script for this experiment. 

This experiment is part of the cerebellar battery run in 2022-2023. 

• Patients (UW and UCSF): Session 3
• Controls (UW): Session 2

In this battery, participants come in for multiple sessions and do multiple experiments in a row. As such, this is a bare bones document on how to run the experiment. Procedures for consent, hearing screening, awareness surveys, general equipment set up, and payment are not included in this document. See the documents below for how these procedures are implemented in this multi-study session: 

1. Protocol for cerebellar battery: controls
2. For patients

This experiment uses formant clamping to simulate acceleration, deceleration, undershoot, and overshoot of the vowel /ai/. 

This is very reliant on accurate OST tracking from Audapter. For this, we individualize OST parameters for each participant using an in-house GUI called audapter_viewer. Here is a video guide for how to use audapter_viewer. If you would like more information about the particular heuristics that are used for OST tracking, see this guide. 

Note: You MUST use UW's version of Audapter (and accompanying Matlab code) for this!! Other versions do not have formant clamping. The experiment code does a hard check for the formant clamping before starting so you will find out quickly if your Audapter is not set up right. 

Before running the participant, determine if they are a speaker with monophthongization of the target vowel or not. Speakers with monophthongization cannot participate in this experiment because it renders the manipulations null!

1. Monophthongization of /ai/ is a typical feature of Southern American English and Black English, though not all speakers of these dialects will necessarily have it (depending on their other linguistic experiences)

2. Monophthongization means the vowel in “buy” or “guide” will sound more like “bah” or “gahd” 

3. If you cannot hear this specifically without looking at a spectrogram, you will get the opportunity to do that during the LPC order check.

Tell the participant: “This experiment has three shorter sections and then one long section. There will be breaks between sections while I set up the next part.” 

1. Type run_taimComp_expt into the command window and hit enter. 
2. You will be asked for participant number. It is important to use the right kind of prefix so that the trials are the right duration (for patients, they are longer/slower with more time between trials) 
   

   1. UW:

      1. if control, spXXX

      2. If patient, caXXX

   2. UCSF, UC-Berkeley: 

      1. Currently, the code looks for the substring ‘ca’ to identify patients. This can be changed to look for an additional condition if you have some other identifier in your own system

3. You will then be asked about the participant’s height. This is how we determine the starting value for LPC order.

1. In this phase, participants will see words on the screen and say them out loud. 

2. Tell the participant: “For this first section, you will see one word at a time appear on the screen. When you see the word on the screen, read it out loud, just like you would normally say it. You will be speaking into the microphone on the desk, and you will hear your own voice and some noise played back through the headphones. Do you have any questions?"
   
   "Please put on your headphones now."

3. The participant will complete 30 trials, 10 trials per word (bod, bead, bide). 

   1. If you have not yet determined if the speaker has monophthongization, look at the formant trajectories in “bide” as they show up on the control screen. 

   2. Examine the Audapter-tracked formants as they are coming up on the control screen. Note if the tracking seems to indicate that the LPC order should be changed. Indications that something might be off: 
      1. F2 transition from a to i in /ai/ might be extremely jumpy or jittery, in a way that does not follow the underlying spectrogram (some speakers may be smoother or more stable than others, so be sure to look at how the colored formant track corresponds with the spectrogram, not just the characteristics of the colored line alone). 
      2. F2 for /a/, especially near the /b/ transition, is questionable
      3. F2 for /i/ might jump down and back up 

4. The check_audapterLPC GUI will then come up. Use the GUI to find an appropriate LPC order for the participant (if you want more general information, see this primer on LPC order, with explanations and examples). Some general guidelines for this experiment: 

   1. If you are still unsure about monophthongization, you can use this time to take a good look at those formant trajectories. Monophthongization should look very obvious: formants will not move at all across the entire vowel (see example below, this is someone from Duck Dynasty saying "sideline" [saidlain] with F1 and F2 highlighted)
      
      
      
      
   2. You do NOT need to include/exclude trials. This button is used to pick out vowels that should be used to calculate a mean F1/F2 value for a particular vowel. We do not use that information in this study. 
      
      
   3. Look at several different vowels by clicking on different points in the vowel map to be sure that you are getting an overall impression of how formant tracking is going, not just looking at a single trial. Since people have some natural variability in their productions from trial to trial, you need to make sure that their general formant range is tracking well. 
      
      
   4. The most important vowel to check for accuracy is the /ai/ in "bide", because this is the vowel that is actually used in the experiment. It is also the one with the most movement over the course of the formants, which can interact with LPC order to produce a formant track that jumps away from the actual resonances. 

   5. If the formant trajectory seems to be pushed lower than where the actual formant is (e.g., the formant  track is overall too low, or there are small patches or spikes where the formant is being pushed down), this is an indication that the LPC order is probably too high (the formant tracking algorithm is assuming that the person has a longer vocal tract than they do, and thus that formants should be lower/closer together). LOWER the LPC order (e.g., from 15 to 13).  

   6. If the formant trajectory seems to be pushed higher than where the actual formant is, this is an indication that the LPC order is too low (the formant tracking algorithm is assuming that the person has a shorter vocal tract than they do, and thus that formants should be higher/further apart). RAISE the LPC order (e.g., from 15 to 17). 
      
      
   7. If you've done another experiment with this participant that checked LPC order, the value you use there may be suggestive as to what you should do in this experiment. However, it may not necessarily be exactly the same, since different vowels are being used, and thus different formant values. 
      
      
   8. This is the first chance you have in this experiment to get to know the participant's vocal tract, which will come into play in the upcoming OST setting. People with a shorter vocal tract (LPC order = 15 or lower) will likely have higher RMS ratio values overall. People with a longer vocal tract (LPC order = 17 or higher) will likely have lower RMS ratio values overall. This is because vocal tract length affects how much energy there is in higher frequencies, and the amount of energy in higher frequencies affects Audapter's calculation of RMS ratio. 

1. Tell the participant: “For this section, you will see a phrase and read it out loud. Try to read it in a clear voice, putting emphasis on the capitalized word, like this: BUY donuts now. Can you say those phrases for me?”

   1. You should coach them until they say the phrase in the right way: [sound examples of good productions: buy donuts example; guide tutors example] 

      1. It is important to use focus (emphasis) on the capitalized word so that it is long enough without being a very unnatural speech rate. 

      2. Many people can produce prosody more accurately to the target when you give them conversational examples where the target prosody would be used. For example, "pretend that you are an elementary school teacher and you are trying to calmly correct a young student. For example, they might ask you, should we make donuts now?? And you would say, no, BUY donuts now." 

      3. They should NOT put pauses between words, because they will be confounding the experimental conditions (and making it difficult to automatically track the segments). It should be a smooth, slow-ish speech rate. People are more likely to put pauses in "guide voters" (likely due to the /dv/ sequence) than in "buy donuts" but there is a tendency for both to happen if they are really trying to emphasize BUY or GUIDE. 

      4. Although duration will not be tracked in this phase, you should try to get them to say it at a speech rate similar to what will be used in the full experiment. That way, the landmarks for the vowels will be consistent (people may have different proportions of [a] to [i] at different speech rates), and the OST setting will be valid for the rest of the experiment. 

2. When they have gotten comfortable with saying the phrases, press the space bar to advance to the screen that gives them the general instructions. Tell them: “Okay, you can start whenever you are ready.” 

3. They will read each phrase 9 times in random order

4. When they finish, tell them: “I am just going to make some measurements, so you can relax for a few minutes.” 

5. After they have finished, audapter_viewer will open. Use audapter_viewer to set the OST parameters for the participant. (See section below for taimComp-specific guidance on OSTs)

6. When you are satisfied with the parameters:

   1. Click "Recalculate ALL trials" using the set of parameters that you are satisfied with. This makes sure that there is no conflicting information about what the OST parameters will be going forward. 

   2. Click “Continue and Exit”.

   3. Click “Save and Exit”. 

   4. Verify the folder you would like to save into 

7. If you had to change anything from the default, it is HIGHLY RECOMMENDED to run the OST setting phase again to make sure that they work with new data (and thus that they can generalize to the participant’s speech)

8. If you have to repeat, tell the participant: “We’re just going to do that one more time so I can make sure everything is set up correctly.” 

taimComp-specific guidance for OST setting

Segmentation

1. Tell the participant: 

   1. “In this section, you will practice saying the phrases at a good speed. When you say each phrase, you will get some feedback about how fast you were talking. If you see a BLUE circle, it’ll tell you to speak a little faster. If you see a YELLOW circle, it will tell you to speak a little slower. If you see a GREEN circle, that means you were speaking at a good speed.” 

   2. Pause to confirm 

   3. “So if you are told to speak a little slower or a little faster, you don’t have to really change how you are speaking drastically. Keep speaking smoothly and clearly, and just adjust a little. So like if you said [speak quickly] “BUY donuts now” and have to slow down, you can just say [speak more slowly] “BUY donuts now”, you don’t have to put any extra pauses in or anything.”

   4. Pause to confirm 

2. They will do 10 trials (5 of each phrase). 

   1. Keep general track of how they do (usually too fast, usually too slow, usually good, etc.) 

   2. Keep an eye on the OSTs. The duration feedback is based on the OST values, so if they are not tracking correctly, the feedback will be off. 

3. You will be given the option to repeat. 

   1. If you need to adjust the OSTs, you can do that, and then run again 

   2. Give general guidance on how fast to speak to the participant if necessary (referring to if they were generally fast/slow) 

1. Tell the participant: “This is the last section. It will be just like the section you just did, but will last longer, about 20 minutes. There will be breaks every 20 trials. If you need to pause at another time, like to cough or to drink water, you can press p on the keyboard. Do you have any questions?” 

2. During the experiment: 

   1. Keep an eye on their OST tracking. You can adjust mid-experiment if necessary by pressing ‘a’. Common triggers of adjustment:  
      1. Changes in loudness: Many people will talk more quietly as the experiment wears on, with accompanying changes in RMS and RMS ratio. You can sometimes address RMS changes by adjusting the gain, but if the ratio gets really out of whack, you may have to adjust the ratio threshold. 
         
         
      2. Changes in proximity to microphone: Some speakers may sit back in the chair after a while, which mostly affects RMS. This again can be helped by changing the gain or by asking them to sit forward again, but if that isn't possible you may need to adjust. 
         
         
   2. There are a few other settings that you can adjust mid-experiment by pressing 'e' 
      1. trial duration: If participants (particularly patients) are having a hard time completing the utterances before the end of the trial, you can increase the trial duration. 
         
         
      2. target vowel duration boundaries: if participants (particularly patients) are having a hard time getting the right duration feedback (not due to OST issues), you can loosen the boundaries for what is considered to be a good duration. Ideally you should only increase the maximum; participants must go slow enough for them to be able to react to the perturbation
         
         
      3. LPC Order: if you notice that the formants are not tracking the way they should be, the LPC order may be off. Formants that are not being tracked well will be overly jittery, and may have sudden dips or spikes. Specifically, these dips and spikes do not follow the underlying formant structure---some people (particularly patients) may have less smooth formants. An example of a trial with LPC order too high (that is, assuming a too-long vocal tract) is below, with the suspect areas underlined in red. Very bad LPC orders may even have whole patches where the shape of the formant is preserved, but is out of line with the rest of the formant (similar to octave doubling/halving in pitch tracking). 
         1. Sudden downward dips below where the actual formant is (such as in the example below) indicate that the formant tracking algorithm is preferring candidates in frequencies that are lower than the actual formant---in this case it is also interacting with the rapid change in formants, basically penalizing candidate formant values for being much higher than the previous values. In this case, you should LOWER the LPC order (e.g., from 15 to 13). This will ultimately give a little more preference to higher formant candidates.  
         2. Sudden upward spikes above where the actual formant is indicate that the formant tracking algorithm is preferring candidates in frequencies that are higher than the actual formant. In this case, you should RAISE the LPC order (e.g., from 15 to 17). This will ultimately give a little more preference to lower formant candidates. 
            
            
      4. RMS ratio threshold: this is the parameter that limits when formants can be tracked relative to how much energy there is in the high frequencies. This is most useful for avoiding tracking formants during sibilants. The default value is 1.7, which should be pretty permissive. Higher values are more restrictive (i.e., if you increase it enough, even vowels won't track anymore), lower values will allow tracking through higher-ratio segments (like /s/). 
         1. Problems with the RMS ratio threshold will result in full dropouts in BOTH formants at the same time. That is, both formants will drop to 0 at the same time. This is because Audapter simply isn't tracking the formants there and essentially providing no value for any formant. 
         2. NOTE 1: It is not uncommon for people with shorter vocal tracts (i.e., higher formants) to need the threshold to be adjusted downward. If you see dropouts, that is an indication that the RMS ratio threshold should be adjusted DOWN. An example of such dropouts is below (threshold set to 3.7; should be lower than 3.2 for this speaker). There are multiple dropouts in the formant tracks that are in the red circle---note the gap between the first and second halves of each formant's contour. 
         3. NOTE 1: 2.5 is 1/0.4. Audapter's coding uses 0.4 as the actual ratio value, but has it inverted for the threshold. 
            
            
            

To restart taimComp in the event of a crash: 

1. Type in run_taimComp_expt and hit enter
2. Type in simple/hard (depending on what version you have been doing) 
3. Type in the participant code
4. You will then be asked if you want to load in their expt file (which should exist already from the first attempt at running). Type y
5. You will be asked if you want to OVERWRITE their expt file. Click CANCEL
6. The script will then look for which modules have already been done. If a data file already exists in each module (LPC order, OST testing, duration training), it will let you know and ask if you want to redo that phase anyway. If there is NOT a data file in one of those modules, that means that you didn't complete that module and will automatically redo it
   1. Note: if you didn't get to segmentation in OST pretest, you should redo it anyway 
7. If you were in the middle of the main experiment, it will start you back where you were 
   1. Note: if you didn't get to the first trial of the perturbation phase, it will start over from trial 1. 

This is a perceptual experiment, using prefabricated tokens. 

• For people running this study at UW: the tokens are located on the server. 
• For people running this study at UCSF: the tokens were shared via Google drive. They should be copied into the folder that is returned when you run fullfile(get_exptLoadPath, 'cerebDurJND', 'stimuli')

Matlab command: run_cerebDurJND_expt

"In this experiment, you will be listening to three words, which will differ mainly in the duration of the vowel. You will then press a button on the keyboard to indicate if the second word sounded more similar to the first sound or the third sound. If you are not sure, just make your best guess."

At this point you can answer any questions they might have (there are also task reminders in each trial). 

"You will start first with a practice phase, where we can make sure that the volume is okay and to get you used to the task. In order to move onto the full task, you will need to get at least 5 of the 6 practice trials correct." 

This experiment starts with a practice phase so that participants can get used to how the task is run. The practice phase uses stimuli with very large intervals, so participants should be able to hear the difference. During practice, the participant will get feedback on if their answers were right or not. They will automatically move onto the full phase of the experiment once they get at least 5/6 practice trials correct. 

After the practice, check with the participant to make sure the volume is okay. 

Note: this experiment assumes that 100 ms is larger than the biggest JND among cerebellar patients, based on data from a different study (for these particular stimuli, it is 100 ms vs. 200 ms, so it is a very large proportional difference). However, if you get a participant that cannot complete the practice because they cannot hear the differences, please contact Robin right away so additional stimuli can be made, and adjustments to the code installed. There will not be an infinite loop---if the participant fails practice more than 5 times, you will be able to manually override. 

Once they have passed the practice, they will go automatically to the main phase of the experiment. They will complete either 100 trials or until they get to 30 reversals, whichever is first. This will last about 10 minutes. 

• If running at UW: the data will be saved in C:\Users\Public\Documents\experiments\cerebDurJND\acousticData\. Copy the participant's folder into: \\wcs-cifs\wc\smng\experiments\cerebDurJND\acousticData 
• If NOT running at UW: the data will be saved into the folder generated by get_acoustSavePath('cerebDurJND'). Copy the participant's folder into the path generated by get_acoustLoadPath('cerebDurJND')

As of 9/23/2022 there is no restart script to start the experiment over in the middle of the experiment.