How to measure latency of too slow responses


Author
Message
Dave
Dave
Supreme Being (1M reputation)Supreme Being (1M reputation)Supreme Being (1M reputation)Supreme Being (1M reputation)Supreme Being (1M reputation)Supreme Being (1M reputation)Supreme Being (1M reputation)Supreme Being (1M reputation)Supreme Being (1M reputation)
Group: Administrators
Posts: 13K, Visits: 108K

Or you could use the <trial> element's /iscorrectresponse attribute to automatically score responses w/ latency > 500 as incorrect.


Jennifer G
Jennifer G
Associate Member (190 reputation)Associate Member (190 reputation)Associate Member (190 reputation)Associate Member (190 reputation)Associate Member (190 reputation)Associate Member (190 reputation)Associate Member (190 reputation)Associate Member (190 reputation)Associate Member (190 reputation)
Group: Forum Members
Posts: 2, Visits: 1

Hi Dave,


Thanks for the quick response! As far as I understand, then Inquisit wouldn't know that any response slower than 500ms is incorrect. I'd like Inquisit to know that the response was too slow, but still have it record the latency of the response. I could easily just manually mark all responses slower than 500ms as too slow after data collection, but I'd also like to sometimes give participants feedback about total errors.


Jennifer


Dave
Dave
Supreme Being (1M reputation)Supreme Being (1M reputation)Supreme Being (1M reputation)Supreme Being (1M reputation)Supreme Being (1M reputation)Supreme Being (1M reputation)Supreme Being (1M reputation)Supreme Being (1M reputation)Supreme Being (1M reputation)
Group: Administrators
Posts: 13K, Visits: 108K

If you want to record responses after 500 ms, you need to get rid of the response timeout.


Jennifer G
Jennifer G
Associate Member (190 reputation)Associate Member (190 reputation)Associate Member (190 reputation)Associate Member (190 reputation)Associate Member (190 reputation)Associate Member (190 reputation)Associate Member (190 reputation)Associate Member (190 reputation)Associate Member (190 reputation)
Group: Forum Members
Posts: 2, Visits: 1

Hi everyone,



I'm currently programming my own version of the Flanker task and I'm having a question about how to record the response  latency for too slow responses.


Right now I'm having the response time out after 500 ms which should then terminate the trail. Responses that are made after these 500 ms are recorded as incorrect with a response latency of 500. Here is the code for one trial that does this:



<trial congruentleft>

/ pretrialpause= rand(800, 1000)

/ stimulustimes = [0=fixationcross;500=primeleft;1000=targetcongruentleft;1500=blank]

/responsetime = 1000

/ response = timeout(500)

/validresponse = ("1", "0")

/correctresponse = ("1")

</trial>



I'm wondering if it would be possible to keep everything as is in terms of how the trial appears on the screen, but also record the latency of responses that come in after 500ms have passed.


Any advice would be greatly appreciated!


Thanks!


 Jennifer


Tags
GO

Merge Selected

Merge into selected topic...



Merge into merge target...



Merge into a specific topic ID...




Reading This Topic

Explore
Messages
Mentions
Search