-
Notifications
You must be signed in to change notification settings - Fork 35
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
Newer numpy (f2py?) produces strange errors #62
Comments
I was able to reproduce this issue. However both I used |
Hi Michael, Thanks a lot for reproducing this. Yes, the SegFault seems to occur as soon as you try to import |
Hi Juan, The details are displayed as follows.
|
Expected behavior
kmos models should be able to run after being compiled with any of the three backends. In addition running
kmos bench
should return output similar toActual behavior
When using numpy 1.13.3, models compile with no apparent errors, however when trying to run a model compiled with
otf
I get a Segmentation Fault. In addition, when runningkmos bench
on a model compiled withlat_int
, the output looks likeNotice the question marks instead of the backend name. This does not happen with the
local_smart
backend.Steps to reproduce the issue
kmos export -b otf
kmos bench
on the model folder2a. Pick your favorite "default backend" kmos model, compile it with
kmos export -b lat_int
3b. Run
kmos bench
on the model folderSystem information
kmos version: 0.3.21
Linux Debian Jessie
Downgrading to numpy 1.8.2 solves the issue. Before I investigate this, it would be nice is somebody could try to reproduce this issue, to make sure is not something wrong with my installation.
The text was updated successfully, but these errors were encountered: