Our decision to enforce object ids of the format: observatory.site.telescope.instrument means passing the parent through the API redundant. While this isn't wrong, it creates the opportunity for API call mistakes.
E.G. NOIRLab has the site "Cerro Pachon" associated with two observatories (CTIO, Gemini). Probably in AEON also.
I rand into a problem because I defined SOAR to be part of "ctio.cp" in one place by "gemini.cp" in another. That produced the error:
"Telescope id must follow the format 'observatory.site.telescope'
I was confused because I DID follow that FORMAT. It was the content that was wrong.
The error message is great for the expected case (not given the dotted string) but causes confusion here.
Our decision to enforce object ids of the format: observatory.site.telescope.instrument means passing the parent through the API redundant. While this isn't wrong, it creates the opportunity for API call mistakes.
E.G. NOIRLab has the site "Cerro Pachon" associated with two observatories (CTIO, Gemini). Probably in AEON also.
I rand into a problem because I defined SOAR to be part of "ctio.cp" in one place by "gemini.cp" in another. That produced the error:
"Telescope id must follow the format 'observatory.site.telescope'
I was confused because I DID follow that FORMAT. It was the content that was wrong.
The error message is great for the expected case (not given the dotted string) but causes confusion here.