Skip to content

Update documentation, processing of root_locus kvect keyword #989

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

Merged

Conversation

murrayrm
Copy link
Member

@murrayrm murrayrm commented Apr 5, 2024

This PR addresses issue #987, which was partially fixed in #988, by consistently using the keyword gains instead of kvect in the root locus commands. In addition, if the kvect keyword is used, a warning is generated indicating that kvect has been deprecated and gains should be used instead.

Also include some minor reformatting of docstrings in rlocus.py.

@coveralls
Copy link

coveralls commented Apr 5, 2024

Coverage Status

coverage: 94.482%. remained the same
when pulling 1b59bd6 on murrayrm:update_rlocus_kvect-04Apr2024
into c638362 on python-control:main.

kvect keyword argument if provided).
(legacy) If the `plot` keyword is given, returns the closed-loop
root locations, arranged such that each row corresponds to a gain
in gains, and the array of gains (ame as gains keyword argument if
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
in gains, and the array of gains (ame as gains keyword argument if
in gains, and the array of gains (same as `gains` keyword argument if

Copy link
Member

@slivingston slivingston left a comment

Choose a reason for hiding this comment

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

This is good to merge, except for the misprint identified by @bnavigator (the misprint existed before this PR, but might as well fix it).

@murrayrm murrayrm merged commit 49f03e7 into python-control:main Apr 6, 2024
23 checks passed
@murrayrm murrayrm added this to the 0.10.1 milestone Jun 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants