fixel2voxel: New option -number #923
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Option specifies the number of fixels to process per voxel. If calculating some statistic from the fixels, then only up to the largest N fixels will be considered. If splitting the data to form a 4D volume, this option controls the number of fixels per voxel to output, and the data will be padded appropriately. This additionally forms a safety barrier in the dwi2response tournier algorithm, in the rare case where no single-fibre voxels contain a second fixel; by specifying -number 2, every voxel will contain 2 fixel amplitude values.
Contributor
|
👍 I've merged manually. Was slightly awkward since the |
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Alternative solution to #900.
Forgot I did this at one point; figured I'd list it to remind myself to have another look, check my laptop and make sure there weren't any other commits. Also whether
LoopFixelsInVoxelWithMaxshould remain here or move into the headers.