FIX: ?h.white is actually created in the -pial step #2020
Merged
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.
In this installment of my never-ending series of minor tweaks to
ReconAll
, I've stumbled across the most annoyingly undocumented (outside of source code) change in process in FreeSurfer v6.0, which is that?h.white
are created in the-pial
step, to take advantage of post-aparc refinements. If you happen to kill a process running-pial
after the other outputs are produced but before?h.white
is produced, rerunning will incorrectly skip over this step.I can't guarantee this is the last PR of the series, but I sincerely hope so.
Related: #1991 #1824 #1790