[solved] Resolution problem

boris

Hi,

I observed that the resolution set in "General Properties" was not the one used during the experiment. In fact the resolution used during the experiment is the one of the windows desktop.

I observed that under XP and a CRT screen, with OS 0.27.1 and psychopy as a backend (for the moment I had always problems with the xpyriment backend so I don't use it).

Btw, it would be nice to have the refresh rate used in the results by default. This would permit to know the precise timing display years after the experiment has been run.

Best,

Boris

sebastiaan

Hi Boris,

I observed that the resolution set in "General Properties" was not the one used during the experiment. In fact the resolution used during the experiment is the one of the windows desktop.

The way that the resolution is used depends on the back-end. In PsychoPy, the resolution is used to specify the size parameter of the Window object (link). In fullscreen mode, this parameter is ignored. For Expyriment, the resolution is used to specify the window_size parameter of the Screen object (link), which is also ignored in fullscreen mode. So it's not that OpenSesame 'forgets' to set the resolution, this is simply a property of the back-ends. I don't think that PsychoPy or Expyriment allow you to change the actual resolution in a clean way, so for now you'll have to do this in the display settings of your operating system.

Btw, it would be nice to have the refresh rate used in the results by default. This would permit to know the precise timing display years after the experiment has been run.

Indeed, that would be convenient. Thanks for the suggestion!

Cheers!
Sebastiaan

boris

Hi Sebastiaan,

The way that the resolution is used depends on the back-end. In PsychoPy, the resolution is used to specify the size parameter of the Window object (link). In fullscreen mode, this parameter is ignored. For Expyriment, the resolution is used to specify the window_size parameter of the Screen object (link), which is also ignored in fullscreen mode. So it's not that OpenSesame 'forgets' to set the resolution, this is simply a property of the back-ends. I don't think that PsychoPy or Expyriment allow you to change the actual resolution in a clean way, so for now you'll have to do this in the display settings of your operating system.

Perhaps that it would be nice if this could appear in a Resolution & Refresh Rate subpart of the Timing Section.

Perhaps, that it could be also nice to have a warning concerning "Full screen mode" or something next to the resolution part in OpenSesame (we have the feeling that in order to change the resolution, it's enough to change these numbers).

I think that it would also be interesting that in this documentation part appears the rule to specify the duration of the sketchpad if we want precise display timing. For instance what you say here is very interesting for people doing masked priming: http://forum.cogsci.nl/index.php?p=/discussion/comment/1054#Comment_1054

Best regards,

Boris

boris

I forgot: given what you said, it would be nice to have also the real resolution and the Full Screen or window mode logged in the subject file (now it's the resolution settled in OS which is not the real one in "Full screen mode")...

sebastiaan

Perhaps that it would be nice if this could appear in a Resolution & Refresh Rate subpart of the Timing Section.

I think that it would also be interesting that in this documentation part appears the rule to specify the duration of the sketchpad if we want precise display timing. For instance what you say here is very interesting for people doing masked priming: http://forum.cogsci.nl/index.php?p=/discussion/comment/1054#Comment_1054

Fyi, the documentation is open for anyone to modify and contribute: http://osdoc.cogsci.nl/contribute/documentation/

That might be a good way to put a critical mind to constructive use.

boris

Hi Sebastiaan,

Fyi, the documentation is open for anyone to modify and contribute: http://osdoc.cogsci.nl/contribute/documentation/

Great ! I made some additions mostly based on your different posts...

Again, thank you for your fabulous tool (OS is very easy to learn andu and powerful when we need it): I've already converted 1 colleague of mine to use it and I hope to convince more very soon...