Maintenance to clip and threshold application arguments #44
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR addresses a naming discrepancy between the
SpotDetection
andPolaris
applications for theclip
andthreshold
parameters. The default value forclip
inSpotDetection
andPolaris
have now been set toTrue
, because this setting gives better spot detection results on a wider range of images.It also removes a line passing a
threshold
argument into theSpotDetection
application inside thePolaris
application. There are two reasons for this: (1) theSpotDetection
application inPolaris
is instantiated withpostprocessing_fn=None
, so thethreshold
argument would not be used, and (2) the default value forthreshold
in theSpotDetection
application prevents an error from being raised about its value.