Sub_loops not maintained in web version

m.vel · December 2023

Hi All,

I have designed two tasks with mouse click response in which I want the participants to click in the designated areas. I have done this by creating sub loops, as per the mouse click instruction videos, so that a trial stays on the screen if a undefined region of interest has been clicked.

Once I have exported my task and tested it on JATOS, the task progresses no matter where I click. So, does this mean that the sub loops are not preserved in the web version? How can I make sure that the online participants click in the defined ROIs. I am attaching the experiment and providing a link to the task.

Thank you, Marta

Link: https://jatos.it.ntnu.no/publix/LMfu637Acqi

AJT_CLI-A.osexp

sebastiaan · December 2023

Hi @m.vel ,

You're using an older version of OSWeb, in which the ROI functionality wasn't available yet. If you update to OpenSesame 4.0 with OSWeb 2.1, this will work!

Hope this helps!

— Sebastiaan

m.vel · January 2

Hi @sebastiaan

Thank you for the tip. I have now updated tip the newest version, but I cannot know if the experiment works as I am struggling with the export. When I go to the OSWeb and JATOS control panel, I have the option to export the study as a jzip study or as an html study. There is no option for JATOS study so that I can build the individual component s in my local JATOS. The current study has two components (the task and a proficiency measure), and I can save them as individual html files, but that only gives me the html file, and not all the other components I need for running the study on JATOS ( before with the export as a JATOS study I would also get the css,img,js folders along with the html file pointing to the osexp file).

So how can I assemble the task for JATOS when I can export only these two components?

I also see that now there is a button to upload the experiment directly to JATOS. Does that mean we do not have to go through the local JATOS anymore? I filled in the address for the JATOS server at my university and I created an API token for the study, but I get an error that it could not be uploaded. Does this itnergration only work with mindprobe or any JATOS server?

Thanks for all your help and happy New Year!

-Marta

sebastiaan · January 4

Hi @m.vel ,

When I go to the OSWeb and JATOS control panel, I have the option to export the study as a jzip study or as an html study. There is no option for JATOS study so that I can build the individual component s in my local JATOS.

The jzip format is the JATOS study archive. So you can simply extract it to see all the component files.

I also see that now there is a button to upload the experiment directly to JATOS. Does that mean we do not have to go through the local JATOS anymore?

Yes it does. It's essentially the same as exporting to jzip from OpenSesame and then importing the study on JATOS.

I filled in the address for the JATOS server at my university and I created an API token for the study, but I get an error that it could not be uploaded. Does this itnergration only work with mindprobe or any JATOS server?

It works with any JATOS server, so this probably means that there's a configuration error either on the server or in your settings. What is the error message?

— Sebastiaan

m.vel · January 5

Hi @sebastiaan

Thank you. Well, I have exported my components as jzips and opened to see all the elements and then assemble them into my local JATOS as per usual. I create a directory, put in all the elem,ebts form the jzips and add the components into my local JATOS. However the experiment does not run because "It has not been configured to use OSWeb". I am puzzled by this since it was exported for JATOS.

The screen aslo says to use the "Open form JATOS function", but this does not work because of my configuration. The error message that I get is "Server does not appear to be a JATOS server: Expecting value: line 1 column 1 (char 0) A ListRemoteError is raised when something goes wrong while trying to list all (remote) experiments on a JATOS server. This may happen when the JATOS server or API token are incorrect. This may also happen when there is a problem with the internet connection."

But either way, I would not want to run it directly form JATOS this way because I have more than one component.

I am sorry, but I am very confused now as how to approach addempling online experiments after the latest update. I am grateful for any help.

Marta

sebastiaan · January 5

However the experiment does not run because "It has not been configured to use OSWeb". I am puzzled by this since it was exported for JATOS.

As of OpenSesame 4, you need to explicitly change the back-end to OSWeb under General properties. Otherwise you can still upload the experiment to JATOS (so this is not related to the error message below), for example to share it with others or to make use of the versioning system, but you cannot run it.

The screen aslo says to use the "Open form JATOS function", but this does not work because of my configuration. The error message that I get is "Server does not appear to be a JATOS server: Expecting value: line 1 column 1 (char 0) A ListRemoteError is raised when something goes wrong while trying to list all (remote) experiments on a JATOS server. This may happen when the JATOS server or API token are incorrect. This may also happen when there is a problem with the internet connection."

This error means that there is someone listening on the other end of the connection, but it does not appear to be a JATOS server. There can be any number of reasons for this, including how the server is set up, since you mention using a server that was set up by your university. What you could do is first try to synchronize with MindProbe, which should work, so that you're sure how the configuration works:

And then contact the administrator of your university's JATOS server to see why it doesn't work there.

Hope this helps!

— Sebastiaan

m.vel · January 8

Hi @sebastiaan

Yes, the problem was that I did not set it up as a OSWeb experiment in the backend. I guess there were a lot of changes with the new version. When I do this and export the files accordingly, I am able to assembel the experiment as per usual in my local JATOS.

However, the new version did not solve my click loop issue: I am still able to click wherever and the experiment progresses. I re-set the experiment to the xperiment backend, and when I run the task locally I can click only into the designated ROIs, as I was my intention. But for the OSWeb version this does not work, even when I test it locally (not through JATOS).

So I know that the update did not affect the loops, but is this possible to implement in the web version?

I am attaching my task here for reference?

Thanks! Marta

AJT_CLI_A-os4.osexp

sebastiaan · January 8

Hi @m.vel ,

Ah, there was actually an OSWeb-specific bug in the repeat_cycle item. I just fixed it and pushed an update to OSWeb (2.1.0.2), which should appear through the automatic updater. This should fix this issue.

— Sebastiaan

m.vel · January 15

Hi @Seb

Sorry for the late reply but I was in the midsts of changing my computer os didn't want to run any more experiments while I was not on the new machine.

I redownloaded OpenSesame on my new computer, the newest version available, but I am not sure it has the updated you mentioned you pushed, because as I am testing the experiment online, I am able to click wherever, so the nested loops seem not to work.

You mentioned an automatic updater, but I do not seem to have that. I have been through all the menus in the new version, and there does not seem to be an automatic updater. I am a Mac user. I remember at some point there being a button in the menu for automatic updates, but it is not there in the new version. How can I get the OsWeb version 2.1.0.2.

I am also not sure which version i currently have, since I can only see my OpenSesame version which is 4.0.1.

sebastiaan · January 15

You mentioned an automatic updater, but I do not seem to have that. I have been through all the menus in the new version, and there does not seem to be an automatic updater. I am a Mac user. I remember at some point there being a button in the menu for automatic updates, but it is not there in the new version. How can I get the OsWeb version 2.1.0.2.

The automatic updater will check in the background for updates. (There is no menu item for it.) This usually takes a while (because it checks through anaconda, which is really slow), but after a while a green button (and a notification) will appear and you can then click this to run the updates.

m.vel · January 15

Hi @sebastiaan

Thank you for the quick reply. I will then leave OS open and see when the update option pops out.

But I did have it open for days in my session last week (I am generally not good at closing my applications) and I have never seen the option. Patience :)

M.

m.vel · January 15

Hi @sebastiaan ,

it has been a few hours and my OpenSesame was open in the background but no notification or button for the update appeared. Is it normal to take 4 hours or more?

is there a way to check for updates or to install them manually?

M.

m.vel · January 17

Hi @sebastiaan ,

it has been a few days and no green button or notification for updates appeared. I am using a Mac with an M2 chip and MacOS 14.2.1 if that helps.

Is there a way to check for updates or to install them manually?

Marta

sebastiaan · January 17

@robbertmijn Can you help @m.vel with this?

m.vel · January 22

Hi @sebastiaan ,

It seems like @robbertmijn has not been active for more than a year. Is there someone else that can look into this, or are there alternative solutions for getting the update?

Thank you!

robbertmijn · February 9

Hi @m.vel and @sebastiaan, I'm looking into the auto updater on mac. It is indeed extremely slow, and I wonder if it just freezes at some point. In my anaconda installation it successfully checks for updates (and identifies osweb as a package that needs updating), but it has not started actually updating after 45 minutes.

Manually updating in the anaconda env enables the use of ROI in osweb for me. But I'm not sure if there's another way to manually update packages. @sebastiaan, is there a way to do this from the console maybe?

sebastiaan · February 12

Hi @robbertmijn ,

Thanks for looking into this!

but it has not started actually updating after 45 minutes.

So you just to clarify: when the update notification appeared, you opened it and clicked on the 'Run update script' button. And then the conda update command just kept hanging for 45 minutes. Is that right?

Manually updating in the anaconda env enables the use of ROI in osweb for me. But I'm not sure if there's another way to manually update packages. @sebastiaan, is there a way to do this from the console maybe?

Yes, there is a way to update from the console but that's essentially by executing the same command that the updater also runs. You can also update with pip in the console, and that works (and @m.vel ) already did that, but that will end up mixing conda and pip packages, which is not ideal.

I'll send you a message on the mattermost dev team and then we'll take it from there! Something is clearly not working well here.

— Sebastiaan

Howdy, Stranger!

Categories

Sub_loops not maintained in web version

Comments

Howdy, Stranger!

Quick Links

Categories

Sub_loops not maintained in web version

Comments