Loading...

Change Owns to Parent Ofs

Set start and due date...

Xporter

XML

Word

Printable

Details

Type: Feature
Priority: Should have
Fix Version/s: PI17
Component/s: LOW MCCS, LOW MCCS SW
Labels:

ARTs:

Obs Mgt & Controls
Acceptance criteria:

Hide

A workshop is held to discuss/plan additional requirements which may be identified for MccsDaqReceiver.

Some extra facilities may be implemented, including the association of metadata with output files. These data may be stored to a database.

Show
A workshop is held to discuss/plan additional requirements which may be identified for MccsDaqReceiver. Some extra facilities may be implemented, including the association of metadata with output files. These data may be stored to a database.
Feature Points:
2
Initial Size:
2
WSJF:
0
Epic Link:
AA0.5 LOW Digital Signal Chain Processing
Agile Teams:

Team_MCCS
Due Sprint:
Sprint 4
Story Point Burn-up:
Overdue:
Outcomes:
Hide

In use the DAQ receiver device revealed a lot of complexities and problems.

Because standard Tango templates do not allow for a listening network port to be opened the receive functionality was split off to a separately-deployed pod.

For communications between the Tango device and the actual receiver a gRPC mechanism was introduced.

This is working under Kubernetes but problems remain when operating under the networking limitations of minikube.

The concept has been discussed extensively within the team and future modifications / additions will be the subject of continued review.

The DAQ receiver artefact has been published, ready for use at hardware-facing deployments.
Show
In use the DAQ receiver device revealed a lot of complexities and problems. Because standard Tango templates do not allow for a listening network port to be opened the receive functionality was split off to a separately-deployed pod. For communications between the Tango device and the actual receiver a gRPC mechanism was introduced. This is working under Kubernetes but problems remain when operating under the networking limitations of minikube. The concept has been discussed extensively within the team and future modifications / additions will be the subject of continued review. The DAQ receiver artefact has been published, ready for use at hardware-facing deployments.
Resolved PI.Sprint:
17.5

Feature Checklist:

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

Demos:
- OMC_ART_SystemDemo_4
Requirement Status:

PI23 - UNCOVERED
Labels_MIRO:
SYSTEM_DEMO_3 Team_MCCS goal_O5 mccs_software
Goals_MIRO:
SPO-2126

Description

~~SP-2624~~ saw the creation of the MccsDaqReceiver device in PI16. We will gather feedback over the course of the next few sprints as this device is used extensively. This will then be assessed and if further requirements are identified they can be planned and implemented. Anticipated extra facilities include:

Add metadata association (and collect into database?)

Attachments

Issue Links

clones

SP-2624 Further Implementation of the MCCS DAQ-to-File device

Done

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

(2 mentioned in)

Structure

Activity

People

Assignee:: Bridger, Alan

Reporter:: Mohile, Vivek

Votes:: 0 Vote for this issue

Watchers:: 2 Start watching this issue

Feature Progress

Story Point Burn-up: (100.00%)

Feature Estimate: 2.0

	Issues	Story Points
To Do	0	0.0
In Progress	0	0.0
Complete	5	13.0
Total	5	13.0

Dates

Created:: 22/Nov/22 9:18 AM

Updated:: 13/Feb/24 2:39 PM

Resolved:: 16/Feb/23 1:59 PM