-
-
Notifications
You must be signed in to change notification settings - Fork 679
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
randomize_order produces unexpected results #2783
Comments
Hi @matanmazor, The The way to do what you are after is using the Cheers! |
Thanks @jodeleeuw, that's very helpful. |
@becky-gilbert if you are still working on docs updates what do you think about adding some clarification to the tutorial to cover this point? |
@matanmazor! sorry about the confusion over how this works, and thanks for flagging it! There's now a note about this in the documentation Simple RT Task tutorial. It's in the box called "Info: Randomizing timeline variables". I didn't wait for feedback on this new info box because I was making some other docs changes alongside this one that I wanted to get out quickly. But if you have suggestions for improving the docs on this, please let us know! |
Also @jodeleeuw @bjoluc you might've noticed this already, but in case not: I also made a few other changes to the RT Task docs alongside this one:
See 540046b. I went ahead with these changes because I figured they were pretty uncontroversial, but just let me know if you want me to change anything, or feel free to edit directly. |
Dear Josh and team,
I'm using JsPsych for all my online experiments (🙏), and today for the first time I noticed an unexpected behaviour: when using 'randomize_order' to randomize trial order within a block, randomization seems to constrain the max number of consecutive trials in a row to 2. I always thought randomizing this way should result in an entirely pseudo-randomized trial order, without any constraints.
I was wondering if there's a way to relax this constraint, and whether this behaviour is expected/documented (I couldn't find it in the docs but maybe I'm searching in the wrong place).
Here's a code snipped that should reproduce this behaviour, adapted from the demo experiment in the tutorial:
(the number of switches between 1 and 2 is around 75% and not 50% as expected by chance alone).
Many thanks!!
-Matan
The text was updated successfully, but these errors were encountered: