Uploaded image for project: 'Data Management'
  1. Data Management
  2. DM-13072

New requirement to explicitly deal with CCOB data

    Details

    • Team:
      Architecture

      Description

      Informally we agree to handle data coming from Camera Calibration Optical Bench (CCOB) as part of early integration. To make this more formal we need to place a requirement on DM, in LSE-61 to be capable of archiving, and performing a meaningful processing on, data from Camera I&T data collection on the CCOB.

        Attachments

          Issue Links

            Activity

            Hide
            tjenness Tim Jenness added a comment -

            This then becomes a requirement for a data detection system to be running. This can't be the normal Archiver because there is no OCS running. We would need to write new code that finds the data in eTraveller as it arrives and triggers the transfer. Kian-Tat Lim may want to comment on the feasibility of doing that.

            Show
            tjenness Tim Jenness added a comment - This then becomes a requirement for a data detection system to be running. This can't be the normal Archiver because there is no OCS running. We would need to write new code that finds the data in eTraveller as it arrives and triggers the transfer. Kian-Tat Lim may want to comment on the feasibility of doing that.
            Hide
            gpdf Gregory Dubois-Felsmann added a comment - - edited

            I think I would avoid using LSE-61 to start specifying performance and implied architectural constraints on behaviors of temporary data transfer mechanisms that should exist only during Construction / Early Integration.  We're not using LSE-61 in any other place (as far as I can recall in the moment) to constrain phasing like that.

            It makes sense to require in LSE-61 that DM be able to ingest, Butlerize, and interpret (i.e., with a suitable obs_* package) Construction-era CCOB data.  Performance and design of the mechanisms that support that now should be documented as part of definition of Early Integration activities, I think - expanding their scope beyond OCS-centric activities to these more data-centric activities.

            Show
            gpdf Gregory Dubois-Felsmann added a comment - - edited I think I would avoid using LSE-61 to start specifying performance and implied architectural constraints on behaviors of temporary data transfer mechanisms that should exist only during Construction / Early Integration.  We're not using LSE-61 in any other place (as far as I can recall in the moment) to constrain phasing like that. It makes sense to require in LSE-61 that DM be able to ingest, Butlerize, and interpret (i.e., with a suitable obs_* package) Construction-era CCOB data.  Performance and design of the mechanisms that support that now should be documented as part of definition of Early Integration activities, I think - expanding their scope beyond OCS-centric activities to these more data-centric activities.
            Hide
            gpdf Gregory Dubois-Felsmann added a comment -

            The performance constraints could also be part of the milestone definition that DM-13073 mentions needs to be developed.  (Though LDM-503 may ultimately be the right place only for the DM parts of this cross-subsystem testing milestone.)

            An LSE-* document defining the early integration milestones would be a good thing...

            Show
            gpdf Gregory Dubois-Felsmann added a comment - The performance constraints could also be part of the milestone definition that DM-13073 mentions needs to be developed.  (Though LDM-503 may ultimately be the right place only for the DM parts of this cross-subsystem testing milestone.) An LSE-* document defining the early integration milestones would be a good thing...
            Hide
            tjenness Tim Jenness added a comment -

            At the CCB meeting today we decided that I will submit this requirement text to the upstream LCR.

            Show
            tjenness Tim Jenness added a comment - At the CCB meeting today we decided that I will submit this requirement text to the upstream LCR.
            Hide
            tjenness Tim Jenness added a comment -

            Suggested requirements text was submitted to LCR on 2018-02-13.

            Show
            tjenness Tim Jenness added a comment - Suggested requirements text was submitted to LCR on 2018-02-13.

              People

              • Assignee:
                tjenness Tim Jenness
                Reporter:
                womullan Wil O'Mullane
                Reviewers:
                Robert Lupton
                Watchers:
                Gregory Dubois-Felsmann, Kian-Tat Lim, Lauren MacArthur, Merlin Fisher-Levine, Ranpal Gill, Robert Lupton, Tim Jenness, Wil O'Mullane
              • Votes:
                0 Vote for this issue
                Watchers:
                8 Start watching this issue

                Dates

                • Due:
                  Created:
                  Updated:
                  Resolved:

                  Summary Panel