Loading...

Change Owns to Parent Ofs

Set start and due date...

Xporter

XML

Word

Printable

Details

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

ARTs:

Obs Mgt & Controls
Feature Points:
2
Initial Size:
2
Cost of Delay:
20
WSJF:
10
Epic Link:
AA0.5 LOW Digital Signal Chain Processing
Agile Teams:

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

Hide

An implementation was made of a mechanism to fetch semi-static data from the telescope model repository (MCCS-957). Because of some issues with the hosted data a local JSON was used. A path to switching to a Web (fastAPI) / git client realization has been identified. Configuration to subservient devices was demonstrated (MCCS-958).

The implemented solution was presented at System Demo 17.3 (MCCS-1274) and initiated some discussions on an architectural level, the focus being on the flat vs hierarchy 'debate' which the architecture team will discuss further. References were also being made to ADR9 with respect to naming conventions.

Show
An implementation was made of a mechanism to fetch semi-static data from the telescope model repository (MCCS-957). Because of some issues with the hosted data a local JSON was used. A path to switching to a Web (fastAPI) / git client realization has been identified. Configuration to subservient devices was demonstrated (MCCS-958). The implemented solution was presented at System Demo 17.3 (MCCS-1274) and initiated some discussions on an architectural level, the focus being on the flat vs hierarchy 'debate' which the architecture team will discuss further. References were also being made to ADR9 with respect to naming conventions.
Resolved PI.Sprint:
17.3

Feature Checklist:

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

Demos:
- OMC_ART_SystemDemo_2
Requirement Status:

PI24 - UNCOVERED
Labels_MIRO:
SYSTEM_DEMO_2 SYSTEM_DEMO_3 Team_MCCS goal_O5 mccs_software
Goals_MIRO:
SPO-2126

Description

Various configuration data have been stored in the telescope model repository. We now need to implement the client-side code to read these into MCCS devices, as required. This will use FastAPI.

Alternatively we could temporarily use another mechanism if simpler. This must be decided first.

The result will be that the required station / antenna location data and the static delays will be available to MCCS devices.

If other data will be required for initial AAVS deployment this must be added to the telescope model.

Attachments

Issue Links

clones

SP-1720 Configuration Scheme (locations, setpoints, etc)

Done

is required by

SP-1399 Configuration Input mechanism and parameter archiving implementation

Analyzing

relates to

SP-2369 Telescope model (instrument configuration) service improvements

Done

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

(8 mentioned in)

Structure

Activity

People

Assignee:: Bridger, Alan

Reporter:: Mohile, Vivek

Votes:: 0 Vote for this issue

Watchers:: 1 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	6	15.0
Total	6	15.0

Dates

Created:: 10/May/22 10:56 AM

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

Resolved:: 20/Jan/23 1:34 PM

CLONE - LOW Telescope Configuration Scheme (locations, setpoints, etc)