Details
-
Type:
Story
-
Status: To Do
-
Resolution: Unresolved
-
Fix Version/s: None
-
Component/s: ip_isr
-
Labels:
-
Story Points:2
-
Epic Link:
-
Team:Data Release Production
-
Urgent?:No
Description
While debugging some Gen3 CPP pipelines with Meredith Rawls and Colin Slater, 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
- relates to
-
DM-26971 Generate Gen 3 stack produced calibration products for HiTS
- Done