double key for response

Resilience_studies

Hello,

I am using OpenSesame 3.2.8 on a MacBook Air OS10.15.7 and I want to collect keyboard responses in my study. Everything works fine, but the keyboard seems to be not sensitive enough. It takes a second keyboard press to get the next stimulus. If you get a habit of "double clicking" the required key, the experiment runs smoothly. However, that is also impacting the response times and most participants will need a lot of practice to acquire that habit. I tried a different keyboard and I tried all 3 backends (legacy, psycho, and xpyriment), still double keys required. How can I fix this?

Regards,

Angela

eduard

Hi Angela,

I suspect you have a sketchpad with which you present the stimulus before collecting the response, right?

What have you put in the duration field of that sketchpad? If it is keypress, then your participants will have to press a key once to move on from the sketchpad to the keyboard item, and then again another time to proceed from the keyboard item to the rest of the experiment. What you probably want is not keypress in that duration field, but 0 , like that you should get the behavior that you want.

Good luck,

Eduard

Resilience_studies

Hi Eduard,

Thanks for the reply. My stimulus is a sound file and duration is "sound". After that, I ask a question with a sketchpad and that has duration "keypress". I want them to answer with pressing a key on the keyboard and then there is the "keyboard_response" to log their answer.

I added a connected logger after the instructions sketchpad for logging reading time for the instruction. I collect EDA data in parallel and have not found out yet how to synchronize the data.

Any idea why the double keyboard response remains?

Regards,

Angela

lvanderlinden

Hi @Resilience_studies ,

I think you should:

• Put the duration of the sketchpad item to 0 instead of "keypress"
• Make the sketchpad follow immediately be a keyboard_response item

Doing so does not mean that the sketchpad is presented for 0 ms, but that the experiment advances immediately to the event of waiting for a keypress, which is exactly what you want. Can you try that?

Cheers,

Lotje