2
2
3
3
.. _version-0.10.2 :
4
4
5
- Version 0.10.2 Release Notes
6
- ----------------------------
5
+ Version 0.10.2 Release Notes (current)
6
+ --------------------------------------
7
7
8
8
* Released: date of release
9
9
* `GitHub release page
@@ -59,7 +59,7 @@ The following bugs have been fixed in this release:
59
59
`cplt.lines `.
60
60
61
61
* Processing of the timebase parameter (`dt `) for I/O systems is now
62
- handled uniformly across all I/O system factor functions. This
62
+ handled uniformly across all I/O system factory functions. This
63
63
affected the `zpk ` function, which was defaulting to a discrete time
64
64
system to have timebase None instead of 0.
65
65
@@ -104,15 +104,15 @@ were implemented in this release:
104
104
* User documentation is now divided into a User Guide that provides a
105
105
description of the main functionality of the python-control package,
106
106
along with a Reference Manual describing classes, functions, and
107
- parameter in more detail.
107
+ parameters in more detail.
108
108
109
109
* Signal responses and I/O subsystem specifications can now use signal
110
110
names in addition to indices to get the desired inputs, outputs, and
111
111
states (e.g., `response.outputs['y0', 'y1'] `). This is implemented
112
112
via a new `NamedSignal ` object, which generalizes `numpy.ndarray `.
113
-
113
+
114
114
* `find_operating_point ` (legacy `find_eqpt `): accepts new parameters
115
- `root_method ` and `root_keyword ` to set the root finding algorithm
115
+ `root_method ` and `root_kwargs ` to set the root finding algorithm
116
116
that is used.
117
117
118
118
* `root_locus_map ` now correctly handles the degenerate case of being
@@ -131,7 +131,7 @@ were implemented in this release:
131
131
functions to be given as a means of creating a MIMO transfer
132
132
function (use the new `combine_tf ` function).
133
133
134
- * The `nlsys ` factor function can now create a `NonlinearIOSystem `
134
+ * The `nlsys ` factory function can now create a `NonlinearIOSystem `
135
135
representation of a `StateSpace ` system (passed as the first
136
136
argument to `nlsys `).
137
137
@@ -168,8 +168,9 @@ were implemented in this release:
168
168
* `FrequencyResponseData `: use `~FrequencyResponseData.complex ` to
169
169
access the (squeeze processed) complex frequency response (instead
170
170
of the legacy `response ` property) and
171
- `~FrequencyResponseData.frdata ` to access the 3D frequency response
172
- data array (instead of the legacy `fresp ` attribute).
171
+ `~FrequencyResponseData.frdata <FrequencyResponseData> ` to access
172
+ the 3D frequency response data array (instead of the legacy `fresp `
173
+ attribute).
173
174
174
175
* Time response and optimization function keywords have been
175
176
regularized to allow consistent use of keywords across related
@@ -182,7 +183,7 @@ were implemented in this release:
182
183
- Variables associated with inputs, outputs, states and time use
183
184
those words plus an appropriate modifier: `initial_state `,
184
185
`final_output `, `input_indices `, etc.
185
-
186
+
186
187
- Aliases are used both to maintain backward compatibility and to
187
188
allow shorthand descriptions: e.g., `U `, `Y `, `X0 `. Short form
188
189
aliases are documented in docstrings by listing the parameter as
@@ -207,7 +208,7 @@ generate a warning message when used:
207
208
* `FrequencyResponseData.response `: use
208
209
`FrequencyResponseData.complex ` to return the complex value of the
209
210
frequency response.
210
-
211
+
211
212
* `FrequencyResponseData.fresp `: use `FrequencyResponseData.frdata
212
213
<FrequencyResponseData> ` to access the raw 3D frequency response
213
214
data array.
0 commit comments