Avatar

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Supported by

sebastiaan

About

Username
sebastiaan
Joined
Visits
7,303
Last Active
Roles
Administrator

Comments

  • Thanks for taking the time to make that screencast. I see what you mean now. Somehow, OpenSesame apparently interprets clicking the script buttons as a rename signal, because the rename dialog should not appear. Still, I haven't managed to reproduce…
  • I just tried it also under Windows 7, and I don't experience the same thing. Is there any other indication that something goes wrong? E.g. perhaps there is an error message in opensesame.exe.log when you close the program? If it does no harm, then I…
  • Hi Andrea, In principle, the quotes should be automatically stripped by your spreadsheet (or other type of analysis software). The logger uses a CSV format as specified for example here, which specifies that any field can have double quotes around …
  • Thanks! Indeed, a similar bug to the one that you reported before: 'sequential' and 'random' should not be translated by the GUI, because these words have a special meaning. Regarding to the second bug. I don't see the same behaviour. Do you have a…
  • Hi Johannes, I took a closer look and indeed: Regarding the second error, there is a bug in the 0.27 pre-release in the way that variables are evaluated in the GUI for the sampler item (and perhaps other items as well, I'll have to look into this).…
  • Hi Johannes, I don't think it's as bad as it sounds! First of all, the PsychoPy warnings (the ones preceded by a timestamp) that you see in the debug window are harmless. That leaves us with two real errors. The first error is a bit strange, beca…
  • Hi Niv, You could, in theory, compile your experiment to an .exe file, but if your aim is to have an easy way for participants to run it on their own computer this is probably more trouble than it's worth. Instead, you could take a look at openses…
  • I see, that's unfortunate! As a workaround, you could try running your experiment in a separate process. To do this, you open Menu→ Tools → Preferences and under Run options select Run experiments in a separate process. You can leave the run comman…
  • Greetings. First of all, I would like to express my deep felt thanks for such an amazing project and software. It is truly a boon for science, that we have access to such a good stimulus delivery and experiment builder software! Thank you! I'm cur…
  • Hi Johannes, If I understand correctly, you encounter the following problems under Windows XP with 0.27~pre24: * The sound playback doesn't work properly with PsychoPy backend (like before) * Renaming the main experiment sequence causes it to go t…
  • Hi Madjid, You're probably not doing anything wrong. The media_player is known to be a bit flaky sometimes, and this issue could be due to any number of things. You might try the following: * Convert the video to a different format, and see if thi…
  • The set() and get() methods are intended to store and retrieve your experimental variables, i.e. variables that you want to write to the log-file, strings that you want to show, etc. As you experienced, they will automatically convert values to a fl…
  • Hi Hansika, Just so we're on the same page, you mean the text_display plug-in, right? Or do you use a custom plug-in called text_screen? At any rate, I think the problem that you're seeing is a bug in the Mac OS version where newlines aren't dealt…
  • I have placed a few eyelink_log items before stimulus presentation with messages for the log. Could this be an issue? That shouldn't be a problem. The eyelink_log plug-in just adds a few messages to the log-file, but it doesn't pause recording, or …
  • I've had a crash course in how to use EyeLink today and seem to be able to successfully calibrate it through OpenSesame (although when instructed to press q to return to the menu it in fact displays a blank screen and when I press V to 'validate acc…
  • Please see 0.27~pre24 (or later). The workaround is now that the first item in the parallel plug-in is not run as a thread, but in the main process. Therefore, you should be able to collect keypress responses, but only if you place the keyboard_res…
  • Hi Anthony, You are correct: There's a Windows-specific issue in which the 'threads' (i.e. the software processes running in parallel) do not have access to the keyboard. So your experiment is fine, and it does work. Just not under Windows, which i…
  • Hi Boo, Right, it seems that the newly updated EyeLink plug-ins use some functionality that wasn't present in OpenSesame 0.26. So the solution would be to either * Use version 0.17 of the plug-ins * Run the latest pre-release of OpenSesame 0.27. …
  • Thanks, yes, that's a good suggestion. I fixed it and I hope that I also fixed the keyboard problem. I'm not 100% sure what caused it, though, so please let me know whether or not the keyboard issue is gone with 0.27~pre23 (which I'll upload later t…
  • Hi Boo, I think there's a slight misunderstanding here: What Lotje meant is that you should not reset the feedback variables after each trial (either by a reset_feedback plug-in, or by ticking the 'Reset feedback variables' box in a feedback item),…
  • Right, yes! I forgot to mention that (crucial) part: See my edit in the previous post.
  • Hi Anthony, Just so we're on the same page: You want to present a target stimulus for 120ms, followed by a blank display (or a mask or something) and you want to collect a keyboard response from the start of the target stimulus with a timeout of 20…
  • Just for my understanding: The scanner essentially emulates a regular keyboard and sends and = sign to indicate the start of the experiment? And your experiment begins with a keyboard response that waits until an= is pressed? Is that correct? That …
  • Right, based on the file you sent me the problem is clear. There are actually two things. The first is that you continuously poll the keyboard by setting a very low timeout: my_keyboard = keyboard(self.experiment, keylist=allowedkeys, timeout=0) I…
  • However, the pre-release creates new bugs. Such as that the other parts of my experiment won't do it anymore (e.g. it does not react to keypresses anymore). There are slight differences between 0.26 and 0.27, but your experiment should be portable …
  • I see, that's probably a bug/ difference due to the older version of PsychoPy that is included with 0.26. With 0.27 pre-releases it should work. If you want to stick to 0.26, I would bring this up on the PsychoPy mailinglist, as it's a separate proj…
  • Ah, I see. Here's a simple example that allows you to change the luminosity of the two patches with the up and down keys, and accept the colours by pressing space. The colours are in HSV space, which means that they are defined in terms of hue, sat…
  • So far, I have not found a function that is able to do that (is there?). That means if I want to run all subparts in one I need to copy paste element by element into a masterfile which is really time consuming! What you could do is simply open your…
  • If I understand correctly, you basically want to show two patches of a different colour in very rapid succession, right? The script below should get you started. It's not a full experiment, but you can add this script to your trial_sequence, and adj…
  • Right, OpenSesame uses computer units, because these are unambiguous. But, of course, given knowledge of your set-up, you can translate these into other units. I wanted to know how exactly spatial frequency is defined and how you can define contras…