Parameters not re-setting

Hello,

I am having trouble with trial- and block-level rules not getting implemented when conditions are met. At the block level, I want to move on to Block 2 when a counter parameter for correct responses reaches a certain value in Block 1. I got this to happen successfully in a couple of test runs but then it simply stopped happening, even though nothing changed as far as I can tell.

When I look in the data file, the correct response counter counter increments as intended (controlled by event feedback) and reaches the target exit value when expected, but the block just keeps running, and I have been completely unable to identify what the conflict might be. Even if I uncheck a trial-level rule related to the same counter, the block-level rule still does not get executed.

I have tried specifying the exit rule at the trial instead of the block level, but it still does not get executed.

At the trial level also, in one version of the experiment I’m having issues with counters that do not reset when a trial-level rule specifies they should re-set.

I feel like there must be a simple explanation - something that’s preventing rules from being executed - and would appreciate suggestions as to what that might be.

Thank you,
Anna

There must be indeed a simple explanation.

You did the right thing by specifying the exit rule at the trial level instead of the block level. One key difference between the two is:

  • Block-level rules are evaluated only after all the trials in the block have been presented.

  • Trial-level rules are evaluated after each trial.

There must be something else that you are missing. If you like, send us an email to setup a zoom meeting to go over your experiment.

Thank you so much for offering to meet, but I have solved my own problem as it turns out - I simply had to change the order of my trial-level rules in order for all of them to get evaluated as intended (e.g., my exit rule was not getting implemented because it was listed after a rule that reset the counter before the counter value could trigger exit). It was a simple explanation indeed!

1 Like

I’m glad it’s resolved.