Response to a slide

David McFarlane mcfarla9 at msu.edu
Thu Feb 26 14:29:18 UTC 2009


I wrote,

> I had an experiment where this technique solved a lot of problems.

Sorry to keep posting in piece-meal fashion, but just to explain a bit...

We had a task where we rapidly looped through a set of slides (i.e., new 
slide on each screen refresh) and wanted to stop when the subject 
responded.  I first did it as you described, testing for a response to 
the slides themselves.  But much of time the program would not detect 
the subject response.  When I thought it through and looked at the 
timing, I realized that in this case the program spent a good proportion 
of its time between each slide, whereas it could collect responses only 
during each slide's run; e.g., if a slide appeared every 17 ms, with 7 
ms for in-between-slide setup and 10 ms of actual slide running (even 
though it does remain on the screen for the full 17 ms), my program got 
responses only during the 10 ms interval so 7/17 = 40% of the time my 
program could not get a response!

I solved the problem using one pre-loop object with extended input as 
described in my previous post, and I have described this just in case it 
can ever do anyone else any good.

-- David McFarlane, Professional Faultfinder

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---



More information about the Eprime mailing list