Freesurfer

freesurfer@nmr.mgh.harvard.edu

16 participants
30084 discussions

EM registration error?
by Wenger, Elisabeth 21 Apr '09

21 Apr '09

Dear freesurfer specialists, we just ran a sample of subjects, and in a few of them the following problem occured: freesurfer exited with error during em registration, telling us that the wm peak could not be found. The protocol looks like this: #@# EM Registration Tue Mar 24 18:47:53 CET 2009 /Applications/freesurfer/subjects/hu66B/mri \n mri_em_register -mask brainmask.mgz nu.mgz /Applications/freesurfer/average/RB_all_2008-03-26.gca transforms/talairach.lta \n using MR volume brainmask.mgz to mask input volume... reading 1 input volumes... logging results to talairach.log reading '/Applications/freesurfer/average/RB_all_2008-03-26.gca'... average std = 6.9 using min determinant for regularization = 4.7 0 singular and 1812 ill-conditioned covariance matrices regularized reading 'nu.mgz'... freeing gibbs priors...done. bounding unknown intensity as < 14.9 or > 790.2 total sample mean = 84.0 (478 zeros) ************************************************ spacing=8, using 2185 sample points, tol=1.00e-05... ************************************************ register_mri: find_optimal_transform find_optimal_transform: nsamples 2185, passno 0, spacing 8 GCAhistoScaleImageIntensities: could not find wm peak resetting wm mean[0]: 102 --> 107 resetting gm mean[0]: 64 --> 64 input volume #1 is the most T1-like using real data threshold=12.9 skull bounding box = (61, 32, 28) --> (196, 145, 201) using (106, 70, 115) as brain centroid... mean wm in atlas = 107, using box (89,56,94) --> (122, 83,136) to find MRI wm before smoothing, mri peak at 0 after smoothing, mri peak at 0, scaling input intensities by inf Darwin mpib4003.mpib-berlin.mpg.de 9.6.0 Darwin Kernel Version 9.6.0: Mon Nov 24 17:37:00 PST 2008; root:xnu-1228.9.59~1/RELEASE_I386 i386 recon-all exited with ERRORS at Tue Mar 24 18:48:48 CET 2009 We are freesurfer beginners and don't have a clue what kind of mistake this could be. We couldn't find any obvious differnces to our other subjects which ran fine. I also attach the whole recon-all.log file, just in case a problem occured on a previous stage we didn't recognize. Thank you for your help! Best, Elisabeth and Shireen

2 1

Re: [Freesurfer] t4_read error (fwd)
by Zhen Zonglei 21 Apr '09

21 Apr '09

Hi avi: Thanks for your help. Still have two questions. 1) How to determine whether the Talairach transform is reasonable based on recon-all.log? 2) As you mentioned, we can make a suitable 3T atlas-representative target to resolve the Talairach transform problem. Now, we have several dozens of adult Chinese 3T MPRAGE data. Would you please give us some cues how to generate the 3T atlas target with FreeSurfer? Anyone has ideas on this issue,please let me know. Thanks again. Zonglei 2009/4/20 Avi Snyder <avi(a)npg.wustl.edu> > Zonglei, > > The log files contain the string "t4_read:..... read error" > This is a benign message indicating the the affine transform > file was not found. This always occurs at the start of the > affine transform sequence and carries no significance. > > Review of the log file indicates that in the case of subjA39 > Talairach atlas transform achieved a reasonable numeric result. > > In the case of subjA06 the Talairach transform did not achieve > a good result. This is an algorithmic issue. It appears that > the talairah_avi module was initiated twice, I assume, in an attmept > to improve the result, but the result did not improve. In this > log file the "read error" message occurs twice but it simply > means that the transform sequence was initiated twice. > > So, there is a problem but the the "read error" message has nothing > to do with it. Poor MP-RAGE to atlas representative target results > most likely are attributable to use of a 1.5T target with 3T input. > It this is correct, then a permanent solution to the problem could > be achieved by selecting the > atlas-representative target according to the MP-RAGE source. > Generation of a suitable 3T target would not be difficult. > > Avi > ------------------------------------------------------ > Date: Sun, 19 Apr 2009 22:52:35 +0800 > Subject: Re: [Freesurfer] t4_read error (fwd) > From: Zhen Zonglei <zonglei.fsl(a)gmail.com> > To: Avi Snyder <avi(a)npg.wustl.edu> > Cc: fischl(a)nmr.mgh.harvard.edu, nicks(a)nmr.mgh.harvard.edu, > freesurfer(a)nmr.mgh.harvard.edu > > Hi avi: > > Thanks for your response, attachments are my recon-all.logs. > If you have any ideas,please let me know. > > Thanks again. > > 2009/4/17 Avi Snyder <avi(a)npg.wustl.edu> > ----------------------------------------------- > > Zonglei, > > > > Send the log file to > > > > avi(a)npg.wustl.edu > > ---------------------------------------- > > >Date: Fri, 17 Apr 2009 11:15:19 -0400 (EDT) > > >From: Bruce Fischl <fischl(a)nmr.mgh.harvard.edu> > > >To: Avi Snyder <avi(a)npg.wustl.edu> > > >cc: nicks(a)nmr.mgh.harvard.edu > > > > > >do you want to contact him directly? > > > > > >On Fri, 17 Apr 2009, Avi Snyder wrote: > > > > > >> Most likely the MPRAGE->atlas computation aborted without creating > > >> the relevant t4 file (ASCII representation of the affine transform). > > >> This could occur if the images were somehow corrupted. > > >> > > >> Alternatively, the t4 file is present but a recent OS upgrade has > caused > > >> the previously compiled t4_read FORTRAN function to bomb. I have seen > this > case > > >> once before and have therefore created an all-C t4 i/o module. > > >> > > >> We can distinguish these cases by asking if you got a core dump, of if > > >> a t4 file is still present. The complete tal transform log file would > > >> be diagnostically very helpful. > > >> > > >> Avi > > >> ------------------------------------------ > > >>> Date: Fri, 17 Apr 2009 07:58:36 -0400 (EDT) > > >>> From: Bruce Fischl <fischl(a)nmr.mgh.harvard.edu> > > >>> To: Avi Snyder <avi(a)npg.wustl.edu> > > >>> cc: Nick Schmansky <nicks(a)nmr.mgh.harvard.edu> > > >>> Subject: [Freesurfer] t4_read error (fwd) > > >>> > > >>> Hi Avi, > > >>> > > >>> do you know what this message means? > > >>> > > >>> thanks > > >>> Bruce > > >>> ---------- Forwarded message ---------- > > >>> Date: Fri, 17 Apr 2009 19:32:05 +0800 > > >>> From: Zhen Zonglei <zonglei.fsl(a)gmail.com> > > >>> To: freesurfer(a)nmr.mgh.harvard.edu > > >>> Subject: [Freesurfer] t4_read error > > >>> > > >>> Dear all: > > >>> Recon-all has finished without error in my reconstruction. However, > when I > > >>> checked recon-all.log, I found three was a error “t4_read: > > >>> talsrcimg_to_711-2C_as_mni_average_305_t4 read error”. > > >>> > > >>> What's this error mean? Does it have some effects on my > reconstruction? > > >>> > > >>> Thanks > > >>> > > >>> -- > > >>> Zonglei Zhen, PhD > > >>> Assistant Professor of Cognitive Neuroscience > > >>> BNU Imaging Center for Brain Research, State Key Laboratory of > > Cognitive > > >>> Neuroscience and Learning, P.R. China > -- > Zonglei Zhen, PhD > Assistant Professor of Cognitive Neuroscience > BNU Imaging Center for Brain Research, State Key Laboratory of Cognitive > Neuroscience and Learning, P.R. China > > > -- Zonglei Zhen, PhD Assistant Professor of Cognitive Neuroscience BNU Imaging Center for Brain Research, State Key Laboratory of Cognitive Neuroscience and Learning, P.R. China

2 1

Re: [Freesurfer] t4_read error
by Allison Stevens 21 Apr '09

21 Apr '09

This message appears in the recon-all.log for several data sets I have here and all that data looks good. The most important thing is how your data looks. Does it look okay? I'm not sure why this message is there (Nick?) but I think you can ignore it. Allison On Sat, 18 Apr 2009, Zhen Zonglei wrote: > The log files from both version 4.03 and version 4.30 report this error( > t4_read: talsrcimg_to_711-2C_as_mni_average_305_t4 read error ). It occurs > in imgreg_4dfp. > > attachment is my logfile,please check it. > > 2009/4/17 Allison Stevens <astevens(a)nmr.mgh.harvard.edu> > >> What version of FreeSurfer are you using and what step of the process does >> that error appear in? >> Allison >> >> -- >> >> On Fri, 17 Apr 2009, Zhen Zonglei wrote: >> >> Dear all: >>> Recon-all has finished without error in my reconstruction. However, when I >>> checked recon-all.log, I found three was a error ?t4_read: >>> talsrcimg_to_711-2C_as_mni_average_305_t4 read error?. >>> >>> What?s this error mean? Does it have some effects on my reconstruction? >>> >>> >>> >>> Thanks >>> >>> >>> > > >

2 1

selxavg3/fast_selxavg3, error saving matrix when Gamma/SPM-HRF
by N. Eiji Nawa 20 Apr '09

20 Apr '09

Hi: I am trying to perform a first-level analysis using mkanalysis-sess and selxavg3-sess using data from one of my experiments and the steps described in the FsFastTutorial (http://surfer.nmr.mgh.harvard.edu/fswiki/FsFastTutorial ). I am able to complete the analysis using the tutorial data but on my data selxavg3 returns the following error: ... ... > In fast_selxavg3 at 212 Warning: Matrix is singular, close to singular or badly scaled. Results may be inaccurate. RCOND = NaN. > In fast_selxavg3 at 212 ntptot = 740, nX = 32, DOF = 708 Saving X matrix to /Users/eiji/exp/ FS_classic_oddball_2009/090407_Kitamichi/bold/classodd-gamma-fwhm8/ Xtmp.mat ??? Error using ==> svd Input to SVD must not contain NaN or Inf. Error in ==> cond at 40 s = svd(A); Error in ==> fast_selxavg3 at 248 XCond = cond(XtX); >> 2009-04-20 13:47:07.771 MATLAB[82205:60b] Process manager already initialized -- can't fully enable headless mode. ------------------------------------------ ERROR: fast_selxavg3() failed\n This only happens when I choose the Gamma function or the SPM hemodynamic response function in mkanalysis-sess. If the chosen function is the finite-impulse response, selxavg3 finishes with no major problems. I am clueless about what could be causing this error. If you have any ideas or need more detailed information, please, let me know! Thanks very much. Eiji -- FREESURFER_HOME: /Applications/freesurfer Build stamp: freesurfer-Darwin-leopard-i686-stable-pub-v4.3.0 Kernel info: Darwin 9.6.0 i386 (Mac OS X 10.5.6 Intel)

1 0

slice time correction in preproc-sess, stc.fsl and Analyze
by N. Eiji Nawa 19 Apr '09

19 Apr '09

Hi, I was trying to preprocess some data with the option of slice time correction but preproc-sess exited with the following error: preproc-sess -sf sessid -df sesspar -rlf runlistfile -sliceorder odd - fwhm 8 -update ... ... -------------------- INFO: set hdr.hist.orient to -1 /Users/eiji/exp/myFS slicetimer -i /Users/eiji/exp/FS_classic_oddball_2009/090407_K/bold/ 004/tmp.76874/in.img -o /Users/eiji/exp/ FS_classic_oddball_2009/090407_K/bold/004/tmp.76874/out.img --ocustom=/ Users/eiji/exp/FS_classic_oddball_2009/090407_K/bold/004/tmp.76874/ saof.dat ERROR:: Unrecognised value (ANALYZE) of environment variable FSLOUTPUTTYPE Legal values are: NIFTI, NIFTI_PAIR, NIFTI_GZ, NIFTI_PAIR_GZ ERROR: mc-sess failed It turns out that I have FSL 4.1 installed on my system and FSL 4.1 does not support outputting of Analyze files anymore (http://www.fmrib.ox.ac.uk/fsl/fsl/whatsnew.html ). I suppose this error will not occur if one sticks with the FSL package (3.2?) that comes bundled with freesurfer. So I thought the "least effort" solution would be to prevent preproc- sess from trying to output in Analyze. Below are 3 changes I had to do in fsfast/bin/stc.fsl to make it work: 1) Comment out line #158 in stc.fsl #setenv FSLOUTPUTTYPE ANALYZE 2) Edit line #159 from set outtmp = $tmpdir/out.img to set outtmp = $tmpdir/out.nii.gz 3) Edit line #176 from set cmd = (mri_convert -it analyze4d $outtmp $outfunc) to set cmd = (mri_convert -it nii $outtmp $outfunc) I want to make sure I am not unknowingly messing up with some later stage in preproc-ses, if you find something like that, please let me know! Thanks a lot! Eiji -- FREESURFER_HOME: /Applications/freesurfer Build stamp: freesurfer-Darwin-leopard-i686-stable-pub-v4.3.0 Kernel info: Darwin 9.6.0 i386 (Mac OS X 10.5.6 Intel)

1 0

Re: [Freesurfer] t4_read error (fwd)
by Zhen Zonglei 19 Apr '09

19 Apr '09

Hi avi: Thanks for your response, attachments are my recon-all.logs. If you have any ideas,please let me know. Thanks again. 2009/4/17 Avi Snyder <avi(a)npg.wustl.edu> > Zonglei, > > Send the log file to > > avi(a)npg.wustl.edu > ---------------------------------------- > >Date: Fri, 17 Apr 2009 11:15:19 -0400 (EDT) > >From: Bruce Fischl <fischl(a)nmr.mgh.harvard.edu> > >To: Avi Snyder <avi(a)npg.wustl.edu> > >cc: nicks(a)nmr.mgh.harvard.edu > > > >do you want to contact him directly? > > > >On Fri, 17 Apr 2009, Avi Snyder wrote: > > > >> Most likely the MPRAGE->atlas computation aborted without creating > >> the relevant t4 file (ASCII representation of the affine transform). > >> This could occur if the images were somehow corrupted. > >> > >> Alternatively, the t4 file is present but a recent OS upgrade has caused > >> the previously compiled t4_read FORTRAN function to bomb. I have seen > this case > >> once before and have therefore created an all-C t4 i/o module. > >> > >> We can distinguish these cases by asking if you got a core dump, of if > >> a t4 file is still present. The complete tal transform log file would > >> be diagnostically very helpful. > >> > >> Avi > >> ------------------------------------------ > >>> Date: Fri, 17 Apr 2009 07:58:36 -0400 (EDT) > >>> From: Bruce Fischl <fischl(a)nmr.mgh.harvard.edu> > >>> To: Avi Snyder <avi(a)npg.wustl.edu> > >>> cc: Nick Schmansky <nicks(a)nmr.mgh.harvard.edu> > >>> Subject: [Freesurfer] t4_read error (fwd) > >>> > >>> Hi Avi, > >>> > >>> do you know what this message means? > >>> > >>> thanks > >>> Bruce > >>> > >>> ---------- Forwarded message ---------- > >>> Date: Fri, 17 Apr 2009 19:32:05 +0800 > >>> From: Zhen Zonglei <zonglei.fsl(a)gmail.com> > >>> To: freesurfer(a)nmr.mgh.harvard.edu > >>> Subject: [Freesurfer] t4_read error > >>> > >>> Dear all: > >>> Recon-all has finished without error in my reconstruction. However, > when I > >>> checked recon-all.log, I found three was a error “t4_read: > >>> talsrcimg_to_711-2C_as_mni_average_305_t4 read error”. > >>> > >>> What’s this error mean? Does it have some effects on my reconstruction? > >>> > >>> Thanks > >>> > >>> -- > >>> Zonglei Zhen, PhD > >>> Assistant Professor of Cognitive Neuroscience > >>> BNU Imaging Center for Brain Research, State Key Laboratory of > Cognitive > >>> Neuroscience and Learning, P.R. China > > -- Zonglei Zhen, PhD Assistant Professor of Cognitive Neuroscience BNU Imaging Center for Brain Research, State Key Laboratory of Cognitive Neuroscience and Learning, P.R. China

1 0

t4_read error
by Zhen Zonglei 17 Apr '09

17 Apr '09

Dear all: Recon-all has finished without error in my reconstruction. However, when I checked recon-all.log, I found three was a error “t4_read: talsrcimg_to_711-2C_as_mni_average_305_t4 read error”. What’s this error mean? Does it have some effects on my reconstruction? Thanks -- Zonglei Zhen, PhD Assistant Professor of Cognitive Neuroscience BNU Imaging Center for Brain Research, State Key Laboratory of Cognitive Neuroscience and Learning, P.R. China

1 0

Extracting Thickness Vertex Values
by Jeff Sadino 16 Apr '09

16 Apr '09

Hello all again, I am displaying the sig.mgh file after running mris_glm. I can also see the fsgdf scatterplot when clicking on a vertex. What I would like is to be able to copy the thickness values for each subject in the group for the vertex I clicked on to an ascii/matlab/excel file. Otherwise, I'll use the mris_convert command on each subject to make an ascii file. As always, thanks for your expert help! Jeff Sadino _________________________________________________________________ Windows Live™: Life without walls. http://windowslive.com/explore?ocid=TXT_TAGLM_WL_allup_1b_explore_042009

1 0

dicom convert
by Gabriel Go.Es. 16 Apr '09

16 Apr '09

Dear colleages, I am trying to convert my dicom files to .mgz from Freesurfer (release 4.2) by using the mri_convert command, but it provides me the following error: [root@localhost ~]$ cd /root/trabajo/freesurfer/subjects/mci_001/mri [root@localhost mri]$ mri_convert -it dicom -ot mgz orig/001*.dcm 001.mgz mri_convert -it dicom -ot mgz orig/001088.dcm orig/001089.dcm orig/001090.dcm orig/001091.dcm orig/001092.dcm orig/001093.dcm orig/001094.dcm orig/001095.dcm orig/001096.dcm orig/001097.dcm orig/001098.dcm orig/001099.dcm orig/001100.dcm orig/001101.dcm orig/001102.dcm orig/001103.dcm orig/001104.dcm orig/001105.dcm orig/001106.dcm orig/001107.dcm orig/001108.dcm orig/001109.dcm orig/001110.dcm orig/001111.dcm orig/001112.dcm orig/001113.dcm orig/001114.dcm orig/001115.dcm orig/001116.dcm orig/001117.dcm orig/001118.dcm orig/001119.dcm orig/001120.dcm orig/001121.dcm orig/001122.dcm orig/001123.dcm orig/001124.dcm orig/001125.dcm orig/001126.dcm orig/001127.dcm orig/001128.dcm orig/001129.dcm orig/001130.dcm orig/001131.dcm orig/001132.dcm orig/001133.dcm orig/001134.dcm orig/001135.dcm orig/001136.dcm orig/001137.dcm orig/001138.dcm orig/001139.dcm orig/001140.dcm orig/001141.dcm orig/001142.dcm orig/001143.dcm orig/001144.dcm orig/001145.dcm orig/001146.dcm orig/001147.dcm orig/001148.dcm orig/001149.dcm orig/001150.dcm orig/001151.dcm orig/001152.dcm orig/001153.dcm orig/001154.dcm orig/001155.dcm orig/001156.dcm orig/001157.dcm orig/001158.dcm orig/001159.dcm orig/001160.dcm orig/001161.dcm orig/001162.dcm orig/001163.dcm orig/001164.dcm orig/001165.dcm orig/001166.dcm orig/001167.dcm orig/001168.dcm orig/001169.dcm orig/001170.dcm orig/001171.dcm orig/001172.dcm orig/001173.dcm orig/001174.dcm orig/001175.dcm orig/001176.dcm orig/001177.dcm orig/001178.dcm orig/001179.dcm orig/001180.dcm orig/001181.dcm orig/001182.dcm orig/001183.dcm orig/001184.dcm orig/001185.dcm orig/001186.dcm orig/001187.dcm orig/001188.dcm orig/001189.dcm orig/001190.dcm orig/001191.dcm orig/001192.dcm orig/001193.dcm orig/001194.dcm orig/001195.dcm orig/001196.dcm orig/001197.dcm orig/001198.dcm orig/001199.dcm orig/001200.dcm orig/001201.dcm orig/001202.dcm orig/001203.dcm orig/001204.dcm orig/001205.dcm orig/001206.dcm orig/001207.dcm orig/001208.dcm orig/001209.dcm orig/001210.dcm orig/001211.dcm orig/001212.dcm orig/001213.dcm orig/001214.dcm orig/001215.dcm orig/001216.dcm orig/001217.dcm orig/001218.dcm orig/001219.dcm orig/001220.dcm orig/001221.dcm orig/001222.dcm 001.mgz mri_convert: extra arguments ("orig/001090.dcm" and following) Could anybody help me with this problem? Thanks in advance, Gabriel _________________________________________________________________ ¿Quieres que tus hijos naveguen seguros? Aprende aquí cómo con Protección Infantil http://www.protegeatushijos.com

4 3

freesurfer vs manual tracing
by Nicolas Cherbuin 16 Apr '09

16 Apr '09

Dear All, A paper comparing freesurfer hippocampal segmentation to manual tracing in a large middle-aged population was published today in PLOSONE and may be of interest to this list. Regards, Nic http://www.plosone.org/article/info%3Adoi%2F10.1371%2Fjournal.pone.00052 65 In Vivo Hippocampal Measurement and Memory: A Comparison of Manual Tracing and Automated Segmentation in a Large Community-Based Sample

2 1

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Freesurfer