At present the command flows from the upper levels of MCCS down to the hardware are mostly unimplemented. As we will soon need some degree of control and monitoring (for demonstrations during this PI and actual deployed field operations during PI13) it is important that we:
Assess what are the gaps
Make a plan in respect of filling the gaps
Start implementing code to fill some of these gaps (particularly in support of PI12 demos).
There are several control flows to consider, for example:
Scan, for example, receives a JSON string specifying configuration parameters for a multiplicity of subarray beams. Currently this does nothing, but we will need to to slice out the parameters for each subarray beam, passing each of them through a Tango command interface to the corresponding SubarrayBeam device. In turn, each of these will convey configuration information to apply to the contributing station beams, which must therefore be passed down to each corresponding StationBeam device. In turn these affect the configuration of the stations touched by each beam, so a StationBeam -> Station and a Station -> Tile configuration interface is needed.
Implementing any of these, or similarly for other command flows, would be a useful step towards the final goal.
So, having conducted an audit of the required additions we will prioritize them and make an implementation plan.
If we can choose implementation work that would lend itself to demonstration of command flow using a Taranta dashboard that would be immediately applicable to a PI12 MCCS demo. Ideally this would demonstrate flow to hardware, but flow short of this would still be very useful. We aim, in particular, to demonstrate the effectiveness of the long-running command implementation for Tile initialization. This work is likely related, but may simply refer to On/Off commands, for example, rather than Configure.
It should be noted that further work on resource management (MCCS-403, MCCS-405) will be required before some of this work can be completed.
Some work on this feature has been accomplished but significant tickets remain to be rolled over to PI13.
The team intends to workshop how to divide the tickets into essential and deferrable and transfer these to new features.
However, the stated objective of this feature - developing a plan, is formed from the identified teickets and this should be able to be documented & closed.
DEvelopment of detailed implementation and deployment plans follows from this.
The focused tickets to facilitate the deployment on AAVS will be contained in SP-2073.
Feature
Must have
