-
Notifications
You must be signed in to change notification settings - Fork 4
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
Beam FITS header & description #314
Comments
Think the most concise header formulation is here:
https://github.com/ratt-ru/eidos/blob/a47fa43d78a814a8d0ea31535f0ebd6433812f3d/eidos/util.py#L78-L107
…On Tue, Nov 14, 2023 at 1:02 PM Joshua George Albert < ***@***.***> wrote:
@JSKenyon <https://github.com/JSKenyon> Could you post the header of a
valid beam model fits? Also, any other constraints it needs to satisfy
would be great.
—
Reply to this email directly, view it on GitHub
<#314>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB4RE6U3SZ2VKRMU5TDPMUDYENFTHAVCNFSM6AAAAAA7KTMFR2VHI2DSMVQWIX3LMV43ASLTON2WKOZRHE4TENJRGM4TENI>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
--
--
Benjamin Hugo
|
You can also look at the very minimal beams used in the tests. |
Thanks for the replies. I notice some wierd things with the test beams:
|
I must confess that I am no expert when it comes to the beams - QuartiCal itself doesn't really use them bar feeding them into the underlying predict (which is implemented in codex-africanus). @sjperkins may have a better idea of precisely what will and won't work. The documentation for the beam term is here. Note that the application of the beam in the predict is known to be a bit of a bottleneck at present. Tagging @landmanbester in case he has better intuition about what we should be doing. |
IIRC it's in DEG because it's sampled in the ALT-AZ coordinate system, rather the LM coordinate system. @bennahugo @o-smirnov can you confirm? I recall we had a long discussion about this a year or two back. NAXIS = 3, so I think the CTYPE4 etc. are ignored. Separate FITS cubes are maintained per correlation/stokes parameter. The FREQ axis can be irregularly spaced and the GFREQn coordinates establish the centre point frequency of the associated voxel. This is a custom modification to the FITS schema introduced by @o-smirnov for use in MeqTrees I believe. |
Ah ok, makes sense then! |
@JSKenyon Could you post the header of a valid beam model fits? Also, any other constraints it needs to satisfy would be great.
The text was updated successfully, but these errors were encountered: