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

Antenna and source tables in cal_solutions have repeated values #241

Open
mooneyse opened this issue Jul 12, 2019 · 4 comments
Open

Antenna and source tables in cal_solutions have repeated values #241

mooneyse opened this issue Jul 12, 2019 · 4 comments

Comments

@mooneyse
Copy link

mooneyse commented Jul 12, 2019

This isn't an issue which causes the pipeline to crash so it is low priority. But inspecting the cal_solutions.h5 resulting from Pre-Facet-Calibrator.parset, the antenna table has 4 copies of each antenna and the source table has 4 copies of the pointing. e.g. Here is the source table in the calibrator solset:

image

Since these aren't actually used for anything, it isn't a big deal. Just thought it was worth noting.

Edit: Maybe this is the desired behavior as the antenna and source tables are just appended for each solve (bandpass, clock, faraday, and polalign).

@tikk3r
Copy link

tikk3r commented Jul 13, 2019

It being each effect would make sense, as different soltabs can have different antennas I think (or was it different solsets?), but someone else may know for sure.

@mooneyse
Copy link
Author

Well each tab will have its own antenna axis anyway, so I guess the best thing would be for the antenna table to have a list of all antennas that appear in any of the soltab axes.

@revoltek
Copy link
Collaborator

This is how the h5parm standard works: each solset has 2 tabs, one with antenna and one with directions that are used to lookup coordinates if needed. If an antenna/direction is in one axis, then it should be also in this table. It can happen that then antenna table and an axis have different entries (e.g. if you solve only for a subset of data).

@mooneyse
Copy link
Author

Yup, understood. I just wouldn't expect the antenna table to have multiple entries for each antenna. Initially when I saw the antenna table had ~345 antennas in it, I figured something had gone wrong, but it is just the way they are appended in the pipeline. Ideally there would be a final step in Prefactor to remove duplicates, but it is low priority admittedly.

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

3 participants