You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
doc inconsistency about return type of lqr - matrix vs array #418
The plan is to shift away from the use of the np.matrix class at a future point. This functionality is already in place through the use of the use_numpy_matrix function. In version 0.8.3, the np.matrix class is still used for backward compatibility, but you can switch to using arrays through the function call
control.use_numpy_matrix(False)
When we release version 0.9.0, we will switch to have np.ndarray be the default class for all matrices in python-control.
I'll leave this issue open for a bit because I think we generally need to update the documentation to reflect that fact that the return type for functions depends on how you have configured python-control. I've been collecting up documentation updates, so will include those changes in that PR.
Activity
murrayrm commentedon Jun 12, 2020
The plan is to shift away from the use of the
np.matrixclass at a future point. This functionality is already in place through the use of theuse_numpy_matrixfunction. In version 0.8.3, thenp.matrixclass is still used for backward compatibility, but you can switch to using arrays through the function callWhen we release version 0.9.0, we will switch to have
np.ndarraybe the default class for all matrices inpython-control.I'll leave this issue open for a bit because I think we generally need to update the documentation to reflect that fact that the return type for functions depends on how you have configured
python-control. I've been collecting up documentation updates, so will include those changes in that PR.update lqr() return type documentation (addresses python-control#418)
Documentation update (#476)