Feature: hook after response given + unlimited number of hooks (array)

[JannisBush]

No description provided.

[michael-franke]

The hook system seems unable to realize basic affordances. An example is in SimonTask -> branch example_hook_problems.

Desired behavior:

• pause
• fixation cross
• 3 things happen simultaneously:
  • RT measurement starts
  • response enabled
  • stimulus shown
     
    I don't see how this is possible to be realized at present. We may wish to consider an event system based on absolute time. E.g., user specifies view-manipulating functions (same as used for customization, if possible) that kick in at different absolute times (as specified in view-instantiation).

[JannisBush]

This behavior works perfectly fine and was (almost) already there.

The problem that the stimulus hides after a short time was introduced here: hide of stimulus added, this also makes it only possible to answer after the stimulus hides (see here for explanation of the hook/trial life cycle)

The problem that the response was enabled to early was introduced here:
response enabled to early

The RT measurement was actually incorrect, because only the pause was subtracted and not the fixation time and the stim duration. I now changed it, to only start measuring the RT after the response is enabled, this means we don't have to subtract anything.

magpie-ea/magpie-simon-task@3f01f3d

Here, I pushed the fixed hooks version.

[michael-franke]

Thanks for clarifying. But this is not quite the required behavior yet. The stimulus should disappear after 500ms after all. However, the response should be enabled (and RT clocking should start) at the moment the stimulus appears. The desired behavior is implemented (without hooks and corrected mistakes in RT measurement) in branch mf_fixes. But I would love to know how to do this with hooks.

…

On 12. Apr 2019, at 21:04, JannisBush ***@***.***> wrote: This behavior works perfectly fine and was (almost) already there. The problem that the stimulus hides after a short time was introduced here: hide of stimulus added, this also makes it only possible to answer after the stimulus hides (see here for explanation of the hook/trial life cycle) The problem that the response was enabled to early was introduced here: response enabled to early The RT measurement was actually incorrect, because only the pause was subtracted and not the fixation time and the stim duration. I now changed it, to only start measuring the RT after the response is enabled, this means we don't have to subtract anything. ***@***.*** Here, I pushed the fixed hooks version. — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

[JannisBush]

Okay, then we can't use the stimulus hide step of the trial life cycle. But we can just do the same thing it does in the after_response_enabled hook.
I pushed the changes (also added the reminder) to the hook branch.

The problem (related to this #53 issue) is, that we have no after response given hook, therefore I had to clear the timeouts in the custom view/handleResponse.

Also, I realized we have no before_pause hook, which could be useful and be realized in connection to the unlimited number of hooks.