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

Improve diagnostics and ease-of-use in ISR PipelineTask connections

    XMLWordPrintable

Details

    • 2
    • Data Release Production
    • No

    Description

      While debugging some Gen3 CPP pipelines with mrawls and ctslater, I noticed two small aspects of IsrTask that, if fixed, would save future devs from ever repeating that investigation:

      • We should make sure all of the exceptions raised when a configured prerequisite dataset is not present (e.g. "no bias and you asked for bias correction") report both the data ID and the actual bias dataset type.
      • We should turn all of the config options like "biasDataProductName" into properties that forward to the Connection-injected configuration options like "connections.bias".  These were Gen2 versions of something Gen3 standardizes and generalizes, and there's just no reason to allow them to ever be different.  We may also want to deprecate those properties at the same time,

      Attachments

        Issue Links

          Activity

            There are no comments yet on this issue.

            People

              Unassigned Unassigned
              jbosch Jim Bosch
              Christopher Waters, Jim Bosch, Meredith Rawls
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:

                Jenkins

                  No builds found.