Millisecond Forums » Millisecond Forums » Inquisit 3 » Stop Signal task,about data collection and interpretation

Stop Signal task,about data collection and interpretation

Iris520 — Thu, 23 May 2013 08:57:27 GMT

Hello,everyone.I am a student.I have some problems in data collection and interpretation at Stop Signal task.I don't know why" values.ssd/expressions.p-rs/expressions.ssd、ssrt、sr-rt "show like the following.Is that normal? ssd ranges from 50 to 1150,but,there is always 50...

I am weak at English,hoping you can understand my description.many thanks for your reply.

Iris

RE: Stop Signal task,about data collection and interpretation

Dave — Thu, 23 May 2013 08:57:27 GMT

[quote] sorry,I didn't notice the forum section[/quote]

No need to apologize. It's just that posting in the correct sub-forum makes it easier for both you and me to determine what an issue may be or how to solve a given problem. Certain things apply to Inquisit 4 but not Inquisit 3 and vice versa.

RE: Stop Signal task,about data collection and interpretation

Iris520 — Thu, 23 May 2013 08:52:45 GMT

Oh^-^ sorry,I didn't notice the forum section.Many thanks,Dave.

RE: Stop Signal task,about data collection and interpretation

Dave — Thu, 23 May 2013 08:43:07 GMT

The latest Inquisit 4 version is 4.0.2.0. 4.0.0.0 is an ancient beta version with many bugs.

Please post any future requests in the correct forum section.

RE: Stop Signal task,about data collection and interpretation

Iris520 — Thu, 23 May 2013 08:40:32 GMT

all machines use the same inquist version 4.0.0.0. I downloaded the script from the Task Library,and don't change anything.keyboard scancodes is consistent

But why one of machines can run correctly,but others can't. so,where is the difference among computers may be?

OMG!I'm going to crazy!

RE: Stop Signal task,about data collection and interpretation

Dave — Thu, 23 May 2013 08:16:37 GMT

(1) Make sure you are using the same Inquisit version on all machines. Since you've posted in the Inquisit 3 forum, that would be version 3.0.6.0.

(2) Check your script thoroughly for errors, especially if you made any changes to it. Compare it to the original, unmodified version available from the Task Library.

(3) As noted previously, check the keyboard scancodes on the machine and in the script.

RE: Stop Signal task,about data collection and interpretation

Iris520 — Thu, 23 May 2013 08:10:46 GMT

Hi,Dave,sorry to bother you again.My problem still needs to be solved.Stop signal task can't run correctly.It seems stop trial can't work——subject can't suppress all of responses;the value.ssd is always 50.

My computer is Window XP system.one of my friend's window 7 can run correctly,but the other one(window 7)can't work on,it has the same problems as I used describe.I used the original script.Do you know what is the cause may be?

Many thanks in advance

Iris

RE: Stop Signal task,about data collection and interpretation

Iris520 — Wed, 22 May 2013 06:25:08 GMT

thanks,because I already translated this script into Chinese,so there have many problem! I will check it carefully. thank you again

RE: Stop Signal task,about data collection and interpretation

Dave — Wed, 22 May 2013 06:03:35 GMT

What are the keyboard scancodes for D & K on your machine (see Tools -> Keyboard Scancodes...) and which scancodes are configured in values.leftkey & values.rightkey in the script's <values> element?

Also note that this does not fit the data set you posted, which clearly shows responses were submitted. If the keys you used were useless, that would not be the case.

RE: Stop Signal task,about data collection and interpretation

Iris520 — Wed, 22 May 2013 05:58:32 GMT

OMG ! the problem is the responses. Press the 'D' key with the left index finger when the arrow is pointing to the left

and press the 'K' key with the right index finger when the arrow is pointing to the right.

but in my computer,the key is useless! so strange!Dave,thank you for all your assistance

RE: Stop Signal task,about data collection and interpretation

Dave — Wed, 22 May 2013 05:24:22 GMT

In the data set you posted there is *no successful inhibition*.

RE: Stop Signal task,about data collection and interpretation

Iris520 — Wed, 22 May 2013 05:22:41 GMT

I know...When inhibition is successful, SSD increases by 50 msec; when inhibition is unsuccessful, SSD decreases by 50 msec.

but whatever the inhibition is successful or not,the SSD is still stay the minSSD 50msec.I don't know why [:'(]

RE: Stop Signal task,about data collection and interpretation

Dave — Wed, 22 May 2013 04:54:47 GMT

[quote] so, I needs to change "probability to respond when a stop-signal is present [expressions.p_rs]"?[/quote]

No! You cannot and should not change it. This is an empirical datum. It means the person who produced the data set responded on 100% of stop-signal trials. If a person *never* suppresses a response despite the presence of a stop-signal, there is *no* basis to change the stop-signal-delay.

Your question(s) suggest that you have not yet fully grasped the reasoning behind stop-signal paradigms. I thus urge you to re-read the literature carefully.

RE: Stop Signal task,about data collection and interpretation

Iris520 — Wed, 22 May 2013 04:50:39 GMT

so, I needs to change "probability to respond when a stop-signal is present [expressions.p_rs]"?

/ p_rs = (1-(values.ss_ncorr/values.ss_ntotal))*100

But how?

many many thanks...Dave

RE: Stop Signal task,about data collection and interpretation

Dave — Wed, 22 May 2013 04:39:48 GMT

The minimum SSD is 50 ms. Since your data show responses on *every* stop-signal trial (p_rs=100), there is no basis to adjust the SSD upwards.

For details, please refer to the literature, specifically Verbruggen et al. (2008).