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 to
Using the [lat_int] backend.
1000000 steps took 1.23 seconds
Or 8.12e+05 steps/s
Actual 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 running kmos bench on a model compiled with lat_int, the output looks like
Using the [???] backend.
1000000 steps took 1.24 seconds
Or 8.08e+05 steps/s
Notice the question marks instead of the backend name. This does not happen with the local_smart backend.
Steps to reproduce the issue
- Update numpy to ver 1.13.3
- Pick your favorite otf-enabled model, recompile it with
kmos export -b otf
- Run
kmos bench on the model folder
2a. Pick your favorite "default backend" kmos model, compile it with kmos export -b lat_int
3b. Run kmos bench on the model folder
System 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.
Expected behavior
kmos models should be able to run after being compiled with any of the three backends. In addition running
kmos benchshould 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
otfI get a Segmentation Fault. In addition, when runningkmos benchon a model compiled withlat_int, the output looks likeNotice the question marks instead of the backend name. This does not happen with the
local_smartbackend.Steps to reproduce the issue
kmos export -b otfkmos benchon the model folder2a. Pick your favorite "default backend" kmos model, compile it with
kmos export -b lat_int3b. Run
kmos benchon 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.