I noticed, that the value of the header keyword of the second extension of the example file
has the form, TFORM6 = 'PE(<built-in method max of _VLF object at 0x784ccbf6f9c0>)' which is obviously wrong. Even FV can't open it.
I have no idea, though, how it was produced. I tried to get an ISGRI spectrum in MMODA with default parameters, the keyword there is TFORM6 = 'PE(256) '.
However, as a side note, even this "good" file leads to exception at
|
logger.debug(f'header: {self.header}') |
when running e.g.
test_rmf with
numpy>=2.0 (I'm working on adaptation to it). If you certify that this keyword value is legitime (I didn't find this specific form in
the standart), then this is a bug in astropy, and we need to report an issue there. They fixed a similar issue some time ago.
As a hotfix, I will use repr() in the logging output, it works.
I noticed, that the value of the header keyword of the second extension of the example file
has the form,
TFORM6 = 'PE(<built-in method max of _VLF object at 0x784ccbf6f9c0>)'which is obviously wrong. Even FV can't open it.I have no idea, though, how it was produced. I tried to get an ISGRI spectrum in MMODA with default parameters, the keyword there is
TFORM6 = 'PE(256) '.However, as a side note, even this "good" file leads to exception at
oda_api/oda_api/data_products.py
Line 314 in 239784f
test_rmfwithnumpy>=2.0(I'm working on adaptation to it). If you certify that this keyword value is legitime (I didn't find this specific form in the standart), then this is a bug in astropy, and we need to report an issue there. They fixed a similar issue some time ago.As a hotfix, I will use repr() in the logging output, it works.