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
Right now we have quite tricky structure for the model-information to get to APIVirtualDevice etc. Most is happening in backend/.../modelSupport/ModelService.scala and it would be nice to have a better structure for this.
One idea is to implement this information with the new Model-curcuit or in a new parallell circuit depending on the Model-Curcuit.
Suggestion of Curcuit-info
Current Model
All driverThings from model/ or all drivers with thingToDriver
All resources / resourceThings
All operationThings from model
All abilities from model
Right now it is happening with operationToAbility
The states + status of the drivers
The states + connections between resource and driver
The states/conditions of the abilities
The states/conditions (or domain) of the operations
This Information is maybe needed
Current Runner?
[This issue is in progress]
The text was updated successfully, but these errors were encountered:
aleastChs
changed the title
Communicatio between Widgets Circuit
Communicatio between VD-Widgets
Jun 20, 2018
aleastChs
changed the title
Communicatio between VD-Widgets
Communication between VD-Widgets
Jun 20, 2018
Right now we have quite tricky structure for the model-information to get to APIVirtualDevice etc. Most is happening in backend/.../modelSupport/ModelService.scala and it would be nice to have a better structure for this.
One idea is to implement this information with the new Model-curcuit or in a new parallell circuit depending on the Model-Curcuit.
Suggestion of Curcuit-info
Right now it is happening with operationToAbility
This Information is maybe needed
[This issue is in progress]
The text was updated successfully, but these errors were encountered: