Howdy, Stranger!

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

Supported by

Counterbalanced lists

Hello,

I am running an Opensesame experiment in JATOS. The experiment has to counterbalanced lists, to ensure that each participant only sees one of them. I did this by implementing this function:

When a run the experiment in my computer, this works because the software counterbalances the the two lists. However, when I imported the experiment into JATOS and sent the link to participate, I only got results for List 1, never for List 2. Does anybody have an idea of what may be going on?

Is there a way to counterbalance the lists of an experiment in JATOS?

Thank you for the help and kind regards :)

Comments

  • Hi Teresa,

    First, a question to clarify: You say your code runs on your computer. Do you mean on OSweb, or if you import it into your local JATOS instance? I have the feeling there might be something missing there, and then @lvanderlinden might be able to help. (I don't know where OSWeb gets the subject_nr variable from)

    If it does run on your local JATOS, then it should in principle also work on the server, if less reliably. If the subject_nr corresponds to workerID, then on the server, running many studies simultaneously, you won't necessarily get all your worker IDs neatly one after the other.

    Best

    Elisa

  • Hello @elisa,

    When I import the experiment into my local JATOS instance and I run it from there (using OSWeb), I always get the following in the results for all participants: "subject_nr":0," subject_parity":"even". This implies that all of them have done the same list (List 1) of the experiment, but nobody has done the second List. However, when I run the experiment directly from OpenSesame in my computer doing a test run, the two lists are counterbalanced.

    That is why I thought the problem may be related to either JATOS or OSWeb.

    In my JATOS local server, I have the following in the JSON input property of the OSWeb component, so I don't know what may be going on:

    Thank you very much,

    Kind regards

  • Well, then the problem is not JATOS, but how OSWeb coded the counterbalance that's not compatible with JATOS :) Let's see what @lvanderlinden says

  • I understand, sorry I posted the question in the wrong discussion forum. Thank you @elisa

Sign In or Register to comment.