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

Data Management for AAVS3 capture

    XporterXMLWordPrintable

Details

    • Obs Mgt & Controls
    • Hide

      At AAVS3 a large number of observations under varying conditions are expected. It is important to work out how to store and manage the data files for these observations, including identifying all metadata and allow for easy retrieval later.

      Show
      At AAVS3 a large number of observations under varying conditions are expected. It is important to work out how to store and manage the data files for these observations, including identifying all metadata and allow for easy retrieval later.
    • Hide

      Data management strategy document. Skeleton implementation should demo-ed as a stretch.

      Show
      Data management strategy document. Skeleton implementation should demo-ed as a stretch.
    • 2
    • 2
    • 0
    • Team_MCCS
    • Sprint 5
    • Hide

      A meeting with stakeholders was held and the necessary data investigated.
      This includes the metadata already in the SPEAD data stream, which are now being forwarded to the grpc server (MCCS-1586).
      A skuid service was added to the charts, and generated unique IDs are now passed through Configure().
      The metadata received by the DAQ RX are now recorded.
      Functional tests have been described as Gherkin code (but not yet implemented).

      Show
      A meeting with stakeholders was held and the necessary data investigated. This includes the metadata already in the SPEAD data stream, which are now being forwarded to the grpc server (MCCS-1586). A skuid service was added to the charts, and generated unique IDs are now passed through Configure(). The metadata received by the DAQ RX are now recorded. Functional tests have been described as Gherkin code (but not yet implemented).
    • 19.6
    • Stories Completed, Integrated, Outcomes Reviewed, Satisfies Acceptance Criteria, Accepted by FO

    • PI22 - UNCOVERED

    • Team_MCCS mccs_software solution-goal-3
    • SOL-G3

    Description

      The approach to storing captured data files from observations on AAVS3 needs to be finalised. It should be possible to easily retrieve the captured data and identify the parameters for the observation.
      The approach should include what metadata needs to be stored, storage and retrieval mechanism, and possibly look at how to search for specific observations.

      Following review and agreement on the approach, a skeleton implementation could be demoed to show how this would work in practice. This could be a stretch.

       

      Scenario: DAQ receiver data file is tagged to a configuration

      Given the Station is ready to be configured

      When the Station is configured to collect a data stream to a file

      Then the configuration will be tagged with a unique ID recorded to the EDA

      And the same unique ID will be stored to the file's metadata

       

      Attachments

        Issue Links

          mentioned in

          Page Loading...

          Structure

            Activity

              People

                v.mohile Mohile, Vivek
                v.mohile 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

                  IssuesStory Points
                  To Do00.0
                  In Progress   00.0
                  Complete818.0
                  Total818.0

                  Dates

                    Created:
                    Updated:
                    Resolved:

                    Structure Helper Panel