Add location of SKA-Low and SKA-Mid telescopes #149
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This pull request adds the location of the SKA-Low and SKA-Mid radio telescopes to
sites.json. I am making this PR on behalf of the SKAO Science Operations team.The location data are taken from the SKAO
ska-ost-array-configpackage. These locations are based on internal SKAO documentation with identifiers: SKA-TEL-SKO-0000422, 513-000001-CIV-1002 and SKA-TEL-INSA-0000537 Revision 11. While the telescopes are still under construction, their array origin is fixed as specified here.I note that SKA telescope deployment follows a staged delivery approach, where the telescopes are made available for science/verification before construction of the full array is completed. Regardless, the array origin for each array does not change across array releases (i.e. the origin is a fixed location, not the centroid of constituent stations within the array).
The pull request also fixes a duplicate
elevationkey in thegbtentry, which resulted in the JSON failing validation.