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

Make Telescope be an attribute of UVData, UVCal, UVFlag to carry the telescope attributes #1095

Closed
bhazelton opened this issue Dec 2, 2021 · 1 comment · Fixed by #1422
Closed

Comments

@bhazelton
Copy link
Member

Potential things:

  • antenna positions (already on Telescope)
  • antenna system temperatures
  • primary beam pointing errors
  • weather (might be just per site or maybe per antenna)
  • associated UVBeam object (or filename)
  • bulk delays (e.g. cable delays, correlator delays)
  • UVCal object optionally associated

Note: the term telescope is potentially confusing. Karto thinks of telescope as meaning one antenna, I think of it as meaning the array. Maybe we should move to "Array" terminology.

@bhazelton
Copy link
Member Author

Plan is to make the current Telescope object be an attribute on UVData, UVCal, and UVFlag with the existing related attributes on those objects aliased to the matching Telescope attribute.

New info can be added later directly to the Telescope object.

@bhazelton bhazelton changed the title Need more antenna-based tracking. Either a new Antenna object or updates to the Telescope object Make Telescope be an attribute of UVData, UVCal, UVFlag to carry the telescope attributes Dec 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
1 participant