Dear Clemens,
this is very strange, since the talairach.xfm is not by default overwritten in recon-all (unless you specified -clean-tal to recon-all).
When you rerun your recon-all after modifying talairach.xfm, your automatic talairach registration will be saved into talairach.auto.xfm, therefore talairach.auto.xfm and talairach.xfm will be different (without editing they will be identical).
See the excerpt of the recon-all -help:
Talairach (-<no>talairach)
This computes the affine transform from the orig volume to the MNI305 atlas using Avi Snyders 4dfp suite of image registration tools, through a FreeSurfer script called talairach_avi. Several of the downstream programs use talairach coordinates as seed points. You can/should check how good the talairach registration is using "tkregister2 --s subjid --fstal-avi". You must have an "fsaverage" subject in your SUBJECTS_DIR. tkregister2 allows you to compare the orig volume against the talairach volume resampled into the orig space. If you modify the registration, it will change the talairach.xfm file. Your edits will be *not* be overwritten unless you run recon-all specifying -clean-tal. Run "tkregister2 --help" for more information. Creates the files mri/transform/talairach.auto.xfm and talairach.xfm. The flag -tal-check will check the registration against known-good transforms. Adding the flag -use-mritotal after -talairach will use the MINC program mritotal (see Collins, et al., 1994) to perform the transform.
Can you check that your edited talairach.xfm is indeed modified to default after recon-all rerun? Do the talairach.xfm and talairach.auto.xfm differ?
Antonin
Hi Antonin
Thank you for your reply.
Here is what I did: 1. tkregister2 --mgz --s x140214_b02_0917040_3_1_wipmp2rage0p8mmsenseV42_reOrient --fstal 2. manual registration (see attached file “before_recon-all_talairach.xfm”) 3. re-run recon-all, which is: recon-all -s x140214_b02_0917040_3_1_wipmp2rage0p8mmsenseV42_reOrient -all -hippocampal-subfields-T1
This resulted in the following error message: #@# Talairach Failure Detection Wed Aug 16 08:53:15 CEST 2017 /Volumes/PromisePegasus/HippocampusPreparedT1Data/subjects/x140214_b02_0917040_3_1_wipmp2rage0p8mmsenseV42_reOrient/mri \n talairach_afd -T 0.005 -xfm transforms/talairach.xfm \n ERROR: talairach_afd: Talairach Transform: transforms/talairach.xfm ***FAILED*** (p=0.0622, pval=0.0034 < threshold=0.0050) \nManual Talairach alignment may be necessary, or include the -notal-check flag to skip this test, making sure the -notal-check flag follows -all or -autorecon1 in the command string. See:\n http://surfer.nmr.mgh.harvard.edu/fswiki/FsTutorial/Talairach
\nERROR: Talairach failed!\n
The file that I now find in the “transforms” folder is attached (“after_recon-all_talairach.xfm”).
I also attached the two talairach.auto.xfm but I didn’t modify these at any point. (Should I? If so, how do I?)
Clemens
-----freesurfer-bounces@nmr.mgh.harvard.edu schrieb: ----- An: freesurfer@nmr.mgh.harvard.edu Von: Antonin Skoch Gesendet von: freesurfer-bounces@nmr.mgh.harvard.edu Datum: 15.08.2017 16:46 Betreff: Re: [Freesurfer] use manually defined talairach.xfm
Dear Clemens,
this is very strange, since the talairach.xfm is not by default overwritten in recon-all (unless you specified -clean-tal to recon-all).
When you rerun your recon-all after modifying talairach.xfm, your automatic talairach registration will be saved into talairach.auto.xfm, therefore talairach.auto.xfm and talairach.xfm will be different (without editing they will be identical).
See the excerpt of the recon-all -help:
Talairach (-<no>talairach)
This computes the affine transform from the orig volume to the MNI305 atlas using Avi Snyders 4dfp suite of image registration tools, through a FreeSurfer script called talairach_avi. Several of the downstream programs use talairach coordinates as seed points. You can/should check how good the talairach registration is using "tkregister2 --s subjid --fstal-avi". You must have an "fsaverage" subject in your SUBJECTS_DIR. tkregister2 allows you to compare the orig volume against the talairach volume resampled into the orig space. If you modify the registration, it will change the talairach.xfm file. Your edits will be *not* be overwritten unless you run recon-all specifying -clean-tal. Run "tkregister2 --help" for more information. Creates the files mri/transform/talairach.auto.xfm and talairach.xfm. The flag -tal-check will check the registration against known-good transforms. Adding the flag -use-mritotal after -talairach will use the MINC program mritotal (see Collins, et al., 1994) to perform the transform.
Can you check that your edited talairach.xfm is indeed modified to default after recon-all rerun? Do the talairach.xfm and talairach.auto.xfm differ?
Antonin
_______________________________________________ Freesurfer mailing list Freesurfer@nmr.mgh.harvard.edu https://mail.nmr.mgh.harvard.edu/mailman/listinfo/freesurfer
The information in this e-mail is intended only for the person to whom it is addressed. If you believe this e-mail was sent to you in error and the e-mail contains patient information, please contact the Partners Compliance HelpLine at http://www.partners.org/complianceline . If the e-mail was sent to you in error but does not contain patient information, please contact the sender and properly dispose of the e-mail.
That is the automatic failure detection for the talairach registration that is throwing the error. This checks the reg matrix against a sample of normal data. If the subject is in at a funny angle, then this can fail even if the registration is ok. You can just turn it off with -no-talcheck
On 08/16/2017 03:20 AM, clemens.schroeder@uzh.ch wrote:
Hi Antonin
Thank you for your reply.
Here is what I did:
1.tkregister2 --mgz --s x140214_b02_0917040_3_1_wipmp2rage0p8mmsenseV42_reOrient --fstal
2.manual registration (see attached file “before_recon-all_talairach.xfm”)
3.re-run recon-all, which is:recon-all -s x140214_b02_0917040_3_1_wipmp2rage0p8mmsenseV42_reOrient -all -hippocampal-subfields-T1
This resulted in the following error message:
#@# Talairach Failure Detection Wed Aug 16 08:53:15 CEST 2017
/Volumes/PromisePegasus/HippocampusPreparedT1Data/subjects/x140214_b02_0917040_3_1_wipmp2rage0p8mmsenseV42_reOrient/mri
\n talairach_afd -T 0.005 -xfm transforms/talairach.xfm \n
ERROR: talairach_afd: Talairach Transform: transforms/talairach.xfm ***FAILED*** (p=0.0622, pval=0.0034 < threshold=0.0050)
\nManual Talairach alignment may be necessary, or
include the -notal-check flag to skip this test,
making sure the -notal-check flag follows -all
or -autorecon1 in the command string.
See:\n
http://surfer.nmr.mgh.harvard.edu/fswiki/FsTutorial/Talairach
\nERROR: Talairach failed!\n
The file that I now find in the “transforms” folder is attached (“after_recon-all_talairach.xfm”).
I also attached the two talairach.auto.xfm but I didn’t modify these at any point.
(Should I? If so, how do I?)
Clemens
-----freesurfer-bounces@nmr.mgh.harvard.edu mailto:-----freesurfer-bounces@nmr.mgh.harvard.edu schrieb: ----- An: freesurfer@nmr.mgh.harvard.edu mailto:freesurfer@nmr.mgh.harvard.edu Von: Antonin Skoch Gesendet von: freesurfer-bounces@nmr.mgh.harvard.edu mailto:freesurfer-bounces@nmr.mgh.harvard.edu Datum: 15.08.2017 16:46 Betreff: Re: [Freesurfer] use manually defined talairach.xfm
Dear Clemens,
this is very strange, since the talairach.xfm is not by default overwritten in recon-all (unless you specified -clean-tal to recon-all).
When you rerun your recon-all after modifying talairach.xfm, your automatic talairach registration will be saved into talairach.auto.xfm, therefore talairach.auto.xfm and talairach.xfm will be different (without editing they will be identical).
See the excerpt of the recon-all -help:
Talairach (-<no>talairach)
This computes the affine transform from the orig volume to the MNI305 atlas using Avi Snyders 4dfp suite of image registration tools, through a FreeSurfer script called talairach_avi. Several of the downstream programs use talairach coordinates as seed points. You can/should check how good the talairach registration is using "tkregister2 --s subjid --fstal-avi". You must have an "fsaverage" subject in your SUBJECTS_DIR. tkregister2 allows you to compare the orig volume against the talairach volume resampled into the orig space. If you modify the registration, it will change the talairach.xfm file. Your edits will be *not* be overwritten unless you run recon-all specifying -clean-tal. Run "tkregister2 --help" for more information. Creates the files mri/transform/talairach.auto.xfm and talairach.xfm. The flag -tal-check will check the registration against known-good transforms. Adding the flag -use-mritotal after -talairach will use the MINC program mritotal (see Collins, et al., 1994) to perform the transform.
Can you check that your edited talairach.xfm is indeed modified to default after recon-all rerun? Do the talairach.xfm and talairach.auto.xfm differ?
Antonin
Freesurfer mailing list Freesurfer@nmr.mgh.harvard.edu mailto:Freesurfer@nmr.mgh.harvard.edu https://mail.nmr.mgh.harvard.edu/mailman/listinfo/freesurfer
The information in this e-mail is intended only for the person to whom it is addressed. If you believe this e-mail was sent to you in error and the e-mail contains patient information, please contact the Partners Compliance HelpLine at http://www.partners.org/complianceline . If the e-mail was sent to you in error but does not contain patient information, please contact the sender and properly dispose of the e-mail.
Freesurfer mailing list Freesurfer@nmr.mgh.harvard.edu https://mail.nmr.mgh.harvard.edu/mailman/listinfo/freesurfer
freesurfer@nmr.mgh.harvard.edu