Freesurfer June 2018

freesurfer@nmr.mgh.harvard.edu

105 participants
154 discussions

mri_vol2surf: dACC/Insula clusters on surface not found
by srishti goel 05 Jul '18

05 Jul '18

External Email - Use Caution Hello, I am using mri_vol2surf to project my volume maps on to the surface. There is a dACC/insula cluster visible in my volume maps that doesn't show up when I project it on the surface. Is that because dACC/insula is not included in surfaces on Freesurfer? Thanks! Best, Srishti Social/Clinical Research Specialist Child Imaging Research and Life Experiences Lab University of North Carolina at Chapel Hill email (W): srishtig(a)email.unc.edu skype: srishti.goel12

3 7

Longitudinal processing in v6.0 using manual edits from v5.3.0 - recon-all.log
by KALEY E ELLIS 04 Jul '18

04 Jul '18

External Email - Use Caution Hello FreeSurfer experts, I previously emailed regarding processing longitudinal data in v6.0 using bases with manual edits that had been completed in v5.3. I went ahead and ran recon-all -all on the base of a subject (originally generated in v5.3) in v6.0, but it looks like the header of the recon-all.log still indicates v5.3. Looking at the /stats output, all files indicate v6.0. Below is the head of the log from running recon-all -all on this subject. Is this what you would expect if you ran recon-all -all on a subject_base in v6.0 that was generated in v5.3? If so, is this okay? Recon-all log: setenv SUBJECTS_DIR /study1/nccam3/data/mri/freesurfer_v6/subjects FREESURFER_HOME /apps/x86_64_sci7/freesurfer-latest Actual FREESURFER_HOME /apps/freesurfer-5.3.0/x86_64_sci6 build-stamp.txt: freesurfer-Linux-centos6_x86_64-stable-pub-v5.3.0 Linux c139.keck.waisman.wisc.edu 3.10.0-514.6.1.el7.x86_64 #1 SMP Tue Jan 17 11:12:41 CST 2017 x86_64 x86_64 x86_64 GNU/Linux Thank you! Kaley Ellis Associate Research Specialist Center for Healthy Minds Waisman Center for Brain Imaging and Behavior University of Wisconsin-Madison

2 1

Longitudinal processing: cannot find input volume error
by Arsenije Subotic 04 Jul '18

04 Jul '18

External Email - Use Caution Dear Freesurfer experts, I’m having problems with one of my participants when I am trying to create the base template for my longitudinal analysis. I get an error saying that the input volume (norm.mgz) for my followup time-point cannot be opened, even though the volume is not missing and loads perfectly fine in Freeview. Is this a bug or is something wrong with my norm.mgz volume by any chance? Please let me know. Thank you, Arsenije

2 1

Longitudinal analysis of multiple scanner acquisitions
by zalewk 04 Jul '18

04 Jul '18

External Email - Use Caution Good afternoon Freesurfer team, I want to run the longitudinal pipeline on multiple groups of subjects, the problem is we are at the mercy of the scanners available to us at the various time-points. We have two different Siemens 1.5 scanners (same type of scanner, there was an effort made to match them) at time point 1 and 2 with a Phillips 3T at time point 3. Is it worth the time to attempt a longitudinal analysis on this cohort? Best, Kody Zalewski

2 1

Longitudinal errors, Voxel size differs
by Erik O'Hanlon 04 Jul '18

04 Jul '18

External Email - Use Caution Hi FS Experts, I'm trying to run a longitudinal analysis across three timepoints and have run the cross steps for the data. I then ran the base step but found that my voxel dimensions are slightly different across the timepoints and I got the following error ERROR: MultiRegistration::loadMovables: images have different voxel sizes. Currently not supported, maybe first make conform? Debug info: size(2) = 0.881117, 0.881117, 0.881117 size(0) = 0.884507, 0.884507, 0.884507 MultiRegistration::loadMovables: voxel size is different /projects/pi-vokeane/HPC_16_00925/MC_FS_testdata_EOH/freesurfer/subjects/abd025_tp3/mri/norm.mgz. I assume I need to resample the data to the voxel size of the first time point and then rerun. Can you advise on what command to use to resample the images from time 2 and time 3 to those of time 1 before rerunning from scratch. I assume I can't avoid rerunning the initial reconall step once I resample my data. Any guidance is much appreciated Best regards Erik Erik O'Hanlon Postdoctoral researcher [cid:rcsi-crest-signature_f581c185-1d03-45c8-a786-23d8ece3d391.png] RCSI Psychiatry Royal College of Surgeons in Ireland Beaumont Road, Beaumont D9 Ireland T: 8093740 E: erikohanlon(a)rcsi.ie W: www.rcsi.com<http://www.rcsi.com/> Transforming Healthcare Education, Research and Service: RCSI Strategic Plan 2018-2022<http://www.rcsi.ie/strategy2018> RCSI DEVELOPING HEALTHCARE LEADERS WHO MAKE A DIFFERENCE WORLDWIDE [cid:both3_b9da8717-e91f-4ea7-8729-dc2c4d0a7a5f.png]

2 4

Longitudinal Process
by Samir Rekic 04 Jul '18

04 Jul '18

External Email - Use Caution Dear FreeSurfers, I am trying to run the longitudinal process including (recon-all -base and -long) for 5 different timepoints. But in my original data one the of five differs in the acquisition orientation and in the size of the field of view, so the results and especially the statistic is distorted. Four of my data sets have RPI as acquisition Parameter and a FOV of 230, the last data set has LPI and a FOV of 257. Does it even make sense to include this last dataset – is it even possible (due to different Parameters)? Do I have to pre-process this different data set? Thank you in advance! Sam

2 1

"WARNING: Image geometries differ across time" upon running base step of longitudinal pipeline
by Tudor Popescu 04 Jul '18

04 Jul '18

External Email - Use Caution Dear all, I have pre and post-intervention data for a single group of subjects, and I'd like to extract the cortical thickness pre and post, for all standard regions in the atlas, and use those in subsequent analyses. Following the standard approach <https://surfer.nmr.mgh.harvard.edu/fswiki/LongitudinalProcessing#Longitudin…>for longitudinal studies, I used the following types of commands: 1. *recon-all -i 01_1.nii.gz -subjid 01_1 recon-all -i 01_2.nii.gz -subjid 01_2 recon-all -i 02_1.nii.gz -subjid 02_1 .. where e.g. 01 is the subj code, and _1 and _2 represent pre and post scans* 2. *recon-all -subjid 01_1 -all recon-all -subjid 01_2 -all ..* 3. *recon-all -base 01 -tp 01_1 -tp 01_2 -all .. * 4. *recon-all -long 01_1 01 -all recon-all -long 01_2 01 -all .. * However, the base step has led to warnings of the type: "WARNING: Image geometries differ across time, maybe due to aquisition changes? This can potentially bias a longitudinal study! ", and consequently to an empty /stats folder -- even though my pre and post images are aligned and have similar acquisition parameters. Have I done something wrong, and how can I fix this warning/error? Many thanks in advance for any help. Best wishes, Tudor

3 7

Geometries-related error from base step & absent norm.mgz
by Tudor Popescu 04 Jul '18

04 Jul '18

External Email - Use Caution Dear FS list, ( Apologies for asking my question again which I am still struggling to resolve and which I tried to clarify and condense below. ) I have pre and post-intervention data for a single group of subjects, and I'd like to extract the cortical thickness at both timepoints, for all standard regions in the atlas. I followed the standard approach <https://surfer.nmr.mgh.harvard.edu/fswiki/LongitudinalProcessing#Longitudin…>for longitudinal studies, however the third ('base') step immediately gives this error: *"WARNING: Image geometries differ across time, maybe due to aquisition changes? This can potentially bias a longitudinal study! "* I don't think the acquisition parameters of the pre-post images actually differ: I could verify that all images indeed have - identical voxel size (1x1x1) - identical image size (176x224x160) - a (0,0,0) point that overlaps well-enough on the anterior commissure This suggests trivial (if any) "geometry" differences, and at Bruce's suggestion, I used mri_convert to resample each subject's 'post' to their 'pre' baseline: mri_convert -rl 01_1.nii.gz 01_2.nii.gz 01_2resampled.nii.gz (and renamed the resampled file to 01_2). However, the base step, recon-all -base 01 -tp 01_1 -tp 01_2 -all still gives the same error about geometries, and also in addition, this one: mghRead(/media/FS/01_1/mri/norm.mgz, -1): could not open file MultiRegistration::loadMovables: could not open input volume /media/FS/01_1/mri/norm.mgz. Inside /media/FS/01_1/mri/ (where /media/FS is my $SUBJECTS_DIR), there is indeed no norm.mgz, which suggests something in my previous commands for subject1: recon-all -i 01_1.nii.gz -subjid 01_1 recon-all -i 01_2.nii.gz -subjid 01_2 recon-all -subjid 01_1 -all recon-all -subjid 01_2 -all ..had gone wrong despite these having produced no errors. Although I thought the base step already does autorecon1 as part of the longitudinal pipeline, I tried doing it manually: recon-all -autorecon1 -subjid 01 however this returns: ERROR: It appears that this subject ID is an existing base/template from longitudinal processing (-base). Please make sure you pass all necessary flags. For example, if you are trying to re-run a -base: \' -base <templateid> -tp <tpNid> ... \' ..whereas running autorecon1 and 2 for the first *timepoint *instead, recon-all -autorecon1 -autorecon2 -subjid 01_1 returns mri_em_register: could not open input volume nu.mgz Should I in fact use, in mri_convert -rl , a *single *target for all the pre&post images in the study, like the study-specific template <https://fsl.fmrib.ox.ac.uk/fsl/fslwiki/FSLVBM/UserGuide#C_-_Creating_the_te…> used by VBM? Or what else can I try to get the base step to continue? I'm very grateful for any suggestions! Cheers, Tudor

1 2

MRI2MESH Yielding Abnormal Volumes
by Palig Mouradian 03 Jul '18

03 Jul '18

External Email - Use Caution Hi Freesurfer, I am working on creating head models using the add-on mri2mesh command that incorporates free surfer. Once I have my mesh, I view it in SCIRUN to see how each surface was modeled. First time through, I noticed white matter abnormalities and that the nasopharynx was being included into the CSF. I did free surfer QC—edited the pial boundary and reran the mri2mesh command, I was successful in eliminating the WM abnormality but it has results in a ballooning of the CSF and skin surface (see attached). My main question is where can I attenuate this abnormality? Is it a result of my edits to the pial boundary? Thank You! Sincerely, Palig Mouradian

2 1

mri_glmfit for first level ?
by Evelyn Eger 03 Jul '18

03 Jul '18

External Email - Use Caution Dear Freesurfer experts, I would like to know whether mri_glmfit can be used to estimate first-level (single subject) models as well or whether it is clearly not intended/recommended for that. I have noticed that it allows to specify a design matrix explicitly and I used the one previously configured in SPM, estimated the individual subject models on the surface and got reasonable results. Then after reading a bit more I gathered that this function is usually used for second-level analyses, and that my models are lacking the temporal autocorrelation correction and do not take into account additional drift terms as one would usually do. I noticed however that there is as well the possibility to compute and save the temporal AR1 with the --tar1 option, but I do not understand how this is taken into account afterwards. Would I get a proper first-level model by activating the --tar1 option and potentially adding additional drift terms to my design matrix myself, or would there be still remaining issues and the models should better be redone completely with selxavg3-sess (which seems a bit more complicated because the data were not organized in the required way from the start)? Thanks a lot in advance, Evelyn -- Dr Evelyn Eger INSERM Cognitive Neuroimaging Unit Neurospin - CEA Saclay F-91191 GIF/YVETTE, FRANCE Tél : 33 (0)1 69 08 19 06 Fax : 33 (0)1 69 08 79 73

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 June 2018