Uploaded image for project: 'SAFe Program'
  1. SAFe Program
  2. SP-2624

Further Implementation of the MCCS DAQ-to-File device

Change Owns to Parent OfsSet start and due date...
    XporterXMLWordPrintable

Details

    • Obs Mgt & Controls
    • Hide

      The breaking out of the MCCS DAQ receiver functionality will allow this module to be released on a cadence differing to that of the core of the MCCS software.

      Show
      The breaking out of the MCCS DAQ receiver functionality will allow this module to be released on a cadence differing to that of the core of the MCCS software.
    • Hide

      The MCCS DAQ device is developed to a point it is able to consistently deploy stably and be demonstrated to acquire data from a simulated source. The core MCCS DAQ software is separated out of the main MCCS software code base into its own repository and has the potential to be brought into an independently releasable state.

      Show
      The MCCS DAQ device is developed to a point it is able to consistently deploy stably and be demonstrated to acquire data from a simulated source. The core MCCS DAQ software is separated out of the main MCCS software code base into its own repository and has the potential to be brought into an independently releasable state.
    • 4
    • 4
    • 20
    • 5

    • Sub-system Version REL-224 MCCS v0.10.0

    • Team_MCCS
    • Sprint 4
    • Hide

      The required functionality was determined (MCCS-1007, MCCS-1073). Initial implementation (MCCS-1029) was refactored as its own Tango device MccsDaqReceiver (MCCS-1070). This provided the necessary functionality for our collaboration with Viola (SPO-1965).
      The code base was split off into its own repository (MCCS-1149) and the opportunity taken to do this also for PaSD (MCCS-1151).
      The test suite for Daq was covered by tickets MCCS-1031, MCCS-1094 and MCCS-1093 (BDD testing) and helm charts were added (MCCS-1177) for deployment.
      Deployment at PSI Low established that further configuration options were required (MCCS-1153) following which operation was DaqReceiver was evaluated (an on-going docker issue is causing some difficulty).

      Show
      The required functionality was determined (MCCS-1007, MCCS-1073). Initial implementation (MCCS-1029) was refactored as its own Tango device MccsDaqReceiver (MCCS-1070). This provided the necessary functionality for our collaboration with Viola (SPO-1965). The code base was split off into its own repository (MCCS-1149) and the opportunity taken to do this also for PaSD (MCCS-1151). The test suite for Daq was covered by tickets MCCS-1031, MCCS-1094 and MCCS-1093 (BDD testing) and helm charts were added (MCCS-1177) for deployment. Deployment at PSI Low established that further configuration options were required (MCCS-1153) following which operation was DaqReceiver was evaluated (an on-going docker issue is causing some difficulty).
    • 16.6
    • Stories Completed, Integrated, Solution Intent Updated, Outcomes Reviewed, NFRS met, Demonstrated, Satisfies Acceptance Criteria, Accepted by FO

    • PI22 - UNCOVERED

    • Cross_Team_Code_Review Team_MCCS goal_O4 mccs_software

    Description

      Implement basic data capture (DAQ) to file, creating a new Tango device which uses the DAQ library to establish the necessary connexions. If necessary, limit to single-tile interactions rather than a whole station.

      This is important as it aids demonstration that any MCCS hardware-facing deployment is able to put in place appropriate configuration so as the establish complete signal flow.

      Attachments

        Issue Links

          clones

          Feature - A Feature is a service that fulfills a stakeholder need. Each feature includes a benefit hypothesis and acceptance criteria, and is sized or split as necessary to be delivered by a single Agile Release Train (ART) in a Program Increment (PI). SP-2090 Initial Implementation of the MCCS DAQ-to-File device

          • Must have - Items labelled as "Must have" are critical to the current delivery timebox in order for it to be a success.
          • Done
          is cloned by

          Feature - A Feature is a service that fulfills a stakeholder need. Each feature includes a benefit hypothesis and acceptance criteria, and is sized or split as necessary to be delivered by a single Agile Release Train (ART) in a Program Increment (PI). SP-3029 Further Implementation of the MCCS DAQ-to-File device

          • Should have - Items labelled as "Should have" are important but not necessary for delivery in the current delivery timebox. While "Should have" items can be as important as "Must have", they are often not as time-critical or there may be another way to satisfy the requirement so that it can be held back until a future delivery timebox.
          • Done
          Is delivered by

          Sub-system Version - A version of a sub-system, used in the Release Management and Configuration Management process REL-224 MCCS v0.10.0

          • Discarded
          mentioned in

          Page Loading...

          Page Loading...

          Page Loading...

          Structure

            Activity

              People

                v.mohile Mohile, Vivek
                r.braddock Braddock, Ralph
                Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Feature Progress

                  Story Point Burn-up: (100.00%)

                  Feature Estimate: 4.0

                  IssuesStory Points
                  To Do00.0
                  In Progress   00.0
                  Complete1447.0
                  Total1447.0

                  Dates

                    Created:
                    Updated:
                    Resolved:

                    Structure Helper Panel