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

Write simple tooling to check QuantumGraph expects vs. actual outputs

    XMLWordPrintable

    Details

    • Story Points:
      2
    • Epic Link:
    • Team:
      Data Release Production
    • Urgent?:
      No

      Description

      It'd be hugely useful to be able to get a summary of what produced outputs and what didn't, with a tiny bit of connection to WMS-specific BPS logs and status tools mediated by an ABC.

      It'd be easy to spend a lot of time making this very pretty; I'll try to keep it to the bare minimum, but my brain already has so many ideas...

      And, of course, all of this would work better if we had quanta in the DB. But we don't, and we need something like this now.

        Attachments

          Issue Links

          relates to

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. DM-29761 Improving error handling (and nothing-to-do quanta) in PipelineTask execution

          • In Progress

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. DM-29776 Attempt complete two-QG HSC RC2 run on w16 on one tract

          • Done

            Activity

            Hide
            Permalink
            jbosch Jim Bosch added a comment -

            This has already passed my self-imposed "if I don't get this done by X, it's not worth doing" time box, and it may turn out to be best to never do the simple one and instead just write a better one on top of DM-29761. But I'm also planning to do some post-run analysis to look at memory usage on DM-29776, well before any DM-29761 features land, so I'm now thinking that I'll just write a small (mostly throwaway) Jupyter notebook to do ad-hoc analysis of this sort on that ticket, and plan to at most transfer any code worth keeping to permanent homes after DM-29761.

            Show
            jbosch Jim Bosch added a comment - This has already passed my self-imposed "if I don't get this done by X, it's not worth doing" time box, and it may turn out to be best to never do the simple one and instead just write a better one on top of DM-29761 . But I'm also planning to do some post-run analysis to look at memory usage on DM-29776 , well before any DM-29761 features land, so I'm now thinking that I'll just write a small (mostly throwaway) Jupyter notebook to do ad-hoc analysis of this sort on that ticket, and plan to at most transfer any code worth keeping to permanent homes after DM-29761 .

              People

              Assignee:
              jbosch Jim Bosch
              Reporter:
              jbosch Jim Bosch
              Watchers:
              Jim Bosch
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Jenkins

                  No builds found.