rip

About

(Quote) But that wouldn't solve my problem. It's the between cycle jitter that I'm concerned about. Adding another sketchpad will just push the jitter down one event. It's still going to be there. (Quote) Right which is why the "load while pre…

in [open] Timing Accuracy and Stimuli Onset Times Comment by rip December 2014
(Quote) Yes that's how I'm using the sequence. (Quote) Wouldn't a more sensible approach be to load the next stimulus while the current one is being presented (a la E-Prime, Presentation, etc...)? (Quote) In fMRI sure, but even there I would want …

in [open] Timing Accuracy and Stimuli Onset Times Comment by rip December 2014
(Quote) Everything is in a sequence item. The prepare and run strategy is a poor choice with sequence items that have only one event in them. It looks like it's a combination of the data logger and stimulus preparation that causing the unexpected o…

in [open] Timing Accuracy and Stimuli Onset Times Comment by rip December 2014
(Quote) This is not true. In fact even modern Android devices will give you unacceptable reaction times with large variability between devices. For example: http://bgr.com/2013/09/20/iphone-android-touch-screen-responsiveness/ Please do some more …

in [open] Response time accuracy Comment by rip December 2014