Webgazer not working

veskerm

Hello, I just downloaded the latest version of OpenSesame (4.0), and wanted to try the sample experiment for Webgazer integration found here: https://osdoc.cogsci.nl/3.3/manual/eyetracking/webgazer/

The sample already hosted on https://jatos.mindprobe.eu/publix/BowSAFY2VWl seems to work fine so I downloaded the actual experimental file from here https://osdoc.cogsci.nl/3.3/attachments/webgazer.osexp

and added the link to the Webgazer library as shown in the instructions

and set the experiment to run in the browser using OSWeb

However, when I run it I end up getting an error that seems to indicate that the Webgazer library isnt actually being loaded:

So am I just missing some step in the setup, or is this a bug?

Also, I noticed that the addition of the link to the Webgazer library and the setting for running the experiment in the browser dont actually get saved from session to session when I save the experimental file, and need to be set every time I start OpenSesame.

Thanks in advance for any help!

eduard

Hi,

Not an expert here, but I suppose this is a conflict of versions. That experiment was written for 3.3, and apparently does not work with Opensesame 4.0. Why this is I don't know, but potentially to do with any of the backwards incompatible changes:

https://osdoc.cogsci.nl/4.0/notes/400/

Eduard

veskerm

Hi Eduard, you were right!

I switched back to 3.3, and the experiment worked. However, this begs the question of how to integrate Webgazer into experiments made in version 4 and later, since the way of doing it in 3.3 (specifically, linking external libraries) isn't working anymore?

eduard

Hi,

Yeah, that's a valid point. OS4 was released before everything (plugins, tutorials, etc) that you can find on the web was updated to 4.0, mostly for practical reasons. In the case of webgazer, I don't know whether the support as intentionally dropped, or just removed temporarily until someone made changes to it to make it work with the latest version of OS4. Maybe @sebastiaan knows?

So for now, you can either stick with 3.3 and see what the future might bring, or you can to speed up the process, maybe even contribute some code yourself.

Eduard

sebastiaan

Hi @veskerm and @eduard ,

There indeed appears to be an issue with including external libraries, such as webgazer.js, in OSWeb 2.0. I don't know what causes it right now, but it's on the radar and should be fixed soon in an update. (I suspect it's a minor issue that slipped through the cracks.)

— Sebastiaan

veskerm

@sebastiaan

Thats great to hear! So does this mean that it should be safe to start building my experiment in OS 4 without Webgazer for now, and then at some point when the external library issue is resolved I could simply add Webgazer to the complete experiment?

sebastiaan

@veskerm Yes, although I can of course not offer guarantees, that's what I would do. I intend to release a minor bugfix update next week. This should appear through the automatic updater.

camila_hinojosa

Hello!

I have a question regarding an issue I'm encountering. I'm working with OpenSesame 4.0.5 and OSWeb, and I'm trying to use WebGazer. However, I keep getting the same error (the one shown in the picture that @veskerm shared) both when running the experiment locally and through JATOS.

I was wondering if there is anything I can do to fix this? I also found this https://github.com/brownhci/WebGazer/issues/296, but I'm not sure if it could be helpful.

Additionally, if I work with version 3.3, can I still upload the experiment in JATOS? I need to save the information that WebGazer provides along with the experiment results. Is this possible, and would everything be stored in JATOS? To achieve this, do I only need to use the logger item?

Any guidance would be greatly appreciated!

Thanks in advance.

camila_hinojosa

cvanbuck

Hi @camila_hinojosa,

Regarding your issue, I see you're using OpenSesame and OSWeb 4.0.5. As you may have guessed from the previous comments, these are outdated versions, and many bugs, likely including the one you're experiencing, have been fixed in later releases. Please first try to update to the latest version (currently 4.0.32) and see if that resolves the problem.

Let me know if you need further help!

Claire

PS. I noticed that you've posted the same question both as a reply to an existing thread and as a new discussion. To keep the forum organized, it's best to post a question only once. Thanks!