|
Size: 1137
Comment:
|
Size: 2844
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 2: | Line 2: |
| This page lists all the various possible edits that could be made to subject data supported by the recon-all stream (both the default 'cross-sectional' stream, and the longitudinal stream). | This page lists the 'persistent' edits that can be made to subject data supported by the recon-all stream (both the default 'cross-sectional' stream, and the longitudinal stream). An 'edit' in this context is a manual intervention by a user necessary when the automated stream (recon-all) does not produce output that is correct or suitable as determined by the user, or if the automated stream fails outright. Manual interventions occur via the volume editing tool tkmedit, tkregister2, or by recon-all command-line options. 'Persistent' in this context means that an edit, once made, is treated as a permanent change: it is saved to a file in some manner (either a voxel change in a volume, or a text file listing points or commands), and it is automatically re-used by recon-all if recon-all is run again. |
| Line 4: | Line 4: |
| All of the edits made to a subject can be revealed by using the -show-edits option of recon-all (available in v5.X): | Persistent edits are removed via '-clean' options to recon-all. A 'persistent' edit is in contrast to the many possible recon-all options available to alter the operation of an executable but are not saved to disk (and not re-used by recon-all, thus necessitating the user to specify the options again on any future run of recon-all if that operation is desired). Specifying gm/wm intensity priors is an example of a 'non-persistent' edit (one which is not saved to disk). All of the persistent edits made to a subject can be revealed by using the -show-edits option of recon-all (available in v5.X): |
| Line 10: | Line 12: |
| Note that 'edits' are made only to volumes. There is no such thing as a surface edit. Problems with the surface are corrected by making edits to an appropriate volume (see [[FsTutorial/TroubleshootingData|troubleshooting]]). | Each of the persistent edits is now described. Where/when/how it is used is referenced, along with how recon-all handles it internally, and how it can be removed. |
| Line 12: | Line 14: |
| '''Note: all edits can be removed with the option {{{-clean}}}''' ---- |
|
| Line 14: | Line 19: |
| Control points are added to indicate a white matter voxel. See [[FsTutorial/ControlPoints]]. | |
| Line 15: | Line 21: |
| The executables 'mri_normalize' and 'mri_ca_normalize' use controls points in the -normalization, -canorm and -normalization2 stages. === removal === {{{-clean-cp}}} ---- |
|
| Line 19: | Line 28: |
| === removal === ---- |
|
| Line 23: | Line 33: |
| === removal === ---- |
|
| Line 27: | Line 38: |
| === removal === ---- |
|
| Line 31: | Line 43: |
| === removal === ---- |
|
| Line 35: | Line 48: |
| === removal === ---- |
|
| Line 39: | Line 53: |
| === removal === ---- == cw256 == === user intervention === === recon-all handling === === removal === ---- == expert options == === user intervention === === recon-all handling === === removal === |
Edits
This page lists the 'persistent' edits that can be made to subject data supported by the recon-all stream (both the default 'cross-sectional' stream, and the longitudinal stream). An 'edit' in this context is a manual intervention by a user necessary when the automated stream (recon-all) does not produce output that is correct or suitable as determined by the user, or if the automated stream fails outright. Manual interventions occur via the volume editing tool tkmedit, tkregister2, or by recon-all command-line options. 'Persistent' in this context means that an edit, once made, is treated as a permanent change: it is saved to a file in some manner (either a voxel change in a volume, or a text file listing points or commands), and it is automatically re-used by recon-all if recon-all is run again.
Persistent edits are removed via '-clean' options to recon-all. A 'persistent' edit is in contrast to the many possible recon-all options available to alter the operation of an executable but are not saved to disk (and not re-used by recon-all, thus necessitating the user to specify the options again on any future run of recon-all if that operation is desired). Specifying gm/wm intensity priors is an example of a 'non-persistent' edit (one which is not saved to disk).
All of the persistent edits made to a subject can be revealed by using the -show-edits option of recon-all (available in v5.X):
recon-all -s subjid -show-edits
Each of the persistent edits is now described. Where/when/how it is used is referenced, along with how recon-all handles it internally, and how it can be removed.
Note: all edits can be removed with the option -clean
control points
user intervention
Control points are added to indicate a white matter voxel. See FsTutorial/ControlPoints.
recon-all handling
The executables 'mri_normalize' and 'mri_ca_normalize' use controls points in the -normalization, -canorm and -normalization2 stages.
removal
-clean-cp
talairach.xfm
user intervention
recon-all handling
removal
brainmask.mgz
user intervention
recon-all handling
removal
aseg.mgz
user intervention
recon-all handling
removal
brain.finalsurfs.mgz
user intervention
recon-all handling
removal
wm.mgz
user intervention
recon-all handling
removal
seed points
user intervention
recon-all handling
removal
cw256
user intervention
recon-all handling
removal
expert options
user intervention
recon-all handling