dear chris,
i know that you are away, but i figured i would document the testing of this while it is in my head.
firstly, in the old days you didn’t need to declare the variable in the range_replicator, is that different now.
secondly, when the range_replicator is used during an experiment, does it have to include a trial in it? or can it replicate over actions?
finally, the example you sent me loads fine, and when i run it goes through the loading process but then barfs when it is meant to display? any idea on why that might happen on my machine.
i will continue testing, but figure, i would send an email with initial thoughts.
best
najib
I’m attaching the example experiment referenced by Najib.
Attachment: load_and_unload.xml (1.99 KB)
Hey Najib,
firstly, in the old days you didn’t need to declare the variable in the range_replicator, is that different now.
Yes, you need to declare the variable used in a range replicator, and the variable’s scope must be “local”.
secondly, when the range_replicator is used during an experiment, does it have to include a trial in it? or can it replicate over actions?
In an experiment, a range replicator can contain only paradigm components (protocols, blocks, trials, lists, task systems, task system states, or other range replicators). If you want to replicate over actions, you have to enclose them in a paradigm component.
finally, the example you sent me loads fine, and when i run it goes through the loading process but then barfs when it is meant to display? any idea on why that might happen on my machine.
The entire experiment runs successfully on my machine. In what way does it “barf” for you?
Chris