Alright, so I now have my audio library. Next on the agenda is a test program that tests reactions of users to vibroacoustic input. The test needs to present randomized stimuli to users, so that they can be tested for:

• Time to respond with a direction
• Accuracy of direction
• Efficacy of stimuli

Since this is probably going to be within subjects (multiple stimuli) and also between subjects (same tests on multiple users) we’re going to want to be able to present the same sequence, so we’ll need to seed the random number generator so we get the same sequence.

• Start with the default random number generator, but maybe run through a wrapper class in case we need something like a Mersenne Twister.
• Xml file to specify the input and output of the experiment. This library looks reasonable.
  • Input
    • Sounds to use (random distribution of sound use)
    • Test type (Accuracy, Speed, or both)
    • Attempts per test
    • Number of tests (must be even)
    • Random seed
    • min/max delay between test segments
    • output filename
  • Output
    • Test UID
    • Date
    • Time
    • Subject
    • Researcher
    • Free form note field (1024 characters?)
    • Accuracy or Reaction time test
    • Audio configuration
    • Random seed
    • Calibration results
      • Time(s) to click in response to visual cue
      • Time(s) to click in response to audio cue
    • For each played sound
      • Sequence x of total
      • Audio file(s) used (WAV)
      • Audio source position (x, y) in screen coordinates from the origin, where the user’s head is
      • Audio playback matrix (actual speaker relative volume)
      • Time to click after play start
      • Duration of sound
      • Click position (x, y) in screen coordinates from the origin, where the sound is perceived to have come from
• App
  • Text
    • File navigator for xml file
  • Calibrate
    • Runs a sequence of tests where the user has to click the mouse as quickly as possible in response to the canvas flashing white, and then all(?) speakers in the headpiece playing the calibration sound
    • Calibration cues are have a randomly determined timing between X and Y seconds
    • Test is disabled until calibration is run. Loading a new xml document effectively resets the system, requiring a new calibration sequence
  • Test
    • Shows a label that says either “Accuracy” or “Speed” based on which test is being run. We could change the background of the display as well?
    • The graphics screen shows a circular cursor that resets to the center of the graphics screen at the beginning of each section. Once the audio cue plays, the user can move the mouse away from the center towards the direction of the sound. The circle is clamped in its motion so that the result is always a valid angle, as long as the user moves the cursor far enough away from the center (TBD). Clicking the mouse causes the clock to stop and the cursor to reset.
    • If this is not the last test segment, then a random time period between X and Y seconds elapses before the next test is run.
    • Once the test completes, the system checks to see if that is the last one. If not, a stochastic choice is made to determine if the next test should be speed or accuracy. By the time all tests have run, the number of speed and accuracy runs will be equal.
  • Output file is appended throughout the test (open, write, close? Or read in the DOM, update and write out?)

Started the FLTK wrapper, and probably saved a good deal of time by going back to Erco’s FLTK page and associated videos

• For tomorrow:
  • Fl_Native_File_Chooser
  • Double Click Detection