Reaction Time for single items in JATOS study designed in OSWeb
Hi,
Truly sorry to be bothering you on August 16th, but I ran into two problems with my OSWeb study.
When I imported it in JATOS, no problem was detected and I run it all (it worked) to see how my variables were stored in the results file.
My experiment has 33 items, I'm attaching a screenshot to give you an idea.
I am interested in reaction times for the three target sketchpads and in the responses to the questions.
(i) First problem is that JATOS seems to be reporting the responses to the questions from the last (33rd) item only.
(ii) Second, it seems that it only reports for "average reaction times" per sketchpad. Now, the 33 items in my experiment are presented in 3 conditions within subjects through a latin square design (I have created 3 different loops were each item is presented in one of the three conditions and I am assigning each participant to one of the loops - through an inline_javascript). For this reason, average reaction time for a certain sketchpad does not tell me much, as the same sketchpad will sometimes show an item in condition A, sometimes in condition B, and sometimes in condition C.
OpenSesame did show me the reaction time per item, so I thought JATOS would, too. I had previously run into this solution for OS but I figured it wasn't needed in the version I'm using (Keyboard responses do log RTs per item)... It's in Python, but I was wondering whether a Javascript version of it (though I have no idea how to "translate" it into Javascript) would do what I am trying to achieve?
I hope my question is clear... I apologize if it's not, I am a complete newbie.
Comments
This is a question for @Daniel , I think
Probably 🙈 I didn't know where to post it and I didn't want to double post in the OSWeb Category.
I guess posting the whole experiment might help (?).
Alright I think I solved it by simply putting three different loggers, one per loop 🙈I thought putting just one at the end of the experiment was the right way to go.
Hi @ellie,
There indeed is a (hard to solve) bug that causes problems when you used multiple instances of the same logger in osweb. This is solved by using different logger items as you did, but is not ideal. We hope to find a solution for this in the near future.
Hi @Daniel, thank you for your answer!
You mentioned it is not ideal - would you mind elaborating on why? I do not seem to find any issue, except for a bit messy results file - but it seems to be logging everything I need.
That's exactly the reason. Each logger writes to the same logfile but does it in its own way, resulting in more messy log files
Fair enough, not a big deal when the other option is losing data! Thank you for your kind answers, it all seems to be working now :)
And thank you for developing such a great tool for non-programmers, it saved my PhD in these weird times.