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

sort loci in PoleZeroData#1070

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

Merged

Conversation

@murrayrm
Copy link
Member

@murrayrmmurrayrm commentedDec 2, 2024
edited
Loading

This small PR adds the option to sort loci when creating a PoleZeroData object. This is useful if you create a PoleZeroData object in some way other than callingroot_locus_map (which sorts the data ahead of time).

The need for this functionality came up when working through Example 5.17 of FBS2e (bicycle eigenvalue location versus speed), as shown in the following code:

https://github.com/murrayrm/fbs2e-python/blob/main/example-5.17-bicycle_stability.py

(At some point I would like to generalized the root locus capability to allow plotting an eigenvalue locus diagram against any free parameter in a nonlinear system, but that will take more time and effort.)

@coveralls
Copy link

coveralls commentedDec 2, 2024
edited
Loading

Coverage Status

coverage: 94.689% (-0.008%) from 94.697%
when pullingd220068 on murrayrm:pzdata_sort-25Nov2024
into57b5307 on python-control:main.

System name.
sys : StateSpace or TransferFunction
System corresponding to the data.
sort_loci : bool, optional)
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
sort_loci :bool,optional)
sort_loci :bool,optional

Copy link
Member

@slivingstonslivingston left a comment

Choose a reason for hiding this comment

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

There is a small misprint in the docstring. Besides that, this is ready to merge.

Not related to code: the PR description refers to Example 6.8 but links toExample 5.17. This PR is clearly relevant to Example 5.17, so I guess "Example 6.8" is a misprint or perhaps example numbers changed in the book, but I want to bring attention to it in case it indicates that more actions are necessary.

@murrayrmmurrayrm merged commit69efbbe intopython-control:mainDec 2, 2024
12 checks passed
@murrayrmmurrayrm added this to the0.10.2 milestoneFeb 19, 2025
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

@slivingstonslivingstonslivingston approved these changes

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

0.10.2

Development

Successfully merging this pull request may close these issues.

3 participants

@murrayrm@coveralls@slivingston

[8]ページ先頭

©2009-2025 Movatter.jp