+xHi Dave,
No problem. I need the following scripts in the visits outlined below. The participants will all complete the same tasks except for at the second visit. Let me know if I can provide any other info!
-visit 1: stroop, emotion dot probe (all participants)
-visit 2: stroop, emotion dot probe, stop signal (group 1)
-visit 2: stroop, emotion dot probe, stop signal, MID (group 2)
-visit 3: stroop, emotion dot probe, stop signal (all participants)
-visit 4: stroop, emotion dot probe, stop signal (all participants)
This is how I have the batch script written:
<batch>
/ sessions = (1 of 4)
/ file = "stroopwithcontrolkeyboard.iqx"
/ file = "emotiondotprobe.iqx"
</batch>
<batch>
/ sessions = (2 of 4)
/ file = "stroopwithcontrolkeyboard.iqx"
/ file = "emotiondotprobe.iqx"
/ file = "stopsignaltask.iqx"
/ file = "monetaryincentivedelaytask.iqx"
/ groups = (1 of 2)
</batch>
<batch>
/ sessions = (2 of 4)
/ file = "stroopwithcontrolkeyboard.iqx"
/ file = "emotiondotprobe.iqx"
/ file = "stopsignaltask.iqx"
/ groups = (2 of 2)
</batch>
<batch>
/ sessions = (3 of 4)
/ file = "stroopwithcontrolkeyboard.iqx"
/ file = "emotiondotprobe.iqx"
/ file = "stopsignaltask2019.iqx"
</batch>
<batch>
/ sessions = (4 of 4)
/ file = "stroopwithcontrolkeyboard.iqx"
/ file = "emotiondotprobe.iqx"
/ file = "stopsignaltask.iqx"
</batch>
I see, thank you for the clarification. The problem here is the combination of both /sessions and /groups at the same level. That won't work: The respective <batch> will run when *either* attribute applies, i.e. enter session number 1 and group number 1, and those two batches apply and will be executed:
<batch>
/ sessions = (
1 of 4)
/ file = "stroopwithcontrolkeyboard.iqx"
/ file = "emotiondotprobe.iqx"
</batch>
<batch>
/ sessions = (2 of 4)
/ file = "stroopwithcontrolkeyboard.iqx"
/ file = "emotiondotprobe.iqx"
/ file = "stopsignaltask.iqx"
/ file = "monetaryincentivedelaytask.iqx"
/ groups = (
1 of 2)
</batch>
The only way around that is to get rid of either /groups (or /sessions) at that level and perform the split into different groups for session #2 in another way , e.g.
//session 1
<batch>
/ file = "stroopwithcontrolkeyboard.iqx"
/ file = "emotiondotprobe.iqx"
/ sessions = (1 of 4)
</batch>
//session 2 groups 1 & 2
<batch>
/ file = "stroopwithcontrolkeyboard.iqx"
/ file = "emotiondotprobe.iqx"
/ file = "stopsignaltask.iqx"
/ file = "group1_vs_group2_shim.iqx"/ sessions = (2 of 4)
</batch>
// session 3
<batch>
/ file = "stroopwithcontrolkeyboard.iqx"
/ file = "emotiondotprobe.iqx"
/ file = "stopsignaltask.iqx"
/ sessions = (3 of 4)
</batch>
// session 4
<batch>
/ file = "stroopwithcontrolkeyboard.iqx"
/ file = "emotiondotprobe.iqx"
/ file = "stopsignaltask.iqx"
/ sessions = (4 of 4)
</batch>
where "group1_vs_group2_shim.iqx" is set up to adminster the MID to one group, but not the other:
<include>
/ precondition = [
mod(script.groupid, 2) == 1;
]
/ file = "monetaryincentivedelaytask.iqx"
</include>