Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Robust hinfsyn: add suboptimal synth#1184

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Open
wuschel-brompf wants to merge2 commits intopython-control:main
base:main
Choose a base branch
Loading
fromwuschel-brompf:robust_hinfsyn_add_suboptimal_synth

Conversation

@wuschel-brompf
Copy link

to obtain numerically more robust controllers, usually a slightly suboptimal controller is synthesized after running the first optimization.

@ilayn
Copy link

Note that this relaxation works typically OK with LMI based design since you introduce slackness but for Riccati based solvers there are no guarantees that this improves the conditioning of the controllers. This is typically due to the bilinear nature of the problem. It works OK for smooth-enough problems though.

Copy link
Member

@murrayrmmurrayrm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

Thanks for this contribution,@wuschel-brompf. I had a few things that I think should be updated to be consistent with our coding conventions and to provide a bit more information to the user.

Also, we need a unit test that covers the new code.



defhinfsyn(P,nmeas,ncon):
defhinfsyn(P,nmeas,ncon,gamTry=None):
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

This parameter name doesn't not follow python-control naming conventions. From thedeveloper notes:

Use longer description parameter names that describe the action or role (e.g., trajectory_constraints and print_summary inoptimal.solve_optimal_trajectory.

I suggest something liketarget_gamma for this parameter name.

ncon : int
Number of control inputs (output from controller).
gamTry : int, optional
Target performance level (default = None).
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

Although this is consistent with the current very terse docstring, I think a bit more information is needed, either here or in a Notes section later in the docstring. Something like:

Iftarget_gamma is specified, then a controller with the target value of$\gamma$ will be generated. This is potentially suboptimal, but save computation time.

@coveralls
Copy link

Coverage Status

coverage: 94.717% (-0.02%) from 94.734%
when pulling22b533e on wuschel-brompf:robust_hinfsyn_add_suboptimal_synth
into2435a6a on python-control:main.

Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

@murrayrmmurrayrmmurrayrm requested changes

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@wuschel-brompf@ilayn@coveralls@murrayrm

[8]ページ先頭

©2009-2025 Movatter.jp