Skip to content
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

FITS headers conventions #105

Open
IanHeywood opened this issue Jun 21, 2024 · 2 comments
Open

FITS headers conventions #105

IanHeywood opened this issue Jun 21, 2024 · 2 comments

Comments

@IanHeywood
Copy link

The reference frequency in the FITS headers produced by pfb seem to correspond to the lowest frequency in the data, e.g. for this UHF map:

CRVAL3  =        592376953.125

It's more standard for MFS images to have the central frequency, but if there's a good reason to have the lowest frequency instead it can be worked around.

@landmanbester landmanbester changed the title Reference frequency in FITS header FITS headers conventions Jun 21, 2024
@landmanbester
Copy link
Collaborator

Thanks for pointing this out. I'm not actually sure if my headers strictly adhere to the fits format (since the truth is actually encoded in the dds and fits is mainly for viewing). I set the headers up here

def set_wcs(cell_x, cell_y, nx, ny, radec, freq,

if you spot anything else that needs to change please report it on this issue. I've renamed it to make it a bit more general

@landmanbester
Copy link
Collaborator

Just to note that there was also an issue with crpix2 viz. it was set to ny//2 instead of 1 + ny//2. I wouldn't call this a solved problem but I managed to get the WCS to agree with wsclean by flipping the v coordinate during gridding/degridding and not flipping any axes when writing fits files (and setting crpix2 = 1 + ny//2). This means that images will be upside down if you rerun the current master on tmp datasets using the old convention (the component models should still be fine, I hope)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants