Freesurfer

freesurfer@nmr.mgh.harvard.edu

3 participants
30135 discussions

Recon-all error
by Emad Ahmadi 08 Jul '14

08 Jul '14

Hello FreeSurfers, Wish you a great summer time! I’m running recon-all on DICOM images of a healthy control, and it's giving me an error. I have attached the log file; I’m running FreeSurfer on a Mac computer and the version I’m using is: freesurfer-Darwin-lion-dev-20140701. I would really appreciate your help. Best, Emad Emad Ahmadi, MD ----------------------------------------------- Postdoc Research Fellow Department of Radiology Massachusetts General Hospital Harvard Medical School 25 New Chardon Street, Suite 400 Boston, MA 02114 Tel: 617 726 5237 Email: emad(a)nmr.mgh.harvard.edu

2 3

Anterior Temporal Lobe / Pial Reconstruction Troubles
by Las Blawimo 08 Jul '14

08 Jul '14

Dear Dr. Fischl, Thanks for your quick reply. Attached you will find some images showing the issues we're having. The images are as follows: 1.) sagittal_1353_norm2+3T_vs_default -> the v5.3 suggested norm2 flags (from the release notes) and the -3T flag vs. the default v5.3 pipeline. Blue is the norm2/3T flag pipeline, yellow is the default. 2.) sagittal_1353_wusl_vs_default ->v5.3 using the -washu_mprage flag, obvious improvement in temporal lobe pial surface. Blue is -washu_mprage flag, yellow is the default v5.3 pipeline 3.) axial_1353_norm2+3T_white -> The white surface, which appears OK using v5.3 with the suggested norm2 parameters and the -3T flag 4.) axial_1353_wusl_white_error -> the white surface, with an obvious error in the lh_postcentral area, using the -washu_mprage flag. Let me know if you have any suggestions on other parameters I should try to improve the temporal lobe pial surface, without compromising the white matter surface reconstruction. Sincerely, Las Message: 5 Date: Mon, 7 Jul 2014 11:14:25 -0400 (EDT) From: Bruce Fischl <fischl(a)nmr.mgh.harvard.edu> Subject: Re: [Freesurfer] Anterior Temporal Lobe / Pial Reconstruction Troubles To: Freesurfer support list <freesurfer(a)nmr.mgh.harvard.edu> Message-ID: <alpine.LRH.2.03.1407071114090.30923(a)nmr.mgh.harvard.edu> Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Hi Las can you send us a couple of images of the problems you are seeing? cheers Bruce On Mon, 7 Jul 2014, Las Blawimo wrote: > Dear FreeSurfer Experts, > > > We are collecting a 0.9mm isotropic FSPGR sequence on a GE MR750 3T scanner. > We're observing, in many subjects, a problem mentioned in previous posts to > the list where the pial surface does not follow the cortex properly in the > anterior temporal lobe region (and also in some frontal regions). The white > matter surface generally looks very good. This is with the default options > from recon-all in v5.3. > > We've also tried running the following options, based on previous posts > (expert options) and the release notes for version 5.2: > > -norm2-b 20 -norm2-n 5 > > and > > -norm2-b 20 -norm2-n 5 -3T > > In general, there is a modest improvement in the medial temporal lobe pial > surface in most subjects. A substantial/desired improvement is observed in > only a few subjects. In general, there was no detrimental effect to either > the white matter or pial surface when using these flags. > > Based on older posts to the list, we've also tried using the following > flags: > > -mprage > > and > > -washu_mprage > > The improvement to the pial surface is much more substantial in almost all > subjects, to some extent with the -mprage flag, mostly with the > -washu_mprage flag. However, this dramatic improvement in pial surface > accuracy was accompanied by many major issues with the white surface in > widespread areas across the brain. Also, some subjects fail to reconstruct > fully due to large defects in the surfaces with this option in place (also > something I've read about happening to people using the -washu otpion on the > list). > > A few questions: > > Would you suggest we also try the options "-norm1-b" and "-norm1-n" in > addition to the norm2 options? If so, any suggested starting values to try? > > Alternatively, would it be sensible to try to use the white surface from the > default pipeline and combine it with (or perhaps initialize) the pial > surface from the -washu_mprage flag? > > Do you have other suggestions for us to try? > > Thank you for your time and help! > > Sincerely, > > Las > >

1 0

mri_convert reads out k_ras from which dicom field
by Fan, Qiuyun 07 Jul '14

07 Jul '14

Dear Freesurfer experts, I used EicomEditor to anonymize the dicom header. When I run mri_convert on the anonymized dicom file, it sets k_ras as NaN. I checked the dcmdump results of both, and I couldn't figure out which fields were erased to cause that problem. I'm attaching the dcmdump info, and mri_convert outputs for more information. Any comments on how to debug this? For example, which field(s) in dicom header does the program read/calculate k_ras from? Thanks a lot! Best, Qiuyun

2 1

talairach fixes - when to do manual intervention
by Elissa McIntosh 07 Jul '14

07 Jul '14

Hello freesurfer experts, I have two questions. First, I've come across some of my subjects who have crooked alignment on the horizontal view, but have seemingly good talairach results. Does it matter that the alignment is crooked as long as talairach is good? My second question is how off does a talairach have to be to merit a manual fix? I've attached an image of someone whose talairach is slightly off making the green line go outside the brain more than it usually does. But I don't know if I'll do more harm by adjusting it slightly. On a related note, does it matter that the green line seems to go outside the brain in the moveable image? Where the green line extends beyond I've had to make manual edits in most of my subjects. Thank you!

1 0

problems with Surface-based Interhemispheric Registration
by angela.favaro＠unipd.it 07 Jul '14

07 Jul '14

Hi all, I have a problem with 'Surface-based Interhemispheric Registration' I followed the instructions and all seem to work, but the command: 'surfreg --s $subject --t fsaverage_sym --lh --xhemi' finish with the error below (indeed in the xhemi/label directory, there is no file) What can I do? Thank you for any help! Angela #@# Cortical Parc rh Mon Jun 30 17:44:52 CEST 2014 /Users/angelafavaro/Desktop/risonanze/studyfree/subj024/xhemi/scripts \n mris_ca_label -l ../label/rh.cortex.label -aseg ../mri/aseg.mgz -seed 1234 subj024/xhemi rh ../surf/rh.sphere.reg /Applications/freesurfer/average/rh.curvature.buckner40.filled.desikan_killiany.2010-03-25.gcs ../label/rh.aparc.annot \n No such file or directory mris_ca_label: could not open label file ../label/rh.cortex.label No such file or directory No such file or directory Darwin host-001.homenet.telecomitalia.it 10.8.0 Darwin Kernel Version 10.8.0: Tue Jun 7 16:33:36 PDT 2011; root:xnu-1504.15.3~1/RELEASE_I386 i386 recon-all -s subj024/xhemi exited with ERRORS at Mon Jun 30 17:44:52 CEST 2014

4 13

neonatal processing stream?
by Alexopoulos, Dimitrios 07 Jul '14

07 Jul '14

Several months ago someone mentioned the possibility of a neonatal processing stream. Is this in development, and if so is there an approximate time frame for release. Thanks Jim The materials in this email are private and may contain Protected Health Information. If you are not the intended recipient, be advised that any unauthorized use, disclosure, copying, distribution or the taking of any action in reliance on the contents of this information is strictly prohibited. If you have received this email in error, please immediately notify the sender via telephone or return email.

1 0

mris_divide_parcellation for white matter
by Corinna Bauer 07 Jul '14

07 Jul '14

hello, I was wondering if it was possible to use mris_divide_parcellation on white matter labels. Thanks, Corinna

3 13

longitudinal freesurfer error
by Salil Soman 07 Jul '14

07 Jul '14

Hi, I have followed the steps in the longitudinal qdec tutorial ( https://surfer.nmr.mgh.harvard.edu/fswiki/LongitudinalTwoStageModel) but when I try to analyze longitudinal features such as long.thickness-rate I get an error: Error in analyze: Couldn't open /SUBJECTS_DIR/SUBJECT_ID/surf/lh.long.thickness-rate.fwhm10.fsaverage.mgz or .mgh file Any suggestions on what I am doing incorrectly? Best wishes, Sal -- Salil Soman, MD, MS Postdoctoral Research Fellow - Stanford Radiological Sciences Laboratory Fellow - Palo Alto War Related Illness and Injury Study Center WOC Neuroradiology Attending - Veterans Affairs Palo Alto Health Care System

2 1

how to edit extracted masks
by Brianna Damadian 07 Jul '14

07 Jul '14

Hello, I used the mri_label2vol command to extract my aseg.mgz to patient native space (output=aseg-in-rawavg.mgz). I then used the mri_extract_label command as follows to create a mask of the ventricles: mri_extract_label aseg-in-rawavg.mgz 4 5 14 15 43 44 72 ventricles.img When I open this mask on top of the rawavg.mgz volume to look at quality, it seems there are some pieces that are clearly ventricle missing from the mask (see attached). Is there a way to edit this mask or the segmentation to include those areas in the ventricle mask as well as the segmentation volume output for the ventricles? Thanks, Brianna

1 0

Problem of Volumes differ in dimension in Longitudinal pipeline
by wang kangcheng 07 Jul '14

07 Jul '14

Dear experts Today, I conduct the longitudinal analysis according to tutorials of freesurfer (https://surfer.nmr.mgh.harvard.edu/fswiki/LongitudinalProcessing) But, when I do recon-all -base <templateid> -tp <tp1id> -tp <tp2id> ... -all, it report the error: --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- mri_diff --notallow-pix /Users/wangkangcheng/Desktop/long_fs_test/long/s12002_MRI2/mri/rawavg.mgz /Users/wangkangcheng/Desktop/long_fs_test/long/s12002_MRI1/mri/rawavg.mgz \n Volumes differ in dimension v1dim 176 256 256 1 v2dim 176 184 200 1 \n******************************************************************************* WARNING: Image geometries differ across time, maybe due to aquisition changes? This can potentially bias a longitudinal study! Will continue in 10s. ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- When I check the raw data and find that the structural data of s12002_MRI1 was the file which was converted by the command of dcm2nii and begin with "co". However, data of s12002_MRI2 was the file which begin with "o". But, when I used the file which begin with "co", they did not have same dimension. How could I solve the problem? (PS: have processed hundreds of data for subject of MRI1) Thank you Wang Kangcheng

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