Details
-
Type:
Story
-
Status: Done
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: meas_deblender
-
Labels:
-
Story Points:1
-
Epic Link:
-
Sprint:DRP S19-1
-
Team:Data Release Production
Description
There seems to be a problem with propagating merge_footprint_XXX flags.
E.g. in some DESC processing an object has
{'merge_footprint_i': False, |
'merge_footprint_r': False, |
'merge_footprint_z': False, |
'merge_footprint_y': False, |
'merge_footprint_g': False, |
'merge_footprint_u': False, |
'merge_footprint_sky': False, |
'merge_peak_i': False, |
'merge_peak_r': False, |
'merge_peak_z': False, |
'merge_peak_y': False, |
'merge_peak_g': False, |
'merge_peak_u': True, |
'merge_peak_sky': False} |
note that there is a merge_peak_sky but no merge_footprint_sky. When Jim Bosch looked into this, it seemed as if the problem was generic rather than just for sky objects.