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
Units and connections will be connected to an archetype that defines how the unit or the connection will behave in the Spine Model (what constraints it will use and when). The user should have a nice view on the unit and the archetype showing what the unit will do. It would also be really nice to be able to test the unit directly (run a mini-model as a test). Version 1.x.
The text was updated successfully, but these errors were encountered:
That mini-model testing needs to be thought out carefully. We are not making something explicitly for Spine Model. It could be implemented as a test data store (with short time series, etc. and couple of fast levers to change things) that can be connected to a particular unit for the test. The unit could be picked with e.g. a filter - so it's really the manipulators that should be able to do this. But the Spine Toolbox should allow to drop in these quick test blocks easily in the project interface.
In GitLab by @jkiviluo on May 4, 2018, 22:16
Units and connections will be connected to an archetype that defines how the unit or the connection will behave in the Spine Model (what constraints it will use and when). The user should have a nice view on the unit and the archetype showing what the unit will do. It would also be really nice to be able to test the unit directly (run a mini-model as a test). Version 1.x.
The text was updated successfully, but these errors were encountered: