We have a nice "demo mode" for the sensory integration experiment that is very
helpful when testing, and also when preparing new properties/stimulus files.
For example, we can play around with different offsets between audio and visual
information without having to shut down the program, change a properties file,
and re-open the program (and then when for the condition-of-interest to
randomly be called in the trial cue!).
The "quickest and dirtiest" way I can think of for doing this, which should
work fine for a start, is to simply read in the relevant properties file, then
go into a mode where there is a big box basically displaying nearly all of the
variables that can be manipulated in the properties file, and second window
playing the trial that would be called by this. I say "nearly all" of the
variables from the properties file since this mode would just play a single
trial, so things like "blockRepetitions" or something wouldn't have meaning.
When a new trial is triggered, the program would just update all of the
variables that are displayed in this window and then run the trial. That would
make it MUCH quick to test different sound banks for instance, as well as
different metric structures (i.e. combinations of Psss Psss Psss P___*).
I discussed this with someone earlier (either Simeon or Ben) and they suggested
putting this in the bug tracking system so that it is noted and then we'll see
if there is time for it in the end.
Original issue reported on code.google.com by schutz.m...@gmail.com on 8 Jan 2014 at 10:17
Original issue reported on code.google.com by
schutz.m...@gmail.comon 8 Jan 2014 at 10:17