Details
-
Feature
-
Must have
-
LOW ART
-
-
-
5
-
5
-
40
-
8
-
Team_MCCS
-
Sprint 4
-
-
-
-
21.6
-
Stories Completed, Integrated, BDD Testing Passes (no errors), Outcomes Reviewed, Satisfies Acceptance Criteria, Accepted by FO
-
-
Team_MCCS mccs_software
Description
Deliver the basic (but verified/validated and documented) allowing control from TMC of MCCS state machine for
- On/off control
- Assigning resources to subarray
- Configure scan
- Execute scan
- The de-allocation of resources from a subarray (IDLE to EMPTY) would be additional but not mandatory.
- Archiving and logging: Verify that the configured tango attributes are stored in the EDA and logs are available.
The basic flow does not necessarily have to allow for all failure scenarios but some basic fault handling would be helpful. Verification of the interface shall require a bdd integration test to run in controlling the system from TMC.
Note: Beam control to be delivered for AAVS3 in SP-3870 expected to be useful for the ITF release and should be tested.
Since the TMC work in PI20 meets the needs of the interface as defined by MCCS, the work in this feature is for MCCS. However Team_Himalaya is expected to support during the integration and testing and a dependency should be created in PI planning.
This feature will release software to fulfil TAIV-791