Freesurfer

freesurfer@nmr.mgh.harvard.edu

3 participants
30135 discussions

Possible error in automatic filling of ventricles in wm.mgz
by Antonin Skoch 16 Oct '15

16 Oct '15

Dear FreeSurfer experts, In some subjects I encounter situation where I suspect that the ventricles are not accurately filled in wm.mgz file. I have uploaded the file ventricle_question.tar.gz with example subject to your server so that you can look. It seems to me that in left hemisphere at slices 91-approx 98 (coronal view) the voxels in temporal apex of the left ventricle are not correctly filled by value 250 which has the consequence that the pial and white surfaces are erroneously "digging in" the ventricle (see also the screenshot with arrow marking the suspicious spot). I encounter this situation repeatedly and in most cases it occurs in left hemisphere. Could you please comment on? Will this possible error have an effect to the analyses? Thank you very much for your support! Regards, Antonin Skoch

1 0

Re: [Freesurfer] pial surface encircling the optical chiasm
by Antonin Skoch 16 Oct '15

16 Oct '15

Dear experts, I am sending the example subject named chiasma_question.tar.gz to your FTP server. The issue with encircling chiasma is located in slices ~134-140. According to Aparc.a2009s+aseg the tissue is marked as optical chiasm, but also part of it is labeled as left cerebral white matter. I guess that for the whole-brain group analysis of cortical thickness this error probably will not have an effect since it seems that this region is masked by cortex.label, but in volumetric analyses there could be an effect, although probably very small. Or could this error cause some bias in cortical parcellation in adjacent cortical areas?...What do you think? Regards, Antonin Skoch

1 0

SOLVED - mri_convert segmentation fault after tracula update on Linux/glibc-2.20 (Gentoo)
by Volkmar Glauche 16 Oct '15

16 Oct '15

Dear all, in reply to myself as a documentation for others: I tried a recent development version of mri_convert. Instead of crashing, this version instructed me to get a new license file for systems running GNU glibc version greater 2.15. The new license file (.license, not license.txt) seems to do the trick. Best, Volkmar -- Freiburg Brain Imaging http://fbi.uniklinik-freiburg.de/ Tel. +761 270-54110 Fax. +761 270-53100

1 0

mri_convert segmentation fault after tracula update on Linux/glibc-2.20 (Gentoo)
by Volkmar Glauche 16 Oct '15

16 Oct '15

Dear List, I am facing a similar problem as described by Knut Bjuland: http://www.mail-archive.com/freesurfer%40nmr.mgh.harvard.edu/msg39745.html I could not find a public reply in the mailing list archives. Therefore I would like to know whether it would be safe to either downgrade mri_convert to the version before the tracula update or use a newer development version of mri_convert with Freesurfer 5.3. Best, Volkmar -- Freiburg Brain Imaging http://fbi.uniklinik-freiburg.de/ Tel. +761 270-54110 Fax. +761 270-53100

1 0

editsFail
by Timothy Quang-Tin Le 15 Oct '15

15 Oct '15

Hello, I am using free surfer version 5.0.0; how do I continue to edit the brain with the previous edits made if the brain was processed under applyEdits, but is now in editsFail? Does this mean that I have to redo the entire brain, or can I have it restored somehow? Thank you Timothy Le

1 0

Make average subject from additional data
by Jones, Richard 15 Oct '15

15 Oct '15

I have a group of subjects that I have run through the standard freesurfer (version 5.3) pipeline, for the same subjects I also have T2 volumetric data and I have created T1/T2 ratio images for each subject. I have registered the ratio images into Freesurfer space and used mri_vol2surf to create surface overlays at different depths into the cortex for each subject, and these look reasonable when displayed with freeview. I now want to create average subjects for the ratio images at each depth, but I'm not sure what's the best way of doing this? Any suggestions would be appreciated. Thanks, Richard

1 0

error using mri_glmfit
by Gold, Andrea (NIH/NIMH) [F] 15 Oct '15

15 Oct '15

Hi, I got the following error during my first time running the mri_glmfit command: mri_glmfit --y Model1_Maltx_ParentEd_Sex_Age_n58-lh-thickness.mgh --fsgd Model1_Maltx_ParentEd_Sex_Age_n58.fsgd --C Model1_Maltx.mtx --C Model1_ParentEd.mtx --surf fsaverage lh --glmdir Model1_Maltx_ParentEd_Sex_Age_n58-lh-thickness.glmdir -------------------------------- ERROR: matrix is ill-conditioned or badly scaled, condno = 1e+08 -------------------------------- Possible problem with experimental design: Check for duplicate entries and/or lack of range of continuous variables within a class. We are trying to look at the main effects of two discrete variables in the same model (I.e., effect of var1 while controlling for var2), while also regressing out sex (class) and age (variable). We don’t care about the interaction term(s). There are 16 regressors = 8 classes * (1 variable +1) = 16. The FSGD file is attached, and I copied the design matrix below. >From reading the archives, I tried Doug’s suggestion of "cat old.fsgd | sed 's/\\r/\\n/g' > new.fsgd” but that did not fix it. Then I tried removing the overall mean (across all 58 subjects) and got the same error – see attached “*_demeaned.fsgd” file. Thank you for your help with troubleshooting this error. Best, Andrea Design matrix ------------------ 1.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 18.053 0.000 0.000 0.000 0.000 0.000 0.000 0.000; 1.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 16.052 0.000 0.000 0.000 0.000 0.000 0.000 0.000; 1.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 14.267 0.000 0.000 0.000 0.000 0.000 0.000 0.000; 1.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 19.120 0.000 0.000 0.000 0.000 0.000 0.000 0.000; 1.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 15.195 0.000 0.000 0.000 0.000 0.000 0.000 0.000; 1.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 18.558 0.000 0.000 0.000 0.000 0.000 0.000 0.000; 1.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 17.895 0.000 0.000 0.000 0.000 0.000 0.000 0.000; 0.000 1.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 16.862 0.000 0.000 0.000 0.000 0.000 0.000; 0.000 1.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 17.974 0.000 0.000 0.000 0.000 0.000 0.000; 0.000 1.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 17.733 0.000 0.000 0.000 0.000 0.000 0.000; 0.000 1.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 17.260 0.000 0.000 0.000 0.000 0.000 0.000; 0.000 0.000 1.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 17.941 0.000 0.000 0.000 0.000 0.000; 0.000 0.000 0.000 1.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 16.712 0.000 0.000 0.000 0.000; 0.000 0.000 0.000 1.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 17.257 0.000 0.000 0.000 0.000; 0.000 0.000 0.000 1.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 17.446 0.000 0.000 0.000 0.000; 0.000 0.000 0.000 1.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 17.741 0.000 0.000 0.000 0.000; 0.000 0.000 0.000 1.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 15.718 0.000 0.000 0.000 0.000; 0.000 0.000 0.000 1.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 13.750 0.000 0.000 0.000 0.000; 0.000 0.000 0.000 1.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 14.111 0.000 0.000 0.000 0.000; 0.000 0.000 0.000 1.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 15.335 0.000 0.000 0.000 0.000; 0.000 0.000 0.000 1.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 16.329 0.000 0.000 0.000 0.000; 0.000 0.000 0.000 0.000 1.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 16.786 0.000 0.000 0.000; 0.000 0.000 0.000 0.000 1.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 17.990 0.000 0.000 0.000; 0.000 0.000 0.000 0.000 1.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 17.886 0.000 0.000 0.000; 0.000 0.000 0.000 0.000 1.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 18.497 0.000 0.000 0.000; 0.000 0.000 0.000 0.000 0.000 1.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 17.569 0.000 0.000; 0.000 0.000 0.000 0.000 0.000 1.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 17.604 0.000 0.000; 0.000 0.000 0.000 0.000 0.000 1.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 17.802 0.000 0.000; 0.000 0.000 0.000 0.000 0.000 1.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 16.851 0.000 0.000; 0.000 0.000 0.000 0.000 0.000 1.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 15.858 0.000 0.000; 0.000 0.000 0.000 0.000 0.000 1.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 16.640 0.000 0.000; 0.000 0.000 0.000 0.000 0.000 1.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 16.597 0.000 0.000; 0.000 0.000 0.000 0.000 0.000 1.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 17.410 0.000 0.000; 0.000 0.000 0.000 0.000 0.000 0.000 1.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 19.160 0.000; 0.000 0.000 0.000 0.000 0.000 0.000 1.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 15.636 0.000; 0.000 0.000 0.000 0.000 0.000 0.000 1.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 14.749 0.000; 0.000 0.000 0.000 0.000 0.000 0.000 1.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 14.056 0.000; 0.000 0.000 0.000 0.000 0.000 0.000 1.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 18.302 0.000; 0.000 0.000 0.000 0.000 0.000 0.000 1.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 17.333 0.000; 0.000 0.000 0.000 0.000 0.000 0.000 1.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 16.668 0.000; 0.000 0.000 0.000 0.000 0.000 0.000 1.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 20.236 0.000; 0.000 0.000 0.000 0.000 0.000 0.000 1.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 16.671 0.000; 0.000 0.000 0.000 0.000 0.000 0.000 1.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 19.058 0.000; 0.000 0.000 0.000 0.000 0.000 0.000 1.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 15.376 0.000; 0.000 0.000 0.000 0.000 0.000 0.000 0.000 1.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 19.209; 0.000 0.000 0.000 0.000 0.000 0.000 0.000 1.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 16.246; 0.000 0.000 0.000 0.000 0.000 0.000 0.000 1.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 17.640; 0.000 0.000 0.000 0.000 0.000 0.000 0.000 1.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 14.483; 0.000 0.000 0.000 0.000 0.000 0.000 0.000 1.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 16.214; 0.000 0.000 0.000 0.000 0.000 0.000 0.000 1.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 18.820; 0.000 0.000 0.000 0.000 0.000 0.000 0.000 1.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 17.955; 0.000 0.000 0.000 0.000 0.000 0.000 0.000 1.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 17.645; 0.000 0.000 0.000 0.000 0.000 0.000 0.000 1.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 17.514; 0.000 0.000 0.000 0.000 0.000 0.000 0.000 1.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 17.331; 0.000 0.000 0.000 0.000 0.000 0.000 0.000 1.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 16.189; 0.000 0.000 0.000 0.000 0.000 0.000 0.000 1.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 15.387; 0.000 0.000 0.000 0.000 0.000 0.000 0.000 1.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 15.231; 0.000 0.000 0.000 0.000 0.000 0.000 0.000 1.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 18.335; -- Andrea Gold, Ph.D. Section on Development and Affective Neuroscience National Institute of Mental Health Room 201, Bldg. 15K, MSC 2670 Bethesda, MD 20892-2670 Phone: 301-827-9804 Fax: 301-402-2010 Email: andrea.gold(a)nih.gov<applewebdata://D38F487B-BA2B-4BF6-A9C4-96248AB2BE51/andrea.gold@nih.gov>

3 3

Tracula stats COR-.info does not exist
by Simon Jones 15 Oct '15

15 Oct '15

Dear Tracula developers I thought I had nearly reached the end of tracula processing. However, when I perform the step, trac-all -stat -c dmrirc_ind_mni_cvs_all_stats.all I receive this error message . Base name of output files: /work/imagingC/Rowe/p00363/freesurfer/all/subs_tracts/stats/lh.cst_AS.avg33_ cvs_flt Text file with list of individual inputs: /work/imagingC/Rowe/p00363/freesurfer/all/subs_tracts/stats/lh.cst_AS.avg33_ cvs_flt.inputs.txt Loading output reference volume from /home/spj24/app/freesurfer/subjects/cvs_avg35 corRead(): can't open file /home/spj24/app/freesurfer/subjects/cvs_avg35/COR-.info ERROR: Could not read /home/spj24/app/freesurfer/subjects/cvs_avg35 There is no file called COR-.info in the directory /home/spj24/app/freesurfer/subjects/cvs_avg35/ I have commented nearly all lines from the file dmrirc_ind_mni_cvs_all_stats.all to leave a minimum configuration file and then the script runs without error. However, in that case the stats directory created only contains files related to avg33_mni_bbr ( and mni_flt if I add the switch set doregflt = 1). There are no cvs files. I am using tracula.update.centos4_x86_64.5.3.2014_05_26 in freesurfer-Linux-centos4_x86_64-stable-pub-v5.3.0. I performed all tracula processing steps before stats without the tracula.update.centos4_x86_64.5.3.2014_05_26, and then added the update to perform the stat step. Thanks for your help, Simon

1 0

Error during long_mris_slopes
by Benedikt Wenk 15 Oct '15

15 Oct '15

Dear FreeSurfer Experts While performing the long_mris_slopes --qdec I receive the following error: Traceback (most recent call last): File "/Applications/freesurfer/bin/long_mris_slopes", line 1125, in <module> shutil.rmtree(dirname) File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/shutil.py", line 253, in rmtree File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/shutil.py", line 251, in rmtree OSError: [Errno 66] Directory not empty: './tmp-lhab_2ur8.base_lh_thickness_f9caSb' I tried to solve the problem with tips from the internet but could not fix it. The directory is empty and every time I try for perform a new long_mris_slopes --qdec I receive the same error concerning another subject's folder like: Traceback (most recent call last): File "/Applications/freesurfer/bin/long_mris_slopes", line 1125, in <module> shutil.rmtree(dirname) File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/shutil.py", line 253, in rmtree File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/shutil.py", line 251, in rmtree OSError: [Errno 66] Directory not empty: './tmp-lhab_1lwe.base_lh_thickness_E_ExHB' Can you please help me with this? Thank you in advance. Sincerely, Ben

2 1

Extracting individual vertex values for surfaces mapped to fsaverage
by Bronwyn Overs 15 Oct '15

15 Oct '15

Dear mailing list, For each of the subjects in our study, we would like to extract the thickness values at each vertex for the surface that has been mapped to fsaverage (so that the number of vertices is identical for all of our subjects). After changing to a specific participants "surf" directory and starting matlab, could I use the following command and file to extract the data I want?: [thick, fnum] = read_curv('lh.thickness.fwhm10.fsaverage.mgh') Also, how do I then determine the annotation associated with each vertex for each subject? -- Kind regards, Bronwyn Overs Research Assistant Neuroscience Research Australia Neuroscience Research Australia Margarete Ainsworth Building Barker Street Randwick Sydney NSW 2031 Australia *M* 0411 308 769 *T* +61 2 9399 1883 neura.edu.au <http://neura.edu.au> Follow @neuraustralia on twitter <https://twitter.com/neuraustralia>Follow NeuRA on facebook <https://www.facebook.com/NeuroscienceResearchAustralia>Subscribe to the NeuRA Magazine <http://www.neura.edu.au/help-research/subscribe>

3 4

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