Post by Kerstin on Jun 14, 2020 14:21:45 GMT
Hi,
I have run a study using the following coding. I have 8 blocks in total which vary the tables of the stimuli (one task uses one table of stimuli). Each table has at least 20 stimulus objects (words or images).
block 2PPos
message PP2I enter
tasklist
2orless 16 all_before_repeat
WPos 16 all_before_repeat
NoGoP2 12 all_before_repeat
NoGoPosW 12 all_before_repeat
end
block 2SNeg
message NS2I enter
tasklist
Shape2 16 all_before_repeat
neg 16 all_before_repeat
NoGoSh2 12 all_before_repeat
NoGoNegW 12 all_before_repeat
end
In my test run I didn't get any repeats of stimuli within a block but in the live run there are 1880 are duplicates (in 47488 trials (106 participants completing 448 trials each, 56 per block). I've done a little more analysis and the only tasks which don't contain any duplication are those in pink - NoGoPosW and neg. The thing they have in common is that they both use a table called 'neg'. This is the only table which is named in all lowercase. The rest of the code seems to have been ok with mixed case, e.g. only running 16 'go' tasks and 12 nogo.
Is there any chance that this could be a quirk in acceptable code that I haven't spotted in the documentation?
Many thanks
I have run a study using the following coding. I have 8 blocks in total which vary the tables of the stimuli (one task uses one table of stimuli). Each table has at least 20 stimulus objects (words or images).
block 2PPos
message PP2I enter
tasklist
2orless 16 all_before_repeat
WPos 16 all_before_repeat
NoGoP2 12 all_before_repeat
NoGoPosW 12 all_before_repeat
end
block 2SNeg
message NS2I enter
tasklist
Shape2 16 all_before_repeat
neg 16 all_before_repeat
NoGoSh2 12 all_before_repeat
NoGoNegW 12 all_before_repeat
end
In my test run I didn't get any repeats of stimuli within a block but in the live run there are 1880 are duplicates (in 47488 trials (106 participants completing 448 trials each, 56 per block). I've done a little more analysis and the only tasks which don't contain any duplication are those in pink - NoGoPosW and neg. The thing they have in common is that they both use a table called 'neg'. This is the only table which is named in all lowercase. The rest of the code seems to have been ok with mixed case, e.g. only running 16 'go' tasks and 12 nogo.
Is there any chance that this could be a quirk in acceptable code that I haven't spotted in the documentation?
Many thanks
