Details
-
Type:
Bug
-
Status: Done
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: obs_decam
-
Labels:
-
Story Points:0.5
-
Epic Link:
-
Sprint:AP F18-4
-
Team:Alert Production
Description
The dataset template calexp_camera is required to use visualizeVisit.py in pipe_drivers. This ticket is to add an appropriate template for obs_decam.
Attachments
Activity
Looks fine.
There's nothing that will propagate the calexp WCS — the WCS for the various CCDs will be slightly discontinuous. No doubt you can smooth over it, but I don't believe anyone has taken the trouble. ds9 -mosaicwcs /path/to/*.fits may help, though.
Paul Price
added a comment - Looks fine.
There's nothing that will propagate the calexp WCS — the WCS for the various CCDs will be slightly discontinuous. No doubt you can smooth over it, but I don't believe anyone has taken the trouble. ds9 -mosaicwcs /path/to/*.fits may help, though. P.S. The alternative to smoothing over the WCS is to resample the pixels via warping. But our warping code doesn't handle large binning factors well.
Paul Price
added a comment - P.S. The alternative to smoothing over the WCS is to resample the pixels via warping. But our warping code doesn't handle large binning factors well. OK, thanks, I thought that would be your likely response. For some reason, ds9's mosaic seems to show very wrong astrometry yet the matcher is performing fine (and indeed, visualizeVisit shows sources consistently in the same place on the camera, visit after visit, as expected).
Would you be willing to review this small change, Paul Price?
It came about because I wanted to make an image of an entire focal plane to visually inspect the results of processCcd. What I would really like, however, is something similar to visualizeVisit that propagates the calexps' WCS (do you have any code for that, by chance...?)
At any rate, this ticket simply adds a template to the obs_decam mapper for the calexp_camera dataset type which is created by visualizeVisit.