Closed IanHeywood closed 3 months ago
Thanks for reporting @IanHeywood. Seems like and easy fix. Just want to get the tests passing here https://github.com/ratt-ru/pfb-clean/pull/96
This is working for me now except I'm not sure what to put in the fits header for the GaussPars in that case. It doesn't seem to like np.nan or None values. Any suggestions?
Not allowed by the 4.0 standard (not in headers at least). The only place where they are expressly allowed is in the data cube, and then they need to be standard IEEE floating point numbers if the precision is set to 32 or 64. I suggest dropping the keywords - they are not axis keywords and not compulsory keywords.
Indeed, that's what I did in the end thanks @bennahugo. I'm not sure if this is the reason but I am not seeing the beam size when opening these fits files with carta. Will investigate
I'm assuming this might be a fully flagged frequency chunk that's tripping up the cube creation when I use the default
--outputs
. Just asking for-i
works without issue.