Fix the whitespace formatting of segstats #558
Merged
Conversation
This file contains 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
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.
This PR makes the whitespace patterns of segstats.py "more" identical with mri_segstats.
Both states work with mri_stats2table, but there other external scripts might be more strict in reading the csv portion of files and specifically using different scanf statements which might not match.
Users can still modify the formatting slightly, by adding more "volume_precision" (parameter to segstats.py), which will increase the number of digits after the colon, but by default, this is 1 in FreeSurfer's mri_segstats and thus we also pass --volume_precision 1 in recon-surf.
This PR also has some minor formatting changes in the code, but the key difference is formatting of the statsfile.