State-space Support Design Issue
Loading and Tracking the state of the part/matrices.
Do we have to use SDF? Would that display even work for matrices?
For current matrix parts we generate EPICS channels at build time of the model, however we would like dynamic sizing for the state-space configuration. So it seems like we would have to "compress" data into a known set of channels. Ex. string channel for matrix: [0, 1, 5; 5, 3, 2; 0, 0, 0]
?
Open Questions
- Does EPICS have to be the interface by which we configure the states/configuration of the part?
- Does EPICS have to be the interface by which we read out the state of the state-space parts?
- Do we need to ramp up/down output for reloading of the state-space part?
- Do we need specific control over when a new/reloaded state-space part engages/takes effect?