Loading...

Change Owns to Parent Ofs

Set start and due date...

Xporter

XML

Word

Printable

Details

Type: Feature
Priority: Should have
Fix Version/s: PI14
Component/s: None
Labels:
- mccs_software

ARTs:

Obs Mgt & Controls
Benefit hypothesis:

Hide

The adoption of base_classes v0.13 will allow the MCCS team to make a distinction between FAST and SLOW commands and elect to use a modified functionality to execute 'long running commands' which up until this point in time have failed to complete due to encountering timeouts during execution.

Show
The adoption of base_classes v0.13 will allow the MCCS team to make a distinction between FAST and SLOW commands and elect to use a modified functionality to execute 'long running commands' which up until this point in time have failed to complete due to encountering timeouts during execution.
Acceptance criteria:

Hide

The breaking change to the MCCS code has began and by the end of the PI a sub set of the code base can be demonstrated to have had the base-classes successfully applied.
A plan to continue with the remainder of the base class adoption work has been presented and feeds into the next PI planning in the form of priorities focused features.

Show
The breaking change to the MCCS code has began and by the end of the PI a sub set of the code base can be demonstrated to have had the base-classes successfully applied. A plan to continue with the remainder of the base class adoption work has been presented and feeds into the next PI planning in the form of priorities focused features.
Feature Points:
10
Initial Size:
10
Cost of Delay:
5
WSJF:
0.5
Epic Link:
LFAA Development and MVP Integration
Agile Teams:

Team_MCCS
Due Sprint:
Sprint 3
Story Point Burn-up:
Overdue:
Outcomes:

Hide

Adopting v0.13 of the base classes has been the highest MCCS software priority for PI14. Given that this adoption initiated a breaking change to ska-low-mccs, the team seized the opportunity to continue and intensify the on-boarding of the newest members of the team by full submersion into the MCCS code base. This also presented the opportunity for the team to establish new working relationships and networking following the significant reworking of the team over the recent PIs.

Work has continued into PI15 under feature ~~SP-2586~~ mostly to address some testing-related problems. Release of 0.13-based MCCS has been put back until the last issues are resolved.

As PI14 concludes the key areas of ska-low-mccs have been updated to use v0.13 of the base classes. The updates have been applied via a 'feature branch' in order to manage the transition from v0.11 to v0.13 in a manner where the MR process is controlled, and can be tested and demonstrated as operational so that a confident merge to main is achieved in a single pass. The components of ska-low-mccs that are present in the end of PI14 merge are listed on this Confluence page: https://confluence.skatelescope.org/x/3gxwCg

Show
Adopting v0.13 of the base classes has been the highest MCCS software priority for PI14. Given that this adoption initiated a breaking change to ska-low-mccs, the team seized the opportunity to continue and intensify the on-boarding of the newest members of the team by full submersion into the MCCS code base. This also presented the opportunity for the team to establish new working relationships and networking following the significant reworking of the team over the recent PIs. Work has continued into PI15 under feature SP-2586 mostly to address some testing-related problems. Release of 0.13-based MCCS has been put back until the last issues are resolved. As PI14 concludes the key areas of ska-low-mccs have been updated to use v0.13 of the base classes. The updates have been applied via a 'feature branch' in order to manage the transition from v0.11 to v0.13 in a manner where the MR process is controlled, and can be tested and demonstrated as operational so that a confident merge to main is achieved in a single pass. The components of ska-low-mccs that are present in the end of PI14 merge are listed on this Confluence page: https://confluence.skatelescope.org/x/3gxwCg
Resolved PI.Sprint:
15.6

Feature Checklist:

Stories Completed, Outcomes Reviewed, Satisfies Acceptance Criteria, Accepted by FO

Demos:
- OMC_ART_SystemDemo_3
Requirement Status:

PI24 - UNCOVERED
Labels_MIRO:
mccs_software

Description

Description Statement for PI14
Over the course of several PIs MCCS has been involved with the development of asynchronous approaches to running Tango commands. This has culminated with base classes version 0.13. This provides various new classes to support Fast commands (expected to complete quickly without asynchrony) and Slow commands (slow to complete, so instead use a call-back mechanism). MCCS already has some commands developed with the previous long-running command realization and others yet to be converted. Under this feature we will adopt the 0.13 base classes and adapt our commands to the new system. This should yield further improvements in stability. Because the new realization is both more flexible and easier to use we anticipate further improvements to MCCS.

###OLD DRAFTS###
###New draft###

During the past several PIs support for long-running Tango commands has evolved. In PI12 the Long Running Command implementation was introduced to the SKA base classes. However, a need to improve support for LRCs addressing of already asynchronous interfaces was identified. Work on this proceeded over PI13.

As this better fits the MCCS use case it was most efficient to postpone work on refactoring MCCS long-running commands until the new mechanism had been merged into the base classes. In PI14 we intend finally to proceed with this work.

###Description to be updated###
This feature focuses on implementing LRC using v0.12 base_classes in MCCS. This cannot be done until v0.12 is released and even then MCCS needs to consider when is the appropriate time to undertake this work.

During PI11 the KAROO team investigated how the base_classes could be updated to implement a solution to address the long running commands issue that has been identified in various areas of the SKA software community. It is proposed that in PI12 the solution identified will be implemented and released into the base classes. The MCCS team have engaged, and where invited to contributed to, throughout the process of defining the long running commands solution. The team would like to continue to contribute through the next phase of adoption and testing of the resulting work and be able to provide feedback.

Attachments

Issue Links

depends on

SP-2077 Refactor and release long running command implementation in ska-tango-base

Done

is cloned by

SP-2586 MCCS adoption of ska_base_classes v0.13. post adoption clean up and demo

Done

mentioned in: Page Loading...; Page Loading...; Page Loading...

Structure

Activity

People

Assignee:: Vrcic, Sonja

Reporter:: Braddock, Ralph

Votes:: 0 Vote for this issue

Watchers:: 1 Start watching this issue

Feature Progress

Story Point Burn-up: (100.00%)

Feature Estimate: 10.0

	Issues	Story Points
To Do	0	0.0
In Progress	0	0.0
Complete	23	87.0
Total	23	87.0

Dates

Created:: 07/Dec/21 11:45 AM

Updated:: 15/Apr/24 9:45 AM

Resolved:: 30/Aug/22 9:50 AM