Millisecond Forums

That was easy! I have now done a pre-test and it seems that everything works fine.
Thank you very much for your help!

<expt>
/ onexptbegin = [values.expcondition = 1]
/ onexptbegin = [values.rahmen1 = "ganz normal schwarz"; values.rahmen2 "gestrichelt" ]
...
</expt>

<expt>
/ onexptbegin = [values.expcondition = 2]
/ onexptbegin = [values.rahmen2 = "gestrichelt"; values.rahmen1 "ganz normal schwarz" ]
...
</expt>

is invalid syntax. "=" is missing in both cases. I.e. if you want values.rahmen2 to store the string "gestrichelt", your syntax ought to read

<expt>
/ onexptbegin = [values.expcondition = 1]
/ onexptbegin = [values.rahmen1 = "ganz normal schwarz"; values.rahmen2 = "gestrichelt" ]
...
</expt>

Similarly, the statement in the 2nd <expt> ought to read

<expt>
/ onexptbegin = [values.expcondition = 2]
/ onexptbegin = [values.rahmen2 = "gestrichelt"; values.rahmen1 = "ganz normal schwarz" ]
...
</expt>

OK!I defined the values as follows:

<values taskparams>
...
/expcondition = 0
/rahmen1 = " "
/rahmen2 = " "
</values>

Apparently, this works for expcondition, but I still receive the error message that the expression rahmen1 / rahmen2 is invalid, but only for group 2.
I have to ask you again for your help!

> 2. OK, thank you for your explanation. Does that also mean that a cue (e.g. nr. 41) and its target (41) are "fixed" to a SOA (the 41. SOA in the list)? I hope that the question is understandable.

Yes. When SOA #41 is selected from <list soa> for a given trial, then cue item #41 and target item #41 will necessarily follow in that trial.

Re. #3: Those values are nowhere defined in the script. values are global variables. You need to define them in a <values> element in the script before you can use them. Just look at how this is done with all the other values that already exists in the script and how they are then used throughout the code.

Thank you very much, this was very helpful.

I changed my script according to your propositions
1. I added 80 SOAs to reach 160 SOAs in total, that works.
2. OK, thank you for your explanation. Does that also mean that a cue (e.g. nr. 41) and its target (41) are "fixed" to a SOA (the 41. SOA in the list)? I hope that the question is understandable.
3. Thank you for this hint. I included two <expt> elements and changed the instruction. Now I get a lot error messages as: values.expcondition / values.rahmen1 / values.rahmen2 is invalid. I am not sure how to define these expressions...!? After collecting data with Inquisit, I will prepare my data in a common statistic program where I can define right / wrong trials (i.e. no need for the summary data etc.).
I attached my modified script with the adjustments at the end of the file.

Could you help me out?
Thank you!

> 1. I ran the script and but there must be an error in the syntax. All cues appear 2 times (as I intended), but all 160 cues are followed by the pictures of the go-target. What did I do wrong?

Your <list> elements are paired, i.e. they are all tied to <list soa>

<list soa>
/ items = (
    100,100,100,100,100,
    200,200,200,200,200,
    300,300,300,300,300,
    400,400,400,400,400,
    500,500,500,500,500,

    100,100,100,100,100,
    200,200,200,200,200,
    300,300,300,300,300,
    400,400,400,400,400,
    500,500,500,500,500,

    100,100,100,100,100,
    200,200,200,200,200,
    300,300,300,300,300,
    400,400,400,400,400,
    500,500,500,500,500,

    100,200,300,400,500)
</list>

<list cuetype>
/ items = (
    1,2,3,4,5,6,7,8,9,10,
11,12,13,14,15,16,17,18,19,20,
21,22,23,24,25,26,27,28,29,30,
31,32,33,34,35,36,37,38,39,40,
41,42,43,44,45,46,47,48,49,50,
51,52,53,54,55,56,57,58,59,60,
61,62,63,64,65,66,67,68,69,70
71,72,73,74,75,76,77,78,79,80,

81,82,83,84,85,86,87,88,89,90,
91,92,93,94,95,96,97,98,99,100,
101,102,103,104,105,106,107,108,109,110,
111,112,113,114,115,116,117,118,119,120,
121,122,123,124,125,126,127,128,129,130,
131,132,133,134,135,136,137,138,139,140,
141,142,143,144,145,146,147,148,149,150,
151,152,153,154,155,156,157,158,159,160)
/ selectionmode = list.soa.currentindex
</list>

<list targettype>
/ items = (
1,2,3,4,5,6,7,8,9,10,
11,12,13,14,15,16,17,18,19,20,
21,22,23,24,25,26,27,28,29,30,
31,32,33,34,35,36,37,38,39,40,
41,42,43,44,45,46,47,48,49,50,
51,52,53,54,55,56,57,58,59,60,
61,62,63,64,65,66,67,68,69,70
71,72,73,74,75,76,77,78,79,80,

81,82,83,84,85,86,87,88,89,90,
91,92,93,94,95,96,97,98,99,100,
101,102,103,104,105,106,107,108,109,110,
111,112,113,114,115,116,117,118,119,120,
121,122,123,124,125,126,127,128,129,130,
131,132,133,134,135,136,137,138,139,140,
141,142,143,144,145,146,147,148,149,150,
151,152,153,154,155,156,157,158,159,160)
/ selectionmode = list.soa.currentindex
</list>


<list correctresp>
/ items = (
    57,0,57,0,57,0,57,0,57,0,
57,0,57,0,57,0,57,0,57,0,
57,0,57,0,57,0,57,0,57,0,
57,0,57,0,57,0,57,0,57,0,
57,0,57,0,57,0,57,0,57,0,
57,0,57,0,57,0,57,0,57,0,
57,0,57,0,57,0,57,0,57,0,
57,0,57,0,57,0,57,0,57,0,
57,0,57,0,57,0,57,0,57,0,
57,0,57,0,57,0,57,0,57,0,
57,0,57,0,57,0,57,0,57,0,
57,0,57,0,57,0,57,0,57,0,
57,0,57,0,57,0,57,0,57,0,
57,0,57,0,57,0,57,0,57,0,
57,0,57,0,57,0,57,0,57,0,
57,0,57,0,57,0,57,0,57,0)
/ selectionmode = list.soa.currentindex
</list>

I.e. if the 3rd item in <list soa> is randomly selected in a trial, the 3rd item in lists cuetype, targettype and correctresp will be selected respectively for that trial.

Your <list soa> contains only 80 items, i.e. the other lists can only select from their first 80 items as well. You never reach items 81 to 160.

> 2. I have the feeling that the presentation of the pictures and the SOAs are randomized (as I would like to have it). Is that true? How do I know from the syntax?

Random selection without replacement is the default behavior. I.e., if no /select or /selectionmode attribute is explicitly defined saying otherwise, that's how a <list> -- here <list soa> -- will behave. It will sample randomly without replacement from its 80 items.

> 3. I would like to have two groups: group 1: go-cue: dotted frame, no-go cue: full frame; group 2: no-go-cue: dotted frame, go cue: full frame. I remember that this works in other tests as well, e. g. AAT. I have already looked up the script but I don’t know how to convert that into my script.

You define between-subjects conditions by setting up two <expt> elements -- one per group. Set the stimuli as needed /onexptbegin in the respective <expt> applicable to the group.

Hello!
I am now trying to modify the Go/No-Go task (http://www.millisecond.com/download/library/gonogo/) into a Food Go/No-Go task. I planned to modify the task as follows:

I would like to use:
80 pictures of food and non-food items as cue-targets (every picture is presented twice)
+ 5 different SOAs (100, 200, 300, 400, 500 ms)
+ 160 targets (the same pictures as in [1], once with a go-target (dotted frame), once with a no-go target (full frame) --> 80 * 2 = 160)
(due to the design, go / no-go ratio is 1:1 (50%))

Now I have some problems. I attached the modified script and inserted a paragraph with my adjustments at the end of the file.

1. I ran the script and but there must be an error in the syntax. All cues appear 2 times (as I intended), but all 160 cues are followed by the pictures of the go-target. What did I do wrong?
2. I have the feeling that the presentation of the pictures and the SOAs are randomized (as I would like to have it). Is that true? How do I know from the syntax?
3. I would like to have two groups: group 1: go-cue: dotted frame, no-go cue: full frame; group 2: no-go-cue: dotted frame, go cue: full frame. I remember that this works in other tests as well, e. g. AAT. I have already looked up the script but I don’t know how to convert that into my script.

Thank you very much for your help!!
Best
Alex

Thank you very much for your opinion. I think I will return to your help anyway;)

Yes, you should be able to take the either the Go/No-Go script or the Food Go/No-Go and modify it according to your needs. I'd probably use the latter, even though it is only available for Inquisit 5. The first step, then, would be to replace any Inquisit 5-specific syntax (i.e. syntax features not available in Inquisit 4) with Inquisit 4 syntax compatible equivalents. Then tackle the remaining modifications.