DM-36885: Ensure cp_pipe only uses a different ISR output when needed

[czwa]

Switch cpSky to operate on postISRCCD datasetType.

[leeskelvin]

From what I can tell, the ISR task for Latiss in cpSky is configured differently to the main Latiss ISR task. When I compare the configs for this cpSky ISR task on this ticket against the default Latiss ISR task, this is my diff:

< config.overscan.fitType='MEDIAN_PER_ROW'
---
> config.overscan.fitType='MEDIAN'
204c204
< config.doCrosstalk=True
---
> config.doCrosstalk=False

Do these ISR task over-rides need to be upstreamed to the main Latiss ISR config over-rides, or can they be removed here?

[leeskelvin]

For reference, Latiss ISR task configs generated using:

pipetask build -t lsst.ip.isr.isrTask.IsrTask --instrument lsst.obs.lsst.Latiss --show config

[czwa]

doCrosstalk=True has been an optimistic hope for a while. I continue to be optimistic that we'll have a calibration soon (there are Camera Team produced ones that are probably sufficient for now).
We probably should switch the overscan method. I'll check for concerns next week.

[leeskelvin]

Having chatted on Slack about this, I think these config differences aren't too problematic. They can be checked after the fact too, so perhaps this is a non-issue. If you're happy with this Chris, then I'm happy too!