Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Supported by

Help with Hayling Test

Hello there!
I've come by this program recently, looking for a way to implement a Hayling Test, but I'm now kind of stuck and in need of some assistance (I thought I could pull it off after watching the tutorial, but boy was I wrong!). If someone could provide me with some guidelines about how to structure my experiment (or point me to a similar one already made), I would be very grateful.
The subjects in this test basically have to listen to a series of incomplete sentences, saying outloud the word that's missing after each one of them. I would like to be able to measure the elapsed time between the end of the sentence and the response of the subject, and if possible, also to record said response (in order to manually classify it after)
I believe the script in this link is able to do that, but I don't even know where/how should I add it.
Thanks very much in advance!


  • Hi Ema,

    Why don't you first try to implement the experiment up to the point that you manage? For example, you could try to build an experiment in which participants respond to the incomplete sentences by pressing the space bar, rather than through a verbal response. Then, once you have that, we can see how to integrate a verbal response. Does that work for you? :smile:


    There's much bigger issues in the world, I know. But I first have to take care of the world I know.

  • edited May 18

    Hello Sebastiaan,

    I'm sorry for the delay in my reply. With some time, I have managed to build the experiment almost the way I was expecting it to be. The core of it are 4 trial sequences (2 practice and 2 experimental) of this structure:

    1) Sketchpad with a red circle, 0 ms duration
    2) Sampler plays the sound file
    3) Sketchpad with a green circle (to signalize now it's the time to speak), 0 ms duration
    4) The inline script with the voicekey code you wrote in the post I linked above
    5) A sketchpad which says press "S" for next audio, "R" to repeat, 0 ms duration
    6) A keyboard response with "S" as correct, "R" as incorrect
    7) An inline script which runs again the whole trial sequence if [correct] == 0
    8) A logger (4 linked copies)

    The experiment flows the way it should, and it detects the audio input for each trial. But I encounter a very big problem: when I see the data logged, there is no variable Response_time! The closest thing is Average_response_time. I should note that if I put a feedback item after the voicekey script that includes [response_time], it shows the response time, so I asume that the problem happens whith the logging (I should also add that "log all variables" is enabled).
    Do you know what could be causing it?

  • Hi Ema,

    Can you share a log file with us? Maybe also the experiment. Normally, the response time variable is stored as response_time, but maybe it got overwritten or something.


Sign In or Register to comment.