Location:On this issue
Edit: I'm trying to make it more clear what I consider in scope for the "base ISR."
A milestone for this cycle is to deliver ISR to correct for all expected effects excluding those that involve pixel boundary distortions: brighter fatter, tree rings, edge rolloff, etc. The rationale is that we are still learning about the more subtle effects, but we need a basic ISR that will allow processing all data up to current levels. Below I outline three categories of effects.
1. Effects in scope for "Base ISR" – I have put the things in bold that I think we need to spend some effort on.
2. Effects that part of ISR, but out of scope for "Base ISR"
3. Effects that are not part of ISR
Effects in scope for "Base ISR"
- Non-linearity correction
- Intra-chip cross-talk correction
- Basic defect and saturation interpolation
- Dark current correction
- Full frame bias correction
- Overscan correction
- Illumination correction
- Amp assembly
- Fringe correction
Effects in ISR, but out of scope for "Base ISR"
- Edge and midline rolloff
- Pixel response non-uniformity
- Hysteresis effects from bright stars
- Charge transfer efficiency corrections
- Inter-chip crosstalk
- Advance defect and saturation interpolation (Gaussian processes?)
Aspects that are out of scope for ISR
- Cosmic ray mitigation
- Persistence – My hope is this is handled by a higher level logging/orchestration framework
- QA – We will need to instrument our tasks, but I think that's a different effort
- is triggering
DM-3878 Implement all ISR corrections for LSST
Did this decision trigger any work? There are no tickets listed on this RFC as resulting from the adoption.
I'll reiterate my comment from last April. Is there any work associated with this RFC?
Thanks to all for the comments. I've tried to tidy things up a bit. If there are no more comments by Monday, I'll mark this as adopted.