Repository navigation
Replies: 1 comment
|
Is there a specific example where you would see yourself shifting back and forth between scipy.signal and python-control? That might help sort out if there a good way to make the systems more compatible. One approach to making things more compatible would be to create a I think the main challenge with making the packages completely compatible is that python-control adds functionality (eg, signal names, interconnection functions, nonlinear systems) that scipy.signal seems unlikely to need. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
I was exploring the idea to migrate from MATLAB to python for signal processing (scipy.signal) and control (python-control).
It was quite a bummer when I realized each module has its own LTI representation and the two are not compatible.
This seems like a serious issue to me, because now I have to handle / convert the two conflicting LTI representations when I want to use both modules.
FYI: I searched for similar discussions, but I could only dig up this old comment, where the question is raised as a side topic, but not further discussed.
All reactions