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

jointcal validation framework integration (continued from S17)

    Details

    • Epic Name:
      jointcal validation integration
    • Story Points:
      20
    • WBS:
      02C.03.00
    • Team:
      Alert Production
    • Cycle:
      Spring 2018

      Description

      Jointcal will be the testbed for the new metrics validation system. This epic captures the work on the jointcal side, including integrating jointcal's output into the system, and writing user documentation to allow others to plug their products into validation.

        Attachments

          Issue Links

          Stories in Epic (Custom Issue Matrix)

            Activity

            Hide
            swinbank John Swinbank added a comment -

            To what extent is this work still relevant given the experience with ap_verify and likely future lsst.verify updates? Unless this is something we intend to work on soon, I'm inclined to say we should shut this epic down and open a new one when we're ready to get to grips with instrumenting Jointcal in the future.

            Show
            swinbank John Swinbank added a comment - To what extent is this work still relevant given the experience with ap_verify and likely future lsst.verify updates? Unless this is something we intend to work on soon, I'm inclined to say we should shut this epic down and open a new one when we're ready to get to grips with instrumenting Jointcal in the future.
            Hide
            Parejkoj John Parejko added a comment -

            The intent is to do this work this cycle: for DM-9534, the only thing necessary (I think) is plugging in the new Measurement persistent system; DM-6577 (or something very much like it) is necessary for the jointcal/meas_mosaic comparison; DM-7151 we could probably postpone, as it basically involves hooking jointcal to the end of whatever pipeline processed validation_data_hsc, which can wait.

            Show
            Parejkoj John Parejko added a comment - The intent is to do this work this cycle: for DM-9534 , the only thing necessary (I think) is plugging in the new Measurement persistent system; DM-6577 (or something very much like it) is necessary for the jointcal/meas_mosaic comparison; DM-7151 we could probably postpone, as it basically involves hooking jointcal to the end of whatever pipeline processed validation_data_hsc , which can wait.
            Hide
            Parejkoj John Parejko added a comment -

            The remaining work (DM-6577 and DM-7151) were moved to a SQuaSH epic to implement, otherwise all pieces are in place on my side to output internal jointcal metrics, and process jointcal through validate_drp.

            Show
            Parejkoj John Parejko added a comment - The remaining work ( DM-6577 and DM-7151 ) were moved to a SQuaSH epic to implement, otherwise all pieces are in place on my side to output internal jointcal metrics, and process jointcal through validate_drp.

              People

              • Assignee:
                Parejkoj John Parejko
                Reporter:
                Parejkoj John Parejko
                Watchers:
                Angelo Fausti, Frossie Economou, John Parejko, John Swinbank, Jonathan Sick, Michael Wood-Vasey, Simon Krughoff, Tim Jenness
              • Votes:
                0 Vote for this issue
                Watchers:
                8 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Summary Panel