We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
See https://arxiv.org/pdf/2106.03503
@mattcieslak told me about these transforms that can apparently calculate a map of distances from an ROI very rapidly (e.g., using implementations in simpleitk, ANTS, but also implemented in scipy: https://docs.scipy.org/doc/scipy/reference/generated/scipy.ndimage.distance_transform_edt.html#scipy.ndimage.distance_transform_edt). My thinking is that if this really is very fast, it can be used to calculate this transform once upfront for each of our waypoint/endpoint ROI and potentially would make calculations of distances to streamlines more efficient.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
See https://arxiv.org/pdf/2106.03503
@mattcieslak told me about these transforms that can apparently calculate a map of distances from an ROI very rapidly (e.g., using implementations in simpleitk, ANTS, but also implemented in scipy: https://docs.scipy.org/doc/scipy/reference/generated/scipy.ndimage.distance_transform_edt.html#scipy.ndimage.distance_transform_edt). My thinking is that if this really is very fast, it can be used to calculate this transform once upfront for each of our waypoint/endpoint ROI and potentially would make calculations of distances to streamlines more efficient.
The text was updated successfully, but these errors were encountered: