Hi all,

There is a new beta release with the above named features. It adds to the existing set of new features in oTree 6.0 beta.

More details here:

https://otree.readthedocs.io/en/latest/misc/version_history.html

Enjoy and let me know how it goes!

Chris

Hi Chris, 

This update is very useful. I'm currently testing the group_by_arrival_time presence detection function. I see that if the participant fails to confirm they are active, they see a page where they can click a button to return to wait page. I was wondering if in addition to this, we could use the fact they didn't confirm their activity to show them a different app and/or if they take too long to click the "Return to wait page", then we direct them to another app. Would this be possible? Thanks much. 

Best, 
Gabriela

Hi, thanks for the feedback and suggestion! I will think about a way to do this. Another user requested that also.

Thanks for the quick reply, Chris. 

Thanks for taking in the feedback. I'm looking forward to experimenting with this version. In the meantime, I noticed that there's no way to tell if a participant has visited the "Return to wait page" Page. I checked both in the APP data and Pagetimes data. Would it be possible to add this information somewhere, please? It would be useful to at least get a sense of how many participants are actually clicking on the button to return to the Wait Page. 

Best, 
Gabriela

hi, what datapoints would be useful to you? especially for deciding to exclude the participant from the study. just a boolean indicating whether they went to the "inactive" page at some point? or more detailed info such as how many times they went there, how long they went there, etc? what are your criteria for deciding if a participant should be excluded from the group game, sent to the end, etc?

Hi Chris, 

In my case, the criteria to exclude a participant would be (1) if they went to the "inactive" page (a boolean would do), and (2) they took too long to click the "back to wait page" button, ideally I would like to be able to set this time. Here I imagine there would be a time variable somewhere that I could use in combination with (1) to classify the participant as inactive and thus, exclude them, i.e. direct them to another APP. I don't think the number of times they went to the "inactive" page is relevant to me right now, as long as they go back within a reasonable time. But could be useful to know nonetheless. 

Thanks for considering these changes! 

Best, 
Gabriela

Hi Chris,

Would the beta version work on macOS? I am testing a project, and I seem to be stuck after clicking the Submit button on a quiz page.

I am with otree==6.0.0b14 and Python 3.12.5

Best,
Richard

Hi, it should work on every system.

i see the message "submitting response"; where does that message come from? it's not a built-in message from oTree. maybe you have some custom javascript code that is encountering an error? check your browser's developer console for errors and network requests. also look at the otree server logs.

Hi Chris,

Thanks for your reply. I think the problem was that all live pages code stopped working. I was able to run the project with beta using a virtual environment (venv).

Best,
Richard