[FIX] Fixes handling of volumetric maps for null models #11
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.
A first pass towards being able to generate null maps for volumetric images. The primary issue I'm running into here is that this is computationally...I don't wanna say impossible, but basically impossible. If you're working with 1mm isotropic data in MNI152, by default you've got upwards of 1.8 million voxels. The distance matrix ends up being many terabytes 😬
Will consider ways around this... Potentially thresholding the distance matrix based on a KNN regime, where users supply the desired K as a distance (i.e., "10mm")?