Documentation or results of systematic testing of pause button behavior available?

Jan Lause's Avatar

Jan Lause

30 May, 2013 02:29 PM

Dear MWorks-developers/-users,

as the pause button is now operational, the group I'm working with is interested in how exactly the button works, whether and how it affects plugins, data recording, stimulus presentation etc..

Is there any documentation of what behavior is expected for given situations in that the button might be pressed? Has anybody already tested situations of particular interest and reported the results? If so, who should I contact to get access to it? I'd be happy for every piece of information so I know where to start my own test procedure.

Cheers!

Jan

  1. Support Staff 1 Posted by Christopher Sta... on 31 May, 2013 02:16 PM

    Christopher Stawarz's Avatar

    Hi Jan,

    When a running experiment is paused, two things happen:

    1) State system execution is suspended, as if the experiment had executed a "wait" action with an infinitely long duration. When the experiment is unpaused, the wait ends, and execution resumes.

    2) Dynamic stimuli (i.e. gratings, movies, and all other stimulus types that derived from DynamicStimulusDriver or StandardDynamicStimulus) are paused at the current frame, just like what happens when you press the pause button on a video player while watching a video. When the experiment is unpaused, dynamic stimuli start playing again from where they left off.

    Nothing else is affected by a pausing. In particular, running I/O devices keep running, and scheduled tasks (i.e. experiment-defined "Schedule Actions" or tasks internal to plugins) keep executing.

    Components defined by plugins may respond to experiment pausing, if the plugin author so desires. To do this, the component needs to watch the #state_system_mode variable and take action when its value changes to PAUSED. However, such behavior is completely optional and must be explicitly implemented by the plugin author (unless the component derives from DynamicStimulusDriver or StandardDynamicStimulus, as noted above).

    Finally, if you want to prevent pausing during a specific block/trial/state/etc., you can set that element's "interruptible" parameter to "NO". If the pause button is pressed while the experiment is in an uninterruptible section, state system execution will continue until that section is complete. (However, dynamic stimuli will pause immediately.)

    That's pretty much all there is to know about experiment pausing. If you have additional questions, please don't hesitate to ask.

    Cheers,
    Chris

  2. Christopher Stawarz closed this discussion on 21 Jun, 2013 01:06 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