in the GBT-EDGE pipeline we now use griddata(...,dtype=np.float32) and this indeed produces BITPIX=-32 cubes.
However, we then use postprocess.cleansplit() which then produces cubes with BITPIX=-64.
Perhaps pedantic, but besides wasting space, karma (kpvslice) cannot handle it. I'll obviously check if I can solve it easily from my end, until then it's an issue.
in the GBT-EDGE pipeline we now use griddata(...,dtype=np.float32) and this indeed produces BITPIX=-32 cubes.
However, we then use postprocess.cleansplit() which then produces cubes with BITPIX=-64.
Perhaps pedantic, but besides wasting space, karma (kpvslice) cannot handle it. I'll obviously check if I can solve it easily from my end, until then it's an issue.
Reference: https://github.com/teuben/GBT-EDGE/issues/4