Details
-
Enabler
-
Not Assigned
-
None
-
Obs Mgt & Controls
-
-
-
3
-
3
-
6
-
Team_NCRA
-
Sprint 3
-
-
-
-
10.3
-
Stories Completed, Integrated, Solution Intent Updated, BDD Testing Passes (no errors), Outcomes Reviewed, NFRS met, Demonstrated, Satisfies Acceptance Criteria, Accepted by FO
-
-
Cross_Team_Code_Review Team_NCRA
-
SPO-863
Description
- The feature extends the work done in PI#9 to refactor TMC nodes and achieve better separation between application logic and Tango implementation. The work includes the implementation of additional APIs in the Tango interface layer. This facilitates to get/set the device attributes values in an easier way and also provide more options while subscribing to the events of other devices.
- TMC should make use of the new version of the Tango interface layer.
- Develop a sample code that consumes the APIs provided by Tango interface layer.
- Documentation:
- The documentation of the Tango interface layer should also be improved. Providing a sample code that specifies how the APIs of the Tango interface layer can be utilized to develop SKA applications will be useful. Also, consider providing a sample that focuses on utilizing the APIs in non-tango applications.
- Verify that the alarms are raised by tmalarmhandler based on changes in the attributes of tmc devices. This is to ensure that the implementation of the Tango interface layer has not impacted the alarm handling.
- MCCS and OET code has some implementation for abstracting Tango APIs. Some discussions and exploration can be done to check if the work of these teams can be consolidated in a single codebase/library so that code is not duplicated.
Attachments
Issue Links
- supporting
-
SP-1687 Refactor Test Cases for TMC code refactoring
- Discarded
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
- mentioned on