-
Notifications
You must be signed in to change notification settings - Fork 438
Fix margin() documentation to address issue #195 #198
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
3 similar comments
control/margins.py
Outdated
Wcp : float | ||
Phase crossover frequency (corresponding to gain margin) (in rad/sec) | ||
wg: float | ||
Gain margin crossover frequency (where phase crosses -180 degrees) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why not omit "crossover" altogether? The parenthetical remarks are helpful -- I always get these mixed up.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I must admit that the Mathworks explanation is nice here https://www.mathworks.com/help/control/ref/margin.html
I don't agree with the terminology as you now propose.
Gain crossover frequency is where gain is (crosses!) 0dB -- corresponds to gain margin
we can call it Wgco or Wpm
Phase crossover (frequency) is where phase crosses -180 deg -- corresponds to phase margin
We can call it Wpco or wg
Gain margin crossover is simply confusing
Maybe say:
wg: frequency at gain margin (phase crossover point, phase = -180 deg)
wp: frequency at phase margin (gain crossover point, gain = 0dB)
@murrayrm, I added a commit on this PR. I also edited comments for the related stability_margins function. |
No description provided.