vault backup: 2024-11-22 14:38:27
This commit is contained in:
parent
533cc4f5c2
commit
5d57465079
@ -2,6 +2,17 @@ Ideas taken from https://services.anu.edu.au/files/development_opportunity/Resea
|
|||||||
|
|
||||||
# Title / Topic
|
# Title / Topic
|
||||||
# Research Problem (Justification)
|
# Research Problem (Justification)
|
||||||
|
- Why does robust control exist
|
||||||
|
- air conditioning example - but what if the plant is different? What is buddy leaves a window open
|
||||||
|
- We can examine whether or not our controller (the ac unit) can handle the perturbed plant
|
||||||
|
- We can know how open the window is before we have problems
|
||||||
|
- We can guarantee this for this controller design and designed laws
|
||||||
|
- So if we do this can be sure when we build the unit that this is how it will perform?
|
||||||
|
- Well if it's controlled with a microcontroller or other code based solution, no.
|
||||||
|
- The abstraction between the design and the finished controller destroys the guarantee
|
||||||
|
- Things can happen in implementation that make the controller built not true to design
|
||||||
|
- As a result, we need to reverify robustness on built controllers
|
||||||
|
- This exists for structured perturbations. We
|
||||||
# Gap In The Literature
|
# Gap In The Literature
|
||||||
# Goals and Outcomes
|
# Goals and Outcomes
|
||||||
# Research Methodology
|
# Research Methodology
|
||||||
|
|||||||
Loading…
x
Reference in New Issue
Block a user