-
Notifications
You must be signed in to change notification settings - Fork 439
Issue with slycot/_wrapper.so #121
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
Comments
I can confirm this error on python3.4 using conda (using ubuntu linux). It works correctly using python3.5 (installed via conda), so appears to be something unique to the python3.4 conda build? |
A bit more info: the problem seems to be in the version of
@TMorville can you give a bit more info on how you installed python-control? Was it via conda, pip or source? I was able to get
and then installing the
This let me use the |
Python is anaconda build, slycot and control was installed with pip. My PATHs are correct and which python yields correct lib. Also I've tried to build control from source as you suggested, but with the same error as I posted above. I've never seen the error related to numpy. |
I did a bit more checking and have reproduced this error in an anaconda build on my mac, using the @TMorville: what OS are you using? We may need to redo the |
@murrayrm I'm on OS X, Sierra 10.12.2. Slycot is 0.2.0 and Control is 0.7.0. Let me know if I can do anything else. |
@TMorville: OK, I have a possible fix but need some help in trying it out. First, you need to uninstall the current
Now re-install slycot using conda:
This command should install Once you have done this, you should be able to Let me know if all of that works. If so, you are good to go and I'll document this fix in the (to be created) troubleshooting section of the user manual. |
@murrayrm implemented as you suggested. Still does not work I'm afraid.
And trying to use
|
Strange. Can you try setting up a clean environment and then doing an install. Here are the commands that I used (and that worked on my machine):
Let me know if that generates the same error. If so, I'll have to figure out what to uninstall from my test environment to recreate the problem. |
The original path of @TMorville Instead of using
|
@murrayrm still no dice. The test env. works fine, but import slycot gives the same error as above, but now just in the test environment.
@slivingston Tried |
This relates to the use of a newer LAPACK, from which dgesv has been deprecated and removed. See pull request number 13 on Slycot |
Since I found this open issue when googling the same error message, it is useful here to note that the conda-forge installation process for control and slycot (see #115) solved this problem for me, presumably because it uses an older version of LAPACK. |
I think this issue is "resolved" from the point of view of python-control, in the sense that it relates to getting a working version of slycot up and running. As @repagh noted above, the issue with lapack as been resolved in Slycot PR #13. |
I have some cryptic issue with slycot:
Using the lqr in Control gives:
And just using doing
import slycot
in python rises:The text was updated successfully, but these errors were encountered: