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
Copy file name to clipboardExpand all lines: docs/src/batch_linearization.md
+2-4Lines changed: 2 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -226,13 +226,11 @@ using Test
226
226
227
227
However, if we only open at `y` we get controller linearizations that _still contain the closed loop through the scheduling connection_`v`. We can verify this by looking at what variables are present in the input-output map
notice how the state of the plant is included in the controller, this is an indication that we didn't fully isolate the controller during the linearizaiton. If we do the same thing for the controller with the loop opened at `u`, we see that the state of the plant is not included in the controller:
233
232
```@example BATCHLIN
234
-
Cu = named_ss(controllersu[end], x=Symbol.(unknowns(ssu)))
235
-
sminreal(Cu).x
233
+
sminreal(controllersu[end]).x
236
234
```
237
235
The call to `sminreal` is important here, it removes the states that are not needed to represent the input-output map of the system. The state of the full model, including the plant state, is present in the linearization before this call.
0 commit comments