SDP Pointing Calibration
Pointing calibration must be performed for the MID telescope. This is achieved by observing “pointing”-type scans with the telescope - for example in a 5-point pattern around a pointing calibrator source.
These scans are processed by SDP using the pointing offset pipeline, which fits the beam of each dish to the measured data and returns the offsets (in cross-elevation and elevation) and their uncertainties.
Deployment of the pointing pipeline
The pointing offset calibration pipeline can be deployed either as a stand-alone pipeline or as an SDP processing script alongside the vis-receive script.
These two methods are described in detail in the pointing documentation:
The functionality that is only used when the pipeline is deployed in SDP is described here.
In addition, there is a pointing calibration notebook in the SDP Jupyter notebooks, which demonstrates the pointing offset script deployment using test data.
Configuring the pointing pipeline via the pointing script
Configuration of the pointing offset script is described in the script documentation.
Real-time operation
During real-time operations, the following steps take place:
AssignResources - configure and start a processing block for pointing-offset and vis-receive scripts
Configure - configure a pointing observation, triggering the pointing pipeline to wait for expected number of scans to complete
Scans - execute pointing scans, and start pointing pipeline when expected number of scans have completed
Once complete, the pointing pipeline publishes the resulting offsets for each dish to a Kafka topic. The QueueConnector device monitors the Kafka topic, and saves the offsets to tango attributes. Each dish has its own tango attribute containing the ID of the last scan of the given pointing observation and the offsets, given in degrees for cross-elevation (xel) and elevation (el).
In addition, the output data are written to an HDF5 output file.