Skip to content

5ttcheck: Alter PVF check#1915

Merged
Lestropie merged 3 commits intodevfrom
5ttcheck_test_value_range
Jan 28, 2020
Merged

5ttcheck: Alter PVF check#1915
Lestropie merged 3 commits intodevfrom
5ttcheck_test_value_range

Conversation

@Lestropie
Copy link
Member

Enhancement of #1909.

When voxels contain a partial volume fraction that does not lie within the range [0.0, 1.0], do not immediately throw an Exception. Instead, include those voxels in the output mask image (if requested), report the number of voxels with such an issue, and only then throw the Exception.
Also rename command-line option "-mask" to "-voxels", since "-mask" typically refers to an input, whereas dwi2response sets the precedent for -voxels.
@Lestropie Lestropie self-assigned this Jan 27, 2020
Left over from experimenting when looking for issues with a specific dataset.
@Lestropie Lestropie merged commit d51ce3e into dev Jan 28, 2020
@Lestropie Lestropie deleted the 5ttcheck_test_value_range branch January 28, 2020 01:15
Lestropie added a commit that referenced this pull request Jan 28, 2020
Due to #1909 and #1915, 5ttcheck will not throw an Exception if there are image values that do not lie within the [0.0, 1.0] range. This includes the current version of test data. Rather than correspondingly causing dwi2response msmt_5tt to fail, instead catch the run.MRtrixCmdError, and print the message to the terminal at warning level as previously.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant