Latency (command: responsetime)

Author	Message
LaraG	LaraG posted 11 Years Ago Topic Details Share Topic
Group: Forum Members Posts: 2, Visits: 6	Dear users, I noticed a problem with my recorded stroop data: I adapted an inquisit file, formerly used for inquisit 3, with the stroop paradigm. Checking the recorded data, I found latency means about 250ms, some are 0 ms, only a few latencies are 'normal', what means about 600 ms or higher. I don't know where the problem was, because almost the same inquisit file was used in another study, but there was used inquisit 3, not 4. May that be the mistake? That's my trial text: <trial tr_gg> / pretrialpause = 200 / stimulustimes = [0=te_fixation, te_redreminder, te_greenreminder; 500=te_greencongruent] / correctresponse = ("g") / validresponse = ("g","h") / errormessage = true(te_error, 400) / correctmessage = true(te_correct, 400) /responsetime = 700 / response = timeout(2700) </trial> Compared to the standard stroop file from the millisecond task library, I found, that the responsetime and response - commands aren't there. In the inquisit 4 help tool, there isn't the response time-command at all. Can you help me? How can I transform that small latencies to the real latencies (if possible)? Thank you very much, Lara
	Reply Like 57

Merge into selected topic...

Merge into merge target...

Merge into a specific topic ID...

LaraG - 11 Years Ago

/responsetime = 700 means that Inquisit was instructed to *start...

Dave - 11 Years Ago

Thank you very much! That means: If I added 200ms to each latency, I...

LaraG - 11 Years Ago

> That means: If I added 200ms to each latency, I would have the...

Dave - 11 Years Ago

Login
Remember Me Reset Password Resend Validation Email Login	Facebook

Millisecond Forums