Open mynamewh opened 6 years ago
Hello WH, did you find out what the problem was? I ran into the same issue, it seems like some of the stimulus cycles get skipped. Best, MN
Hi All,
If you want to debug, I suggest calling your experiment from the command line, then saving the params file and posting it.
For example, you can do the following (or something like it),
params = retCreateDefaultGUIParams;
params.fixation = 'dot with grid';
ret(params);
And then post both the code you ran and the saved file (which should be on your Desktop)
-Jon
On Fri, Jun 29, 2018 at 10:58 AM Naubody notifications@github.com wrote:
Hello WH, did you find out what the problem was? I ran into the same issue, it seems like some of the stimulus cycles get skipped. Best, MN
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/vistalab/vistadisp/issues/11#issuecomment-401380512, or mute the thread https://github.com/notifications/unsubscribe-auth/ACBX3uwurjNSbNUvhbmj19enZ9aBVzPRks5uBkCUgaJpZM4TZm92 .
-- Jonathan Winawer Assistant Professor of Psychology and Neural Science
New York University 6 Washington Place New York, NY, 10003 (212) 998-7922 (phone) (212) 995-4018 (fax) jonathan.winawer@nyu.edu http://psych.nyu.edu/winawer/
Hello! Sorry to bother you. I ran vistadisp on Ubuntu 16.06 with matlab 2014a. I found the duration of stimuli is shorter than expectation. For example, when I set type=8 bars, TR=2.5s, period=360s, question appeared: [showScanStimulus]:Stimulus run time: 289.054455 seconds [should be: 359.937500]. The stimuli presented correctly, just the duration was wrong. I checked the codes and fresh rate of my monitor, they are just fine. I am very confused about that, could you help me? Thank you very much! WH