Details
-
Type:
Story
-
Status: Done
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: None
-
Labels:None
-
Story Points:10
-
Epic Link:
-
Sprint:DRP S17-1, DRP S17-2, DRP S17-3, DRP S17-4
-
Team:Data Release Production
Description
Attachments
Issue Links
- is blocked by
-
DM-9028 Process the HSC RC dataset with the latest hscPipe 4.0.5
- Done
- relates to
-
DM-9107 Investigate isotropic footprint growing/dilating behavior: HSC vs. LSST
- Done
-
DM-9108 Investigate distribution of footprint sizes: HSC vs. LSST
- Done
-
DM-9109 Create ellipticity residuals quiver plots
- Done
-
DM-9110 Investigate source of systematic difference of model psf trace radii: HSC vs. LSST
- Done
-
DM-9252 Investigate bimodal distribution of footprint sizes for "stars"
- Done
-
DM-9383 Investigate propagation of visit flags for certain patches in HSC RC processing
- Done
-
DM-9535 Assess whether differences in Brighter-Fatter implementations are contributing to the trace radii differences: LSST vs. HSC
- Done
-
DM-9554 Process HSC "RC" dataset through the LSST stack using HSC's Brighter-Fatter implementation
- Done
-
DM-6817 Compare HSC and LSST processing of RC dataset
- Done
-
DM-6818 Quality check LSST processing of RC dataset
- Done
The issue revealed in
DM-9109and tracked down inDM-9110leads to a very small difference (~0.5% systematic offset between model psf trace radii between HSC and LSST stack). I'm not sure how much its propagated effect could add up to (and I've only looked in detail at this one visit...others could be worse). In order to ensure we are comparing apples with apples, we will need to rerun one of the RC datasets. Given that the newer defaults are meant to be used, I'm not sure if it makes more sense to rerun the RC dataset with the updated HSC stack, or with the "down-dated" LSST stack. Any opinion on this Paul Price?