-
Notifications
You must be signed in to change notification settings - Fork 0
Update the script to SCT v7.2 #27
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
Open
valosekj
wants to merge
15
commits into
main
Choose a base branch
from
bk/udpate_to_sct70
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+151
−29
Open
Changes from all commits
Commits
Show all changes
15 commits
Select commit
Hold shift + click to select a range
0fb8325
Update the script to SCT v7.0
KahinaBch 9e9fabc
Adding aSCOR analysis
KahinaBch c17e3ac
Adapting to longitudinal path name
KahinaBch b2a0205
Adaptation to new folder format having multiple time points
KahinaBch 98046dd
Apply suggestions from code review
KahinaBch 14bf44d
Addying suggestions from code review
KahinaBch a0ba2f0
solve conflict
KahinaBch cb24bda
fix file naming during lesions segmentation for sct7 compatibility
KahinaBch de3b20e
clarify comment for `sct_label_vertebrae -discfile`
valosekj 625da2f
remove unused comment; update exiting comment
valosekj f3ad3bb
remove extra spaces
valosekj 3e65120
update echo
valosekj 694d14c
Move canal seg, lesion seg and aSCOR computation out of the if statem…
valosekj 7d13bab
Move canal seg, lesion seg and aSCOR before compression metric comput…
valosekj 2168566
Improve comments for easier code readability
valosekj File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,7 +1,7 @@ | ||
{ | ||
"path_data" : "/home/GRAMES.POLYMTL.CA/p118175/extrassd1/janvalosek/data/dcm-zurich", | ||
"path_output" : "/home/GRAMES.POLYMTL.CA/p118175/extrassd1/janvalosek/dcm-zurich_2023-05-17_persex", | ||
"script" : "/home/GRAMES.POLYMTL.CA/p118175/code/dcm_metric_normalization/scripts/process_data_dcm-zurich.sh", | ||
"path_data" : "/Users/kahina/NeuroPoly/data/dcm-zurich", | ||
"path_output" : "/Users/kahina/NeuroPoly/results/first_tests_sept25", | ||
"script" : "/Users/kahina/NeuroPoly/scr/dcm-metric-normalization/scripts/process_data_dcm-zurich.sh", | ||
"exclude_list" : ["sub-817811", "sub-834907", "sub-842197", "sub-294305", "sub-796358", "sub-561017", "sub-250791", "sub-895299"], | ||
"jobs" : 32 | ||
"jobs" : 4 | ||
} |
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Migth also be worth testing using totalspineseg directly on the axial image and compare results!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would that mean computing everything twice and comparing each metric obtained?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
comparing getting the vertebral labels from the sagittal image vs getting it using totalspineseg directly on the axial, and doing a QC report comparing the quality of the labeling, is it more clear?