Description of the problem: Hello, I have uploaded my experiment onto pavlovia, however I am having issues. In my experiment I have included the demo for the Big Five inventory as well as the demographics scale. Both of these components run absolutely fine when I run the experiment from the builder, however when my experiment is running on pavlovia both of these components are not visible. I have checked the code and compared it the code for the components in the demo pack and they are they same. Also the questions were created in an excel file, accordingly I made sure that the right file is included. Your help will be much appreciated, thank you in advance.
If either of those use the ârating scaleâ component for local experiments, they will not work online: RatingScale in online experiments
As that thread says, you can replace them with âsliderâ components.
Otherwise, you will need to link to your gitlab repository on pavlovia or give more information about the exact construction of the experiment in the builder.
Thank you for your response, sorry but I wasnât very clear. What I meant to say is that the demographic form is not visible for participants to note their responses, neither is the BFI form when the study runs on Pavlovia but both of these forms appear and work perfectly fine when I run the experiment from the desktop.
Letâs try this: For each code component, open it and make sure âCode typeâ is set to âAuto->JSâ. Re-select that option if itâs selected to make sure JavaScript code appears in the right half of the code component window. Oh, and make sure youâre on the most recent version of PsychoPy (2020.1.3).
Other than that, Iâm not entirely sure what the issue is. The Form component should work in Pavlovia as far as I know.
Thank you, does it matter if I created the experiment on an older version of psychopy but currently running it on the latest version ? If this is an issue how do I update the experiment so that it is compatible with the latest version?
Depending on what version you made it on, the steps I outlined will change what matters. 2020.1.0 added the auto->JS functionality for code components, so if it was made in an earlier version, the code simply wasnât auto-converted. However, if it was made on a version that could connect to Pavlovia at all, nothing else should need to be changed (in theory).
Since updating the auto->JS functionality for code components and now receiving this error message, also on Pavlovia when I click to pilot I see a forbidden 403 message.
raise ValueError("Found an unexpected change_type '{}' in gitpython Diff".format(this.change_type))
ValueError: Found an unexpected change_type âUâ in gitpython Dif
If you remake the study from scratch in the newest version of PsychoPy (I know, not ideal) it probably wonât have that issue, since it seems to be something about the conversion to javascript being wonky. If you made this in a much older version of PsychoPy initially, that could be it, but I would have expected it to just recompile everything from the builder.
Hello, I tried that and now I am faced with another error. For some reason when I upload the experiment onto Pavlovia I sync the experiment but the platform in which is was created never appears. I a left with a 403 forbidden error message .
Thatâs very strange. Are you sure that the pavlovia account you have in PsychoPy is the same one you are using to log in to the website, and that you are logged in when you visit the website? This is one where @jon or another website administrator might be needed.
According to the docs of git âUâ indicates an âunmergedâ file. My guess is that the project has been changed on another computer in a way that has caused a merge conflict (ie the file changed in the same place on multiple computers) and thereâs now a merge conflict. We havenât built in tools to help with sophisticated merge problems like that. Iâd suggest you use a more sophisticated tool like GitKraken (free version) to fix the merge conflict. Alternatively you would need to move the files to a new project folder and start again