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
non-critical: missing zero-initialisation of FstatResults #11
Comments
Simple hack-ish steps to reproduce:
==>
|
This looks like an upstream problem with the SWIG bindings not vetoing access to "illegal" fields of the results structure. I've contacted Karl for it. In the meantime, this poses no practical problems for PyFstat at all unless one deliberately hacks out the FSTATQ_2F bit from the base ComputeFstat class as done above. I only noticed this because of an earlier bug where the atoms bit for the transient case was overwriting this bit instead of being added to it, which I've long since fixed. So this is really just a paranoia-level investigation. |
Will be solved upstream in lalsuite, thanks to quick work from Karl: https://git.ligo.org/lscsoft/lalsuite/-/merge_requests/1258 |
This has been solved by @kwwette in the LALSuite SWIG modules, thanks! https://git.ligo.org/lscsoft/lalsuite/-/commit/c11cd5a0c64de48bc3aced217aa8508a4785eb46 |
from https://gitlab.aei.uni-hannover.de/GregAshton/PyFstat/issues/19 (20191105):
The text was updated successfully, but these errors were encountered: