Differences between revisions 7 and 13 (spanning 6 versions)
Revision 7 as of 2010-03-31 12:32:33
Size: 2496
Comment:
Revision 13 as of 2010-03-31 13:52:33
Size: 3253
Comment:
Deletions are marked like this. Additions are marked like this.
Line 2: Line 2:
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). 'Edits' is the term that describes manual interventions 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 (which 'edits' the alignment to Talairach space), or by adding explicit command-line arguments. 'Persistent' edits means these edits, once made, are treated as permanent changes, in the sense that once an edit is made, it is saved to a file (either a voxel change in a volume, or a text file listing points or commands), and it is automatically re-used by recon-all when recon-all is run. Persistent edits are removed via '-clean' options to recon-all. A 'persistent' edit is in contrast to the host of possible recon-all flags that could be added 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 specifying them again on the recon-all command string 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). 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).
Line 6: Line 6:
{{{
recon-all -s subjid -show-edits
}}}
'''All of the persistent edits made to a subject can be revealed by using the recon-all option {{{-show-edits}}}''' (available in v5.X).
Line 10: Line 8:
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. 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}}}'''
Line 14: Line 14:
=== user intervention ===
See [[FsTutorial/TroubleshootingData|troubleshooting]].

=== recon-all handling ===
==== user intervention ====
A control point is added to indicate a white matter voxel. See [[FsTutorial/ControlPoints]].
==== recon-all handling ====
'mri_normalize' and 'mri_ca_normalize' use controls points in the -normalization, -canorm and -normalization2 stages.
==== removal ====
{{{-clean-cp}}}
Line 20: Line 22:
=== user intervention ===
=== recon-all handling ===
==== user intervention ====
If the talairach alignment is bad, tkregister2 is used to manually correct it. See [[FsTutorial/Talairach]].
==== recon-all handling ====
The -talairach stage creates the file talairach.auto.xfm, and copies it to talairach.xfm '''unless the file talairach.xfm already exists'''. If talairach.xfm already exists, it is assumed the user has either edited talairach.xfm, or it exists from a prior run of recon-all.
==== removal ====
{{{-clean-tal}}}
Line 24: Line 30:
=== user intervention ===
=== recon-all handling ===
==== user intervention ====
==== recon-all handling ====
==== removal ====
Line 28: Line 35:
=== user intervention ===
=== recon-all handling ===
==== user intervention ====
==== recon-all handling ====
==== removal ====
Line 32: Line 40:
=== user intervention ===
=== recon-all handling ===
==== user intervention ====
==== recon-all handling ====
==== removal ====
Line 36: Line 45:
=== user intervention ===
=== recon-all handling ===
==== user intervention ====
==== recon-all handling ====
==== removal ====
Line 40: Line 50:
=== user intervention ===
=== recon-all handling ===
==== user intervention ====
==== recon-all handling ====
==== removal ====
Line 44: Line 55:
=== user intervention ===
=== recon-all handling ===
==== user intervention ====
==== recon-all handling ====
==== removal ====
Line 48: Line 60:
=== user intervention ===
=== recon-all handling ===
==== 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 recon-all option -show-edits (available in v5.X).

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

A control point is added to indicate a white matter voxel. See FsTutorial/ControlPoints.

recon-all handling

'mri_normalize' and 'mri_ca_normalize' use controls points in the -normalization, -canorm and -normalization2 stages.

removal

-clean-cp


talairach.xfm

user intervention

If the talairach alignment is bad, tkregister2 is used to manually correct it. See FsTutorial/Talairach.

recon-all handling

The -talairach stage creates the file talairach.auto.xfm, and copies it to talairach.xfm unless the file talairach.xfm already exists. If talairach.xfm already exists, it is assumed the user has either edited talairach.xfm, or it exists from a prior run of recon-all.

removal

-clean-tal


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

removal

Edits (last edited 2015-04-20 16:48:54 by MartinReuter)