BUG: Fixed when reopening saved vascular territory segmentation segments name list was incorrectly read. #282
Conversation
This file contains hidden or 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
olevs
approved these changes
Apr 9, 2025
RafaelPalomar
requested changes
Apr 9, 2025
…nts name list was incorrectly read.
RuoyanMeng
force-pushed
the
feature/VascularSegmentsCalculation-bug-fix
branch
from
2dd98ca to
cab28f7
Compare
RafaelPalomar
approved these changes
Apr 22, 2025
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 function updateVascTerrList intends to fetch all the segments' names. However, in the code, it reads segmentID which is different from the segment Name leading to the unsuccessful recovery of vascular territory segmentation info.