| Author |
 Topic  |
|
|
djp16
Starting Member
9 Posts |
 Posted - May 01 2008 : 11:31:03 AM
|
I'm having an issue with PTB 2.54 in the 3T. It's difficult to diagnose because sometimes it occurs, and sometimes it doesn't.
Problem: The initial Screen of my program displays correctly and waits for a key press to begin the experiment. Upon key press (initially, but then even before key press) the PTB Screen minimizes while program continues to run (in a minimized window?). For some reason a matlab Figure window is also generated. I thought it might be a button box issue, maybe a sticky button or something, or sticky button on the keyboard?
My program to give participants practice with the paradigm worked fine twice before the experiment, once before the participant arrived and once for the participant, and worked the night before, as did my experiment program. But Wednesday my programs have failed as described above, and have begun to run without waiting for the requisite key press.
I've subsequently tried the same program in the BIAC computer room and it works there.
Has anyone else had this or a similar issue of PTB Screens minimizing?
Thanks,
david
|
|
|
dvsmith
Advanced Member
USA
218 Posts |
Posted - May 04 2008 : 10:16:39 AM
|
I've never seen anything like that. It could be a stuck button, but other folks would've had similar issues. Is your program waiting for input from outside (you) or inside the scanner (the subject)? Even if it is a stuck button, I'm not sure why it would minimize your screens. At any rate, you could test the stuck button hypothesis at the mock scanner by holding down the input buttons to see if that replicates the problem.
The matlab figure window is being generated because you probably have something like "h = actxcontrol(’Mabry.JoyStkCtrl’);" in your script so that you can use the joystick. See http://fourier.biac.duke.edu/wiki/doku.php/huettel:psychtoolbox#button_box
Hopefully someone else will have better insight than this.
David
|
 |
|
|
djp16
Starting Member
9 Posts |
Posted - May 05 2008 : 9:28:46 PM
|
This issue was resolved after testing problematic code on several machines.
Tested without joystick code:
Mach: occasional screens not drawn
Donders: ok
4T computers: ok
Tested with joystick code:
4T computer: screen minimized (original issue)
Removed KbWait and KbCheck (separate from joystick code) and retested:
4T computer: ok
Mach: screen minimized
Converted "SCREEN" to "Screen" (not known to be a critical issue)
Mach: ok
Further note: accidentally tried to run "RiskyKid_testScanner.m" by calling "riskyKid_testScanner.m". Ordinarily, Matlab can deal with this kind of exception. On Mach, however, the resources to handle case exceptions do appear to be available.
|
|
|
| |
Topic |
|
|
|
3T Stimulus Machine, PTB 2.54, Screen minimizing
