sebastiaan
About
- Username
- sebastiaan
- Joined
- Visits
- 7,303
- Last Active
- Roles
- Administrator
Comments
-
Hi Robbert, Thanks for reporting this. It's clearly a bug. We'll release a maintenance release of OSWeb (1.3.1) soon to address these issues as they're coming in. Cheers! Sebastiaan
-
@elesa This is a very old discussion. As you can read on the documentation, the Android runtime for OpenSesame no longer works on recent versions of Android. In many cases, there are better alternatives now, such as using a Windows tablet or running…
-
Good to hear that you've figured it out. (I've moved the discussion to the JATOS forum.)
-
Closing as a duplicate of this discussion.
-
Closing as duplicate of this discussion.
-
> Do you have any idea on how I could check that it really is the former? You could show a first sketchpad with a "1" on it, then wait for the a second, and then show a second sketchpad with a "2" on it. Then if you run and th…
-
Hi Libgvi, That's an interesting scenario. It's actually quite easy to implement everything that you want. > My audio is playing if you click at image_button in the middle of screen or if you click at Next_button at the bottom of screen. I would …
-
Hi Zgolot, I'm not familiar with this problem. In general, and as you suggest, it sounds like something that has to do with the graphics drivers. Your workaround seems ok to me, but to be safe I would check one thing: Is it the case that the first d…
-
Hi Ruby, Without more information it's difficult to say. Could you post the experiment here, and describe in more detail what exactly doesn't work on OSWeb? Cheers! Sebastiaan
-
Good to hear you found a solution!
-
Hi Irmak, The focus=yes approach applies to form_base items, i.e. to OpenSesame script. In your case, you're using Python inline_script, in which case you can accomplish the same thing using the focus_widget keyword when executing the form: form._ex…
-
HI @Jessica Bourgin , The resolution indeed has different effects depending on the backend and operating system. Specifically, the legacy backend really changes the resolution, whereas the other backends leave the display resolution as it is and pre…
-
Hi Tom, Thanks for giving this elaborate test script. One thing that I noticed immediately is that the image files are capitalized incorrectly in the experiment. Specifically, Image_rate__3 refers to RealVAS.jpg, but the file is actually called Real…
-
Hi Josh, For OpenSesame to keep track of accuracy, you need to define the correct_response variable. If you do this, most response items, such as the keyboard_response, will automatically calculate the variables acc / accuracy. See also: https://os…
-
I'm closing this, because it strikes me as a duplicate of #4943.
-
Hi Mark, There are two questions in there. First, can you ignore all keys except for some? This is possible, but it will require some coding to handle the key presses yourself. So if it's not crucial, doing this may be more trouble then it's worth. …
-
Hi Klara, Without more details it's very difficult to say what could be going on. Could you upload the experiment here, or perhaps a simplified version that illustrates the problem? Cheers! Sebastiaan
-
Hi Bar, There is no easy way to change how the prepare and run phases are handled. The logic is always that the prepare phases of all items in a sequence (or coroutines) are called first, and then all the run phases. You could write a script that ex…
-
Hi Florian, I'm guessing you're using a German QWERTZ keyboard, given that the ^ is next to the 1? How keyboard layouts are handled exactly depends on the operating system, but generally speaking you can toggle between different modes (in Windows of…
-
> Now you should post the results of everyone's favorite teletubby somewhere... That's clearly Tinky Winky. I don't need data to know that.
-
Great to hear that you figured it out!
-
Hi Rob, Which version of OpenSesame are you using exactly? This should not happen, so if you're using the latest (3.2.6) version I'd like to see where this comes from. But don't worry: In any case, you can edit the experiment file in a text editor …
-
Hi Julienne, You're simply working with a tutorial for an old version of OpenSesame. For the latest version, see: https://osdoc.cogsci.nl/3.2/tutorials/beginner/ Cheers! Sebastiaan
-
> So, after several hours I could find out what is happening. This code 'GetSensorValue' is always gonna give us one value from the device (I gonna attache some prt sc from the manual). The value only change when I press enter on the link. Absolu…
-
Hi David, There are a few ways in which you could implement this. The easiest would be to simply validate the form to check if the slider values (or textinput values) add up to some value before accepting it. https://osdoc.cogsci.nl/3.2/manual/forms…
-
Hi, Thanks for reposting your question here 😊 I see what you mean. The problem seems to be that some of the variables (such as item and item_type) are only defined later on in the experiment, after the logger has already been executed once, and ther…
-
> While testing that version, I have seen that I can reference the image files directly from a specific location on the drive and that I don't need the file pool. Apparently, it does not change the access time to the files. Is it correct ? That i…
-
Hi RobotNoob, You can install expyriment with pip. If you've tried that, and expyriment was successfully installed, but still didn't appear in OpenSesame, then you probably have multiple Python environments, and installed expyriment into the wrong o…
-
> When it is done, the implemented test can be shared by example experiments? That's very generous! 👍️ There's no systematic system for sharing experiments. However, you could upload it to the OSF in a public project. That's what I usually do.
-
Hi Stéphanie, The problem is clear: The keyboard is polled, and it responds to escape presses (because you can abort), but apparently the key value is never "return", and therefore you never break the while loop. But why this happens, and …