-
Notifications
You must be signed in to change notification settings - Fork 68
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
local_max_peak_finder reports erroneous x/y/z data with cropped datasets #1814
Comments
This issue seems to apply to all spot finding algorithms (e.g. FindSpots.BlobDetector and FindSpots.TrackpyLocalMaxPeakFinder). One possible fix is to use The code below can be used to test the issue:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
If
local_max_peak_finder
is called with a cropped dataset, the x/y/z pixel coordinates in thePerImageSliceSpotResults
table are the pixel offsets and not the pixel coordinates.starfish/starfish/core/spots/FindSpots/local_max_peak_finder.py
Lines 252 to 260 in 1e10dae
The text was updated successfully, but these errors were encountered: