Open maxnoe opened 5 years ago
Using the current release version, under certain circumstances, pyhessio reads wrong values, and that stochastically.
See for example this failing test on travis: https://travis-ci.org/cta-observatory/ctapipe/jobs/477729111
I could also reproduce this locally, running ctapipe test:
pytest ctapipe/io/tests/test_simteleventsource.py::test_compare_event_hessio_and_simtel
It fails at different points from time to time because pyhessio yields different values.
could this be related to the fact that it also crashes randomly due to memory allocation problems in libhessio?
maybe
Using the current release version, under certain circumstances, pyhessio reads wrong values, and that stochastically.
See for example this failing test on travis: https://travis-ci.org/cta-observatory/ctapipe/jobs/477729111
I could also reproduce this locally, running ctapipe test:
It fails at different points from time to time because pyhessio yields different values.