Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bf: fixed ThalamicNuclei segmentation naming #1197

Open
wants to merge 1 commit into
base: dev
Choose a base branch
from

Conversation

andreaboscutti
Copy link

@andreaboscutti andreaboscutti commented Apr 3, 2024

ThalamicNuclei segmentation naming conventions differ depending on the tool used:

If segmented with segmentThalamicNuclei.sh

  • ThalamicNuclei."$thalver"."$analysisID".mgz
    default for "$thalver" is 'V13' (current version) and for "$analysisID" is 'T1'

If segmented with segment_subregions --cross

  • ThalamicNuclei."$analysisID".FSvoxelSpace.mgz
    default for "$analysisID" is an empty string

If segmented with segment_subregions --long

  • ThalamicNuclei.long"$analysisID".FSvoxelSpace.mgz
    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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant