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

TEMPO-format observatories must have a TEMPO site code to find clock corrections #1241

Closed
aarchiba opened this issue May 11, 2022 · 0 comments · Fixed by #1239
Closed

TEMPO-format observatories must have a TEMPO site code to find clock corrections #1241

aarchiba opened this issue May 11, 2022 · 0 comments · Fixed by #1239

Comments

@aarchiba
Copy link
Contributor

The way TEMPO stores its clock corrections is all in one big file (possibly split via INCLUDE statements) with each clock correction labelled with the site code. Currently if PINT is given an observatory without a site code it just loads all the clock corrections for every telescope and reports no error, but obviously gives a totally bogus set of clock corrections. The problem is that tempo site codes are used as aliases, so you can't afford to have, say, the GBT-old-position site use the same site code as the GBT-current-position, but without that how do you find a set of TEMPO-format clock corrections for it?

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

Successfully merging a pull request may close this issue.

1 participant