Group: Administrators
Posts: 13K,
Visits: 104K
|
The slight delay is probably due to one or several of the stimuli presented by <trial base_negUP> being erased. The delay will thus be on the order of 1 to 2 display frames. You can only get rid of it by setting all the stimulus element's /erase attributes to false as in
<shape blank> ... / erase = false </shape>
etc.
If need be, have the follow up <trial> overwrite any stimuli by displaying the "blank" shape at the start.
<trial what_prompt> / validresponse = ("a", "5") / correctresponse = ("") / stimulustimes = [0 = blank, what; 300 = blank] / timeout= 700 </trial>
Also, <trial what_prompt> will only start accepting response after its final stimulus has been displayed ("blank" at 300ms). If you want the trial to start accepting responses earlier (starting with the presentation of "what"), you should specify
<trial what_prompt> / ontrialbegin = [trial.what_prompt.resetstimulusframes(); ] / validresponse = ("a", "5") / correctresponse = ("") / stimulustimes = [0 = blank, what; 300 = blank] / timeout= 700 / beginresponsetime = 0 </trial>
For information regarding Inquisit's stimulus erasing behavior, see the "How to erase stimuli" topic in the documentation. For an overview of the various components involved in timing stimuli, trials and responses, I would recommend taking a look at the "How to Control Trial Duration and Inter-Trial Intervals" topic.
|