Does MWorks pause for implicit display updates?

ereming's Avatar

ereming

22 Jan, 2016 04:29 PM

I know that MWorks will pause for explicit update_stimulus_display actions. Is this the case for implicit updates for as well?

I'm trying to decide whether it is safe to use a regular timer ("wait" action) within a state to time a digital output. It would be bad if the wait ended during a display update pause.

  1. Support Staff 1 Posted by Christopher Sta... on 22 Jan, 2016 06:21 PM

    Christopher Stawarz's Avatar

    I know that MWorks will pause for explicit update_stimulus_display actions. Is this the case for implicit updates for as well?

    No. Display updates are handled on their own thread, which runs in parallel with (and independent of) the main experiment execution thread. By design, explicit updates (initiated via update_stimulus_display) pause the main experiment thread until the display update thread has submitted all the relevant drawing commands to the graphics hardware (more precisely, until the equivalent of glFlush has completed). However, there's no such pause associated with implicit updates (e.g. those initiated by dynamic stimuli), because they are initiated and executed entirely on the display update thread.

    Chris

  2. Christopher Stawarz closed this discussion on 28 Jan, 2016 02:59 PM.

Comments are currently closed for this discussion. You can start a new one.

Keyboard shortcuts

Generic

? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac