Details
-
Type:
Bug
-
Status: Done
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: meas_base
-
Labels:
-
Story Points:2
-
Epic Link:
-
Sprint:Measurement-S14-4
-
Team:Data Release Production
Description
testForced.py is currently passing even though it probably should be failing: it's trying to get centroid values from a source which has neither a valid centroid slot or a Footprint with Peaks (I suspect because transforming a footprint might remove the peaks). Prior to DM-976, that would have caused a segfault; on DM-976, I've turned it into an exception, which is then turned into a warning by the measurement framework.
Attachments
Activity
I think I might have, when I modified the default centroid slot for ForcedMeasurementTask. In any case, if you don't see log messages about an exception being raised and squashed when running the test, feel free to close this issue. That was the symptom that caused me to create this issue.
Jim:
I don't see any place in testForced.py where an undefined centroid slot is used.
The setUp routine creates a catalog which transforms the footprint peaks (in the way that we never agreed that the Exposure transform code could do safely). But I don't think the centroid slot is used.
testOnCcd does not seem to use a centroid, nor does testOnSameWcs.
Did you fix this bug previously?