Block actions

Jump to bottom Edit New page

Valentin Gologuzov edited this page Jan 4, 2015 · 1 revision

#Draft

Goal: Split Block FSM into the two independent state machines. User part is not affected by execution token.

User actions

Block configuration: enter parameters, link inputs, do data annotation.
Compute scores/visualization.
Run block. Do we really want this? Let's forget about it for now. And only run

Reserved states:

modified - indicates that block is being configured by user, also initial state
ready - block is in the valid state for auto execution
running - block is being executed at least for one execution token

Auto execution actions

Deterministic flow, we can draw FSM with exception handling.

Reserved states:

notready - execution is impossible, during user configuration and after error occurence
ready - can start execution
done - execution was successful

We should also define partial bi-directional relation between states in this two FSMs:

All User states except ready => Auto execution notready
User ready <--> Auto execution ready
Auto execution [notready, done] => User _modified