Optimization for long_fastsurfer, one view only for skull stripping #659
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 PR optimizes fastsurfer so that the skull stripping needed for longitudinal registration only uses one fastsurfer view.
Currently, run_prediction cannot be configured to only run on one view. But if it could, long_prepare_template would likely only need one view to compute the brainmask. Maybe we can even deactivate aseg and asegdkt output to save up time and disk space. This would then speed up this initial step.
Step 1: Modify run_prediction so the user is able to "deselect" views that should not be included. Syntax (example)
--cfg_ax none
Step 2 (optional) Modify run_predicrion so the user is able to "deselect" certain outputs. Syntax: no
--aseg_name
means no aseg, unsure about--asegdkt_segfile
maybe none.Step 3: Test how reliable different view predict the brainmask.
Step 4: implement the best view for
long_prepare_template.sh
.Step 5: Test impact on longitudinal pipeline.