OM Structure: Multiple Clusters Connected to a Controller
PR #92 introduces the structure for a single cluster to be connected to some "controller" (represented by an IVC component). We will need the ability for the controller to communicate with multiple clusters. This requires the following:
- A basic controller model to be implemented
- Framework update to connect all clusters to the controller
There are a few options here with the components that translate information from the controller to the cluster.
If all clusters have the same cell design and number of stacks, then the components that pre-compute the information needed to connect the controller to the clusters could be specified once (specifically the bounds component and the component that calculates the control command to current coefficients). The other piece of the connector should be done per-cluster.
If clusters have unique designs, then the components that pre-compute the information needed to connect the controller to the clusters should be created per cluster.
OM Structure: Multiple Clusters Connected to a Controller
PR #92 introduces the structure for a single cluster to be connected to some "controller" (represented by an IVC component). We will need the ability for the controller to communicate with multiple clusters. This requires the following:
There are a few options here with the components that translate information from the controller to the cluster.
If all clusters have the same cell design and number of stacks, then the components that pre-compute the information needed to connect the controller to the clusters could be specified once (specifically the bounds component and the component that calculates the control command to current coefficients). The other piece of the connector should be done per-cluster.
If clusters have unique designs, then the components that pre-compute the information needed to connect the controller to the clusters should be created per cluster.