#### Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Supported by

# [solved] Record Random Order

edited February 2014

Hi All,

I have tried searching the forum for the answer to this but the answers all seem to be combined with other questions that need answering!

Basically I am just trying to adapt the tutorial experiment to get a hand of things, and am only planning on running each cycle once, which I have done. However, the cycle will be in a random order.

I cant figure out a way for logger to output the sequence/trial/cycle number that goes with each response the participant gives.

The idea is each cycle will provide a priming word, however in the output it would be easier for me if I could see which RTs were associated with each cycle (as cycle 1-4 may use one word, whereas 5-8 may use a different word, so it would allow me to group these together).

Thanks in advanced!

Dan

## Comments

• edited 5:58PM

Hi Dan,

I'm not quite sure which of the options below you were looking for, so I'll give them both:

Log running order of random sequences

To log the current cycle number, it's easiest to use a variable that is auto-created by OpenSesame. Let's say you have a `loop` that runs a `sequence` called single_trial. The auto-created variable that keeps track of the amount of times this sequence is run (which equals the cycle number) is then called count_single_trial. For the first cycle its value will be 0, for the second its value will be 1, ..., for the Nth cycle its value will be N-1. So this will produce the order [0,1,2,3,4] for five trials.

Log cycle number regardless of running order

To log the cycle number, the easiest thing to do is add a variable called cyclenr to your loop. Log this variable and you will know exactly which cycle was run when. An example of the order this produces could be [3,2,4,1,0] for five trials.

Does this make sense?

• edited 5:58PM

Yeah definitely, I cant believe I didnt think of the doing the second option!

Thanks!

Sign In or Register to comment.