Group: Administrators
Posts: 13K,
Visits: 104K
|
Thanks for the script. What happens is the following:
If you respond in an instance of a given <trial> element *prior* to the stimulus "leer" being shown at 2500ms, the *next* instance of that same trial element will behave wrongly and *not* display "leer" at 2500ms. Basically, Inquisit fails to properly reset the trial's stimulus presentation sequence if that sequence was interrupted by an early response (i.e., prior to all scheduled stimuli having been displayed).
To see this for yourself, temporarily add
<block debug> / trials = [1-10 = greenincongruentred] </block>
to the script and run just that block. Respond early in the 1st trial and observe that the 2nd trial will not display "leer" at 2500ms.
To avoid the issue, you can force a reset of the stimulus presentation sequence via
<trial greenincongruentred> / ontrialend = [trial.greenincongruentred.resetstimulusframes(); ] / pretrialpause = 1500 / stimulustimes = [0=Fixationskreuz; 500 = leer, greenincongruentred, redreminder, greenreminder, bluereminder, yellowreminder; 2500 = leer, redreminder, greenreminder, bluereminder, yellowreminder] / correctresponse = ("d") / validresponse = ("d", "f", "j", "k") / beginresponsetime = 500 </trial>
Add the above statement to <trial greenincongruentred>, run the <block debug> element again as detailed above and observe the difference.
|