Scaling difference in impulse response compared to scipy.signal #747
-
|
I had some code that I wanted to port from using import numpy as np
import control
import scipy.signal
# random state space matrices
t= np.linspace(0, 10, dtype=float)
ss = control.drss(3, 2, 1)
A, B, C, D = ss.A, ss.B, ss.C, ss.D
dt = t[1]
# compute impulse response with python-control
ss = control.ss(A, B, C, D, dt=dt)
t_control, h_control = control.impulse_response(ss, T=t)
plt.figure()
plt.plot(t_control, h_control[0, 0])
plt.plot(t_control, h_control[1, 0])
# compute impulse response with scipy.signal
ss_scipy = scipy.signal.StateSpace(A, B, C, D, dt=dt)
t_scipy, (h_scipy,) = scipy.signal.dimpulse(ss_scipy, t=t)
plt.figure()
plt.plot(t_scipy, h_scipy[:, 0])
plt.plot(t_scipy, h_scipy[:, 1])
plt.show()Creates these two here.
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
|
python-control computes the response to a unit area impulse, rather than a unit height impulse: #447 |
Beta Was this translation helpful? Give feedback.
-
|
That's a subtle and important detail.Thanks! Would it make sense to document this in impulse_response's docstring or am I just too ignorant of this common concept? |
Beta Was this translation helpful? Give feedback.
-
|
I think it would totally make sense to mention it in the docs. |
Beta Was this translation helpful? Give feedback.
python-control computes the response to a unit area impulse, rather than a unit height impulse: #447