Mystery timing issue

[liwenna]

Hi Evelina,

Does your task involve several pictures to be shown simultaneously or
shortly after another? How shortly? Or any other 'more heavy' tasks?
If the task design is actually a bit faster than the program is able
to load, for instance pictures, than the accumulative delay could
result in delays, although the pattern you describe (accumulating over
several runs) is pretty particular. This might be solved of there is
some space (timewise) in between the pictures that you can use to
'preload' the pictures which you'll have to tell the program with a
little script.

This script can be found elsewhere on this site or I can post it here
but I rather first here if this might actually be the problem. If not,
could you describe the task in a bit more detail?

Best,

liw

On Jan 25, 6:07 am, Evelina Tapia <evel... at illinois.edu> wrote:
> Hello,
>
> I have a simple visual priming task I want to run -- design is very
> simple (one block, one procedure repeated for 100 trials). No inline
> script or anything "fancy". When I run the script on one of the
> machines in my lab, the last few trials on the machine start slowing
> down -- there are stimulus timing/duration errors in the last few
> trials; when I run the same script again, the number of trials with
> timing issues increase and during a third run all trials have timing
> problems. I've tried this under "normal" conditions (Internet,
> background programs) and when the PC was unplugged from the Internet,
> screensaver was disabled, the PC was running under Diagnostic mode (so
> all background programs were turned off) without any significant
> changes in the outcome. Now, if I run the exact same script on
> another, very similar machine, there are no timing issues AT ALL and
> that's with Internet connected and background programs running their
> usual course.
>
> For various reasons I need to run my program on the "faulty" machine
> so I would appreciate any ideas of what might be causing these timing
> issues on one PC but not another.
>
> The "faulty" PC is running
> Windows XP Professional, version 202, Service Pack 3
> AMD Athlon
> Core Processor 3800+
> 2.00 Ghz, 2.00 GB of RAM
> Graphics card: NVIDIA GeForce8400GS, memory 512. MB, version
> 6.14.0011.8250, date March 2009
>
> The "good" PC is running
> Windows XP Media center edition, version 2002, Service Pack 3
> Pentium 4 CPU
> 3.06 GHz, 1.00 GB of RAM
> Graphics card: NVIDIA GeForce7300LE, version 8.2.6.8, date June 2006
>
> Could it be that the better/newer graphics card on the "faulty"
> machine is not functioning properly and if so, how would I test it to
> verify?
>
> Could the monitor for whatever reason be a problem?
>
> Also, I've noticed that the duration errors appear when I repeating
> the SAME script -- if I run another script (which basically does the
> exact same thing but is created in another E-studio set), it seems to
> function fine.
>
> Any ideas will be greatly appreciated.
> Thank you!
>
> Evelina

-- 
You received this message because you are subscribed to the Google Groups "E-Prime" group.
To post to this group, send email to e-prime at googlegroups.com.
To unsubscribe from this group, send email to e-prime+unsubscribe at googlegroups.com.
For more options, visit this group at http://groups.google.com/group/e-prime?hl=en.