Running PsychoPy tasks on Pavlovia: coder-only task (403 error) and Builder task issues

[JKim]

Hi everyone,

I’m trying to run several PsychoPy tasks online via Pavlovia and ran into two issues.

1) Coder-only tasks (403 Forbidden)
Some of my tasks were created only in PsychoPy Coder (no .psyexp Builder files). When I sync and try to run them on Pavlovia, I get a 403 Forbidden error.
From what I understand, Pavlovia requires HTML output generated via Builder/PsychoJS.

• Is it correct that Coder-only tasks cannot run on Pavlovia?

• If so, is there any workaround to run coder-only tasks online, or do they need to be recreated in Builder?

2) Builder task runs but fails during the mouse/click stage
I have one task built in Builder that does run online, but:

• The mouse cursor is not visible during a click-response routine

• After advancing with the spacebar, the experiment throws an error and stops

Since this task includes several Code Components with custom python codes, I was wondering if the python-only code in Code Components is causing these online errors, and what’s the best way to debug or fix this.

Thank you so much for any advice!

[JensBoelte]

Hello @JKim

PsychoPy experiments cannot be run online. They are written in Python. In order to run a PychoPy experiment online, it needs to be translated into PsychoJS, which is what the Builder does when you sync your experiment with Pavlovia. Unfortunately, there is no way to get a coder coded experiment into the Builder.

@JKim

Since this task includes several Code Components with custom python codes, I was wondering if the python-only code in Code Components is causing these online errors, and what’s the best way to debug or fix this.

What is the error?

Best wishes Jens

[wakecarter]

Hi,

Python coder tasks cannot run on Pavlovia, which uses PsychoJS, not PsychoPy. Here are some of my relevant tips.

Wakefield's Daily Tips

Builder isn’t Coder I strongly discourage the use of PsychoPy Coder for the creation of psychology experiments because Builder is easier to debug, share with others and translate into PsychoJS for use online. If you already have an experiment written in Coder, pasting the code into Builder code components is not sufficient to turn it into a Builder experiment. The logic of how to arrange an experiment is slightly different because of the way Builder works with components, routines and loops. F…

Wakefield's Daily Tips

Know the difference between PsychoJS and jsPsych PsychoPy was orginally written as a set of Python libraries to support the programming of cognitive psychology experiments, much like Psychtoolbox for MATLAB. However, PsychoPy is also used to refers to the PsychoPy Builder, an experimental generator which allows a user to create experiments in Python using the PsychoPy libraries via a graphical user interface. The Python script generated by PsychoPy Builder can be further customised through the u…

[JensBoelte]

Hello @JKim

look here

Wakefield's Daily Tips

Use Auto → JS code components wherever possible Even if you aren’t planning to run your experiment online, using an Auto code component will help you spot syntax errors in your Python code. [image] There are some cases where valid Python code comes up as a Syntax error on the JavaScript side but these are rare and, when you encounter then, you can switch to a Both code component and edit or delete the JavaScript side to highlight the fact that they contain code that won’t run online unedited. …

and here for debugging online experiments

Debugging online - Thomas's demos

Hi, @thomas_pronk Could you please make your demos active again? I want to show some of my students how to debug online. Many thanks, Artur

Best wishes Jens