Duke-UNC Brain Imaging and Analysis Center
BIAC Forums | Profile | Register | Active Topics | Members | Search | FAQ
 All Forums
 Support Forums
 Experimental Control
 3T Stimulus Machine, PTB 2.54, Screen minimizing

Note: You must be registered in order to post a reply.
To register, click here. Registration is FREE!

Screensize:
UserName:
Password:
Format Mode:
Format: BoldItalicizedUnderlineStrikethrough Align LeftCenteredAlign Right Horizontal Rule Insert HyperlinkInsert EmailInsert Image Insert CodeInsert QuoteInsert List
   
Message:

* HTML is OFF
* Forum Code is ON
Smilies
Smile [:)] Big Smile [:D] Cool [8D] Blush [:I]
Tongue [:P] Evil [):] Wink [;)] Clown [:o)]
Black Eye [B)] Eight Ball [8] Frown [:(] Shy [8)]
Shocked [:0] Angry [:(!] Dead [xx(] Sleepy [|)]
Kisses [:X] Approve [^] Disapprove [V] Question [?]

 
Check here to subscribe to this topic.
   

T O P I C    R E V I E W
djp16 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
2   L A T E S T    R E P L I E S    (Newest First)
djp16 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.

dvsmith 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


BIAC Forums © 2000-2010 Brain Imaging and Analysis Center Go To Top Of Page
This page was generated in 0.35 seconds. Snitz Forums 2000