Details
-
Type:
Improvement
-
Status: Done
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: meas_algorithms
-
Labels:
-
Story Points:1
-
Epic Link:
-
Sprint:AP S19-6
-
Team:Alert Production
Description
As part of our weekly brown bag discussion, we did a deep dive into SourceDetectionTask and noticed a number of confusing or misleading docstrings. Here are the notes I took during the brown bag. I'll try to translate these into cleanups shortly, so I don't forget:
DetectionConfig: threshold, thresholdValue
DetectionTask:
detectFootprints: doSmooth & sigma
convolveImage: under what circumstances would you not want `doSmooth==True`?
Better document relationship between reEstimateBackground and thresholdParity? - `applyThreshold` has a fun pair of `if`s, which might then be removed in `clearUnwantedResults`remove `makeSourceCatalog = run
Ian Sullivan: do you mind reviewing this small doc cleanup?
I think I got everything except the "relationship between reEstimateBackground and thresholdParity" (because I didn't know what to say about it) and "remove `makeSourceCatalog = run`" (because it turns out there's a lot of uses of `detection.makeSourceCatalog()` across a variety of packages. Which we should definitely clean up, but it might be worth waiting for gen3 butler to do that?).