Details
-
Feature
-
Must have
-
Obs Mgt & Controls
-
-
-
4.5
-
1
-
3
-
0.667
-
Team_MCCS
-
Sprint 5
-
-
-
- implementation of revisions recommended in the description
No backdoors as such, but the implemented commands could be used by a notebook to drive pointing delays semi-manually
- demo of resource management in beams
Deferred to PI21
- initial beam is shown to point at Zenith for drift scan (0 geometric delay, but cable delays through offline calibration corrected)
- Deferred to PI21
- further version of beams includes pointing through 'backdoor' where delays can be calculated separately and fed directly to the TPMs
Implemented commands could be used in this way
- update of confluence documentation
Scan and EndScan commands have been implemented. The devise hierarchy is all in place in the deployment charts with revised devise identifiers. Connectivity from the Station and StationBeam devices has been made to the SPS Tango devices, completing the configuration paths and the delay-setting paths. Delay calculation for static / tracked pointing is in place. An updated pointing architecture have been described in Confluence ready for implementation in PI21.
Functional testing is in place for:
- MccsController.Allocate with valid schema
- MccsController.Allocate with invalid schema
- MccsController.Release after allocation
- MccsSubarray.Configure with valid schema
- MccsSubarray.End
- MccsSubarray.Configure with configured system.
It was planned to expand on the PI19 demo but this has been deferred (MCCS-1675) after further pointing implementation.
AAVS3 as-built antenna / station location data are present in the data exported to telescope model preparatory to executing pointed observations.
implementation of revisions recommended in the description No backdoors as such, but the implemented commands could be used by a notebook to drive pointing delays semi-manually demo of resource management in beams Deferred to PI21 initial beam is shown to point at Zenith for drift scan (0 geometric delay, but cable delays through offline calibration corrected) Deferred to PI21 further version of beams includes pointing through 'backdoor' where delays can be calculated separately and fed directly to the TPMs Implemented commands could be used in this way update of confluence documentation Define open issues and alternatives for station pointing Scan and EndScan commands have been implemented. The devise hierarchy is all in place in the deployment charts with revised devise identifiers. Connectivity from the Station and StationBeam devices has been made to the SPS Tango devices, completing the configuration paths and the delay-setting paths. Delay calculation for static / tracked pointing is in place. An updated pointing architecture have been described in Confluence ready for implementation in PI21. Functional testing is in place for: MccsController.Allocate with valid schema MccsController.Allocate with invalid schema MccsController.Release after allocation MccsSubarray.Configure with valid schema MccsSubarray.End MccsSubarray.Configure with configured system. It was planned to expand on the PI19 demo but this has been deferred (MCCS-1675) after further pointing implementation. AAVS3 as-built antenna / station location data are present in the data exported to telescope model preparatory to executing pointed observations. - implementation of revisions recommended in the description
-
20.6
-
Outcomes Reviewed, Accepted by FO
-
-
Team_MCCS mccs_software
Description
As this feature is a Clone, Some of these aspects may have been completed already. The comments on the Outcome of SP-1970 which this Clones should be considered for the part still remaining to be completed.
-----------------------------------------------------------------------------------------------------------
Whilst SP-1718 extended TPM configuration capabilities, further to form and control beams on AAVS (and beyond) we need to finish implementing the linkages between the beam devices and the tiles. We must fill any remaining gaps in resource management (de-allocation?). To implement the Scan command we need to start a PointingJob and connect this to the TPM delay control.
The initial version of the beams will be pointing to the Zenith for drift scan observations (0 geometric delay, but cable delays obtained through offline calibration are corrected for)
After the drift scan is established, to facilitate pointing for AAVS operation (i.e. in the absence of a TM system) we might consider implementing appropriate 'back-door' functionality. For instance, a driving notebook could set beam pointing for a strong source such as the Sun or galactic centre and demo a real observation. This would use the methods in station/point_station.py. The more advanced case would run regular updates to achieve scanning / tracking.
In PI18 it was expedient to sidestep some of the SubarrayBeam allocation/configuration work, leaving some of this functionality in Subarray rather than fulfilling the planned architecture. We will implement SubarrayBeam as intended, so as to abstract beam functionality, removing station-level beam responsibilities from the Subarray device.
