+xYes, a trap for young players! I totally misinterpreted what it was doing. Thanks as always for your clear explanation and I do understand how it works now. Out of interest, when would the feature of /groupassignment = random be useful? i.e. when would one be wanting a random group Id that was not related to between subjects version? Is the idea that you use a 'if group == 1 then' command to control task behaviour throughout the script?
> Out of interest, when would the feature of /groupassignment = random be useful?
It's useful in a couple of situations, specifically when you cannot use subject ID or group ID for condition assignment, because they're already used for other purposes. Keep in mind that condition assignment is a mathematical operation, so it only works on numerical IDs. For example:
- The subject IDs you need to deal with are not numerical (e.g. Qualtrics IDs), so you can't use subject ID for condition assignment.
- You need the group ID to assign a condition in a batch script.
<batch>
/ subjects = (1 of 2)
/ groupassignment = groupnumber
/ file = "a.iqx"
/ file = "b.iqx"
</batch>
<batch>
/ subjects = (2 of 2)
/ groupassignment = groupnumber
/ file = "c.iqx"
/ file = "d.iqx"
</batch>
Then, if in any of the 4 scripts a.iqx to d.iqx above you also need to do some kind of condition assighment, you can fall back on /groupassignment = random.
/ groupassignment = random is also useful in non-web situations, for example if your protocol requires experimenters to be blind to condition assignment in a lab setting.