Repository navigation
docstring improvements #804
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
Changes from 3 commits
3a554b5
11d9350
bf50ded
2311a4d
7acd3fc
16457d7
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -20,6 +20,8 @@ System creation | |
| frd | ||
| rss | ||
| drss | ||
| NonlinearIOSystem | ||
|
|
||
|
|
||
| System interconnections | ||
| ======================= | ||
|
|
@@ -32,9 +34,8 @@ System interconnections | |
| negate | ||
| parallel | ||
| series | ||
| interconnect | ||
|
|
||
| See also the :ref:`iosys-module` module, which can be used to create and | ||
| interconnect nonlinear input/output systems. | ||
|
|
||
| Frequency domain plotting | ||
| ========================= | ||
|
|
@@ -78,8 +79,9 @@ Control system analysis | |
|
|
||
| dcgain | ||
| describing_function | ||
| evalfr | ||
| freqresp | ||
| frequency_response | ||
| TransferFunction.__call__ | ||
| StateSpace.__call__ | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I agree this format is a bit long and cumbersome. Would it make sense to have this show up as something more like
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Ok looked around in numpy and scipy and found Unless anybody else has other ideas about how to refer to this, I would propose to leave it as it is in this PR and plan to update later if somebody figures something out. |
||
| get_input_ff_index | ||
| get_output_fb_index | ||
| ispassive | ||
|
|
@@ -114,10 +116,10 @@ Control system synthesis | |
|
|
||
| acker | ||
| create_statefbk_iosystem | ||
| dlqr | ||
| h2syn | ||
| hinfsyn | ||
| lqr | ||
| dlqr | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I understand why this might go here, but doesn't it make more sense to list alphabetically? Alternatively, we could list this as Note that if you pass a
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. re-alphebetized them in recent commit. |
||
| mixsyn | ||
| place | ||
| rootlocus_pid_designer | ||
|
|
@@ -141,7 +143,6 @@ Nonlinear system support | |
|
|
||
| describing_function | ||
| find_eqpt | ||
| interconnect | ||
| linearize | ||
| input_output_response | ||
| ss2io | ||
|
|
@@ -156,8 +157,8 @@ Stochastic system support | |
|
|
||
| correlation | ||
| create_estimator_iosystem | ||
| dlqe | ||
|
sawyerbfuller marked this conversation as resolved.
Resolved
|
||
| lqe | ||
| dlqe | ||
| white_noise | ||
|
|
||
| .. _utility-and-conversions: | ||
|
|
@@ -193,3 +194,5 @@ Utility functions and conversions | |
| use_fbs_defaults | ||
| use_matlab_defaults | ||
| use_numpy_matrix | ||
|
|
||
|
|
||

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.
Per the numpydoc style guide, the "Other Parameters" section should come after the "Returns" section. When processed using numpydoc (eg, for readthedocs), these parameters will get lumped with all other parameters in a single section. But when they are displayed in an interactive session, they are shown in the order listed (so you see the most common parameters, then what the function returns, then other parameters).
For an example, see
ct.input_output_response. If you look at the docstring in an interactive session (eg,?ct.input_output_responsein iPython) then you see the the documentation forsolve_ivp_method(a rarely used parameter) after the "Returns" section:But if you look at the documentation on readthedocs, you see all of the parameters gathered together:
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.
Thanks. I had noticed that there were a few places where the docstrings in the library listed "additional Parameters" and sphinx was not handling it right. So I took it out. And since making this commit I discovered that sphinx was looking for "other parameters." I'll look around for any more instances of "additional parameters" and change them back to "other parameters"