HELP - online experiment issue

[wakecarter]

Hi,

You haven’t given much information about your experiment, or your version of PsychoPy but 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

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. …

Wakefield's Daily Tips

ReferenceError: varName is not defined This is one of the most common errors in online experiments [image] It is also one of the easiest to solve. The issue is one of “scope”. To define a variable so it has scope across your whole experiment, all you have to do is assign it a value. Don’t edit your JavaScript to add “var” or “let” commands. To give your variable scope assign the value in a Begin Experiment code component tab outside any clauses (i.e. no Python indents). [image] I usually s…

Wakefield's Daily Tips

The answer is (almost) never to edit the generated code When you create an experiment in Builder, PsychoPy then generates a Python file which you can use to run the experiment locally and two JavaScript files suitable for running the experiment online (using current and older browsers). If something doesn’t work, there may be a temptation to make edits directly to the Python/JavaScript files rather than the Builder file. However, this is generally a bad idea for two reasons: The process is o…

Wakefield's Daily Tips

Developer Tools If you encounter an error in an online study, open the Developer tools console using Ctl-Shift-I in Windows/Chrome, Cmd-Opt-J or Cmd-Opt-I in Mac/Chrome, F12 in IE/Edge, Ctrl-Shift-J in Windows/Safari or Ctrl-Opt-J in Mac/Safari. [image] [image] Select the Console tab at the top and errors item on the left to view errors. Ignore the 404 error related to favicon.ico Look for the error that appears on the main screen and click on the link next to Scheduler._currentTask. Take…