Fix Version/s: None
Sprint:Science Pipelines DM-S15-6
Team:Data Release Production
When transitioning meas_extensions_photometryKron to the new measurement framework, aperture correction was omitted pending the completion of
DM-85. It needs to be re-enabled when that epic is complete.
Jim: that is an excellent suggestion. I'll give that a try. It will add some time to the ticket, but is worth doing.
Lauren: do you have time to look at this?
All the work is on meas_extensions_photometryKron tickets/
I was able to add a test for aperture correction to the existing unit test.
It looks like you should squash these two commits:
54d4327 2015-08-14 Add a test that aperture correction works. [Russell Owen]
768f5a7 2015-08-14 starting to add ap corr to unit test [Russell Owen]
Otherwise, I built your branch and ran processCcd.py on HSC data and all looks ok within the context of this ticket (per Jim's comment above).
After squashing, feel free to merge to master.
Thank you for catching the missing squash. I did that and merged to master.
If we do test aperture correction here at all (and I'm not saying we need to, at least on this issue), I think it's sufficient to merely test their application, not their measurement (since the latter requires doing quite a bit more and is tested elsewhere). In other words, we could simply mock up an ApCorrMap with a constant ChebyshevBoundedField and verify that running measurement with aperture correction enabled scales the expected result by the value in the ChebyshevBoundedField.