Details
-
Feature
-
Medium
-
Obs Mgt & Controls
-
2
-
2
-
0
-
REL-1705 TMC Mid Support Global Pointing Model and generic pattern handling
-
Team_HIMALAYA
-
Sprint 5
-
-
-
-
OMC_ART_SystemDemo_5 Team_HIMALAYA Team_SAHYADRI
Description
Exact content to be confirmed as PI23 concludes.
- Implement a TMC Central Node command that can be used to update Global Pointing Model for a particular dish or set of dishes. The command takes as input the Dish ID, Observing Band and the file name and version. Global Pointing Model will be stored in a file and accessible via the Telescope Model. The structure of the directory and the file name is TM in PI24. Each file contains Global Pointing Model parameters for a single dish and a single frequency band. TMC takes as an input file name, obtains the file from the Telescope Model and passes the content of the file to DISH.LMC.
- TBD is this need at the Central Node level ? TMC should enable read access to the currently used Global Pointing Model (stored in the Dish Structure Controller). This would require TMC to obtain the GPM parameters from a dish or set of dishes and make then available to a client. May be implemented as a command or an attribute?
- Health: TMC should be able to verify that dishes are using the GPM as expected - this would require TMC to obtain GPM parameters from a dish and compare that with the GPM parameters in the latest commanded GPM file. This might be performed periodically and on request. It may be a good idea to perform this at subarray level, as one of the parameters that contribute to subarray health.
- Integrate and demonstrate via Pairwise testing the success of the PI23 implementation against a REAL Dish LMC once the required development on the Dish LMC side is complete.
- In PI23 the command is implemented by the Dish Leaf Node. (Which means that the Jupyter Notebook used to test this Capability in PI23 will have to communicate with the Dish leaf Node directly... Adam.Avison can help with the Notebook stuff)