danesabo/Obsidian
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

vault backup: 2024-10-16 12:15:44

Browse Source
This commit is contained in:
Dane Sabo 2024-10-16 12:15:44 -04:00
parent a2b27f2cbb
commit 44e0c4825d
3 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
.obsidian/graph.json vendored
View File

@ -67,6 +67,6 @@
"repelStrength": 11.9791666666667,
"linkStrength": 1,
"linkDistance": 148,
"scale": 0.13348388671875,
"scale": 0.200225830078125,
"close": true
}

0
How is robust control validation done?.md → 4 Qualifying Exam/3 Notes/How is robust control validation done?.md
View File

4
4 Qualifying Exam/3 Notes/Robust Control.md
View File

@ -1,6 +1,6 @@
# History
## Where did Robust Control come from?
After the beginnings of modern control and the development of optimal control, John Doyle released a paper in 1978 titled [Guaranteed Margins for LQG regulators](doyleGuaranteedMarginsLQG1978a). This is a less than one page paper that basically gave birth to the robust control field, with a three word abstract: "There are none." I'm working out the kinks in this one ([[Feedback Control Theory]]), but essentially the gaussian part of the LQG is what destroys the guaranteed part of the phase and gain margins. The additional estimator involved can really screw with things.
After the beginnings of modern control and the development of optimal control, John Doyle released a paper in 1978 titled [Guaranteed Margins for LQG regulators](doyleGuaranteedMarginsLQG1978). This is a less than one page paper that basically gave birth to the robust control field, with a three word abstract: "There are none." I'm working out the kinks in this one ([[Feedback Control Theory]]), but essentially the gaussian part of the LQG is what destroys the guaranteed part of the phase and gain margins. The additional estimator involved can really screw with things.
I should add some context: [[4 Qualifying Exam/3 Notes/Feedback Control Theory]].
# What does Robust Control do?
@ -11,6 +11,6 @@ Not particularly a limit but something to look at: there are a ton of papers tha
[[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].
There is some work going on that tries to deal with this @atsumiModifiedBodePlots2012 . These people have made a tool
There is some work going on that tries to deal with this @atsumiModifiedBodePlots2012 . These people have made a tool that can create transfer functions using an upper bound of $\Delta$ and $W$
**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.