bf: fixed ThalamicNuclei segmentation naming #1197
Open
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.
ThalamicNuclei segmentation naming conventions differ depending on the tool used:
If segmented with segmentThalamicNuclei.sh
default for "$thalver" is 'V13' (current version) and for "$analysisID" is 'T1'
If segmented with segment_subregions --cross
default for "$analysisID" is an empty string
If segmented with segment_subregions --long
default for "$analysisID" is an empty string
This fix incorporates these naming conventions. Since "$analysisID" is not taken into account, a change to the error message was made in order to instruct the user to adjust their ThalamicNuclei segmentation naming accordingly, if any "$analysisID" suffix is present.
Testing was performed with segment ThalamicNuclei.sh, segment_subregions --cross and segment_subregions --long.