Skip to content

Newer numpy (f2py?) produces strange errors #62

@jmlorenzi

Description

@jmlorenzi

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

  1. Update numpy to ver 1.13.3
  2. Pick your favorite otf-enabled model, recompile it with kmos export -b otf
  3. 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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions