search

MAPLE-Lab / auditory-research-suite

Automatically exported from code.google.com/p/auditory-research-suite
0 stars 2 forks source link

Build 204 - Slider configuration for unimodal vs. bimodal blocks #23

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Build 204 is functioning great! I just noticed one small issue to fix regarding 
the sliders:

As you know, the SI experiment has 4 possible conditions/blocks: 2 unimodal – 
i.e. includeAudioBlock (audio alone) & includeAnimationBlock (animation alone), 
and 2 bimodal – includeVideoBlock (audio-visual videos), & 
includeAudioAnimationBlock (audio-visual animations).

 A few months ago, I had noticed that in Build 173 the video condition (i.e. includeVideoBlock=true) was missing a slider. At the time it was only showing the short/long slider and was missing the low agreement/high agreement slider. This was subsequently fixed in Build 189, but also introduced some other slider issues, that my students did not catch while testing, as we were focused on the functionality of other parameters (i.e. warm-up trials).

As I was testing out the newest build (204) I noticed that all conditions 
featured both sliders, when in fact we only want both sliders to appear in the 
bimodal conditions.

In summary, we would like the following slider configurations:

includeAudioBlock – short/long slider only
includeAnimationBlock – short/long slider only
includeVideoBlock – Both short/long and high agreement/low agreement sliders
includeAudioAnimationBlock – Both short/long and high agreement /low 
agreement sliders

I have included this description as a PDF in case you find it useful to have 
the formatted version with different fonts for technical terms, etc.

Thanks so much for all your hard work!

Original issue reported on code.google.com by jess.gil...@gmail.com on 17 Apr 2014 at 3:08

Attachments:

GoogleCodeExporter commented 9 years ago

Original comment by zach.br...@datamininglab.com on 18 Apr 2014 at 6:36

GoogleCodeExporter commented 9 years ago 
Fixed in r222. Error had originally been introduced in r189.

Original comment by zach.br...@datamininglab.com on 22 Apr 2014 at 1:30