You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This refers to separating by design (and eventually implementation) EnTK and RTS. Originally, this was derived from the requirements to use other task execution systems, e.g., Dask and others that now have disappeared. Today, this requirement is less urgent and I would suggest to de-prioritize against the one of designing EnTK for better performance.
I agree with Matteo. I mean, we probably want to make sure that adding another RTS is still possible, but it is not highest priority right now.
I've realized that EnTK does not distinguish between the final states of an RTS. Would it make sense to map the state of the RTS to internal states?
IMHO distinguishing final states is a necessity. If that is done via mapping into an RE state model or by having the RE state model expand the RTS/RP state model is really an implementation detail. Mapping will be required once we add a second RTS, until then it does not matter...
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
By @mturilli:
By @andre-merzky:
Beta Was this translation helpful? Give feedback.
All reactions