You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When we take a look at the attached image, we can observe that in the upper left corner no line/branch is present. Nevertheless with the following code the coordinates list contains the point (0,0) within the pixel coordinates, which for my understanding shouldn't be. I also think that such a behavior is not documented in the docs, although there it says that pixel_coordinates is an array of shape (Nnz + 1, skel.ndim). Is this +1 mentioned there the point (0,0)?
Yes, this is the +1. Indeed if that point was actually part of the skeleton it would appear twice.
The reason is that the pixels in the skeleton are numbered 1..Nnz, and we want to use them to index directly into the coordinates.
Possibly, it's best to produce a number -> index map and then have exactly those coordinates in the coordinates array. scikit-image 0.17 has a new map_array function that could make this very fast. In the meantime, it might be useful to document this behaviour.
I would welcome a pull request to fix these things if you have the bandwidth, otherwise, I'll try to get to it soon. Thanks for reporting!
theo258
added a commit
to theo258/skan
that referenced
this issue
Sep 1, 2020
When we take a look at the attached image, we can observe that in the upper left corner no line/branch is present. Nevertheless with the following code the coordinates list contains the point (0,0) within the pixel coordinates, which for my understanding shouldn't be. I also think that such a behavior is not documented in the docs, although there it says that pixel_coordinates is an array of shape (Nnz + 1, skel.ndim). Is this +1 mentioned there the point (0,0)?
I'm using version
Skan version: 0.8
installed from conda.The text was updated successfully, but these errors were encountered: