I merged the changes to master.
obs_decam
README.md | 10 +-
|
examples/genDefectText.py | 49 ++++++++
|
policy/DecamMapper.paf | 225 ++++++++++++++++++++++++++++++++++-
|
python/lsst/obs/decam/decamMapper.py | 48 +++++++-
|
python/lsst/obs/decam/isr.py | 26 ++++
|
tests/getRaw.py | 2 +-
|
6 files changed, 351 insertions(+), 9 deletions(-)
|
testdata_decam
calib/calibRegistry.sqlite3 | 2 +-
|
calib/fringe/DECam_Master_20131115v1-zG_ci_z_01.fits | 3 +++
|
calib/fringe/DECam_Master_20131115v1-zG_ci_z_13.fits | 3 ---
|
3 files changed, 4 insertions(+), 4 deletions(-)
|
I didn't add a test in meas.algorithms.detection.SourceDetectionTask.setEdgeBits. A new ticket may be filed. As for its use in obs.decam.isr, I added some comments in the code to describe what is going on there. Images were also visually inspected to check it does do what we intend. For example the attacked screenshots
and
were created with isr.numEdgeSuspect=30 and isr.numEdgeSuspect=35, respectively. Yellow is SUSPECT, red (which looks more like orange with my transparency setting) is BAD, and green is INTRP. The yellow mask covers 30 and 30 pixels wide as expected.
I'd say don't worry about a new ticket. I think, since we've added these to most obs packages by now anyway, we can just see how the tickets you mention work out.