Fix Version/s: None
Team:Data Release Production
The straylight correction for HSC does not clearly follow the same coding structure, correction file, or design as other ISR methods. This should probably be updated to work more like other corrections.
This (and fringe support) can be addressed by adding some kind of optional input support to PipelineTask, indicating that zero instances of an input dataset are allowable.
I believe that will fix the simple fringe case as well. If this becomes just a simple boolean (`isOptional`) in `InputDatasetField`, will this cause conflict with the `scalar=False` option? The end case for fringes is that we would want to support a NULL result (for filter != y), a single entry (for a simple fringe), and a list (for a complex multi-mode fringe).
Good question; I'm starting to think we might want to replace the boolean scalar with some kind of multiple-choice field. It's now feeling a lot like that narg options in Python's argparse module (though without perhaps quite so many options).
I think the base PipelineTask functionality for this was completed on
DM-20205; what remains is specific to IsrTask, and I'll open a new ticket for that.
DM-19393, I think the approach here should look something like this: