vault backup: 2024-10-16 11:56:18
This commit is contained in:
parent
43779e6e33
commit
a2b27f2cbb
@ -5,7 +5,7 @@
|
|||||||
{
|
{
|
||||||
"id": 1,
|
"id": 1,
|
||||||
"name": "My Library",
|
"name": "My Library",
|
||||||
"lastUpdate": 1729090755257
|
"lastUpdate": 1729094040058
|
||||||
}
|
}
|
||||||
],
|
],
|
||||||
"renderCitations": true,
|
"renderCitations": true,
|
||||||
|
|||||||
@ -11,5 +11,6 @@ Not particularly a limit but something to look at: there are a ton of papers tha
|
|||||||
[[farzanRobustControlSynthesis2020]]
|
[[farzanRobustControlSynthesis2020]]
|
||||||
|
|
||||||
**Limitation**: Using automated design tools for robust control of SISO systems has its benefits outweighed by the labor involved in creating the weighting transfer functions [@atsumiModifiedBodePlots2012].
|
**Limitation**: Using automated design tools for robust control of SISO systems has its benefits outweighed by the labor involved in creating the weighting transfer functions [@atsumiModifiedBodePlots2012].
|
||||||
|
There is some work going on that tries to deal with this @atsumiModifiedBodePlots2012 . These people have made a tool
|
||||||
|
|
||||||
**Limitation**: Disk unstructured uncertainty cannot lend itself to creating individual examples of perturbed plants. It is not as simple as picking a plant that is within the robust control disk, because the transfer function that actually gets you there is lost in the abstraction. Or perhaps generalized.
|
**Limitation**: Disk unstructured uncertainty cannot lend itself to creating individual examples of perturbed plants. It is not as simple as picking a plant that is within the robust control disk, because the transfer function that actually gets you there is lost in the abstraction. Or perhaps generalized.
|
||||||
Loading…
x
Reference in New Issue
Block a user