Freesurfer

freesurfer@nmr.mgh.harvard.edu

19 participants
30088 discussions

QDEC thickness data to table
by Alexandru Hanganu 12 Jul '11

12 Jul '11

Dear Freesurfer experts, In the QDEC plot there is the possibility to view cortical thickness for each subject in a specific region. Is there a possibility to make an automatic table of all these thickness data ? In a previous question, the answer was to use a script: =========================== # Script created December 2007 by Pedro Paulo Jr. # Use with Freesurfer 4.x # Updated: 24/03/2010 set FSAVERAGE_DIR = "usr/local/freesurfer/subjects/fsaverage" cd /usr/local/freesurfer/subjects/qdec/QDEC-DATA set numsubject = 17 for i in 'seq 1 $numsubject' do mri_convert --frame $i y.mgh $FSAVERAGE_DIR/surf/lh.$i.mgh mris_convert -c $i.mgh $FSAVERAGE_DIR/surf/lh.inflated lh.$i.asc done =========================== But that script doesn't work in tcsh, so we changed the cmd line: =========================== foreach i in (`seq 1 $numsubject`) mri_convert --frame $i y.mgh $FSAVERAGE_DIR/surf/lh.$i.mgh mris_convert -c $i.mgh $FSAVERAGE_DIR/surf/lh.inflated lh.$i.asc end =========================== But we still receive error. Can you please help us ? (we use FS 5.1, Centos4_x86_64) Thank you in advance, Sincerely, Alex. * *

1 0

mri_convert and orientation
by Yang Liu 12 Jul '11

12 Jul '11

Hi all, I have a nifti file f.nii whose size is 80*80*60*266, (266 is the TRs). Using "mri_info f.nii", I can see that its orientation is is PIL. I want to change it to RPI. I do the following: "mri_conver --in_orientation PIL --out_orientation RPI -i f.nii -o f.rpi.nii" It give me f.rpi.nii, which has an orientaion of RPI. The problem is that f.rpi.nii is 80*80*60. It contains only one volume. How can I get a reoriented volume that has the same size as the original 80*80*60*266? Many thanks. Yang

1 0

New version and workflow
by Myriam Siefert 11 Jul '11

11 Jul '11

Hello Freesurfer users and experts, We already run 55 subjects with Freesurfer 5.0 and wish now to increase our sample size up to 200 and are now deciding whether to run everybody again with Freesurfer 5.1 or just go on with the previous version. We are doing subcortical analysis (amygdala) and hopefully cortical analysis (correlations with behavioural results), on Siemens 3T. I have 2 questions relative to this issue : - To what extend should the results be more accurate or reliable (I read in the release note that 3T data is now better handled) ? I run 3 subjects on boths versions and compared aseg stats, most results were very close except for a few that were highly discrepant (ex left amygdala and hippocampus for 1 subject were much smaller with FS 5.1). What could explain this? - I also noticed on the web site that the recommended workflow had been updated. Is this linked to the new release (if less or no editing is needed, checking the output only after recon-all -all would obviously save time...)? Is less need for editing expected with the new release? Or is less editing now advised ("Less is more")? Thanks in advance for any advice! Myriam Siefert

2 1

Fw: Multiple frames error
by Antonella Kis 11 Jul '11

11 Jul '11

HiBruce, I 1). My LNX3 the only one which is working is a Fedora Linux, Kernel Linux 2.6.32.23-170.fc12.x86_64, GENOME 2.28.2 LNX2 where I get the weird surface display is a Linux CENTOS x86_64, GENOME 2.16.0 The Analyst computer where I got the multiple frames error is a Linux, Kernel Linux 2.6.35.13-91.fc14.x86_64, GENOME 2.32.0 2). Also, when I am doing my data analysis after running the recon -all and qcache -all for my subjects, what is the best steps order to be followed. While reading the FreeSurfer Troubleshooting Reconstruction Work suggests the user to run all these steps at once before beginning to inspect the data since this allows the user to see the final complete output before deciding on any interventions.But this steps are in a different order that the one in the tutorial and also in a different order that the one described in the attached document. 8. Check the segmentations - After editing the wm.mgz volume run the following steps: -normalization -maskbfs -segmentation -autorecon2-wm -autorecon3. Thank you for your help! Antonella

3 2

Creation of normalized cortical regions of interest
by 汪贵宏 11 Jul '11

11 Jul '11

Hi,freesurfers: Recently,I read a paper which used freesurfer to processed their data,this is the paper's link:http://www.plosbiology.org/article/info%3Adoi%2F10.1371%2Fjournal.pbio… In this paper,the antor said : "One of the critical steps of the whole procedure was to partition the participants' cortex into ROIs located in an identical topographic position for each participant despite interindividual anatomical variation. We used Freesurfer to register a labeled mesh from an average brain onto the brain of each individual participant, where each label corresponded to one of 66 anatomical cortical regions . This output provided for every participant a standardized partition of the cortex into 66 regional areas. In a second step, each of these regional areas were subdivided on the Freesurfer average brain into a set of small and compact regions of about 1.5 cm2, resulting in 998 ROIs covering the entire cortex. This subdivision was then registered on the individual brain using the same transformation as for the 66 regional areas thus maintaining the topological constraints of mapping. Consequently, the resulting partitions of the cortex into 66 and 998 ROIs were in anatomically closely matched positions for all participants " So,I wander how can we subdivided the 66 ROIs into 998 ROIs? Thanks, wang

2 1

Nipype 0.4 release
by Chris Filo Gorgolewski 11 Jul '11

11 Jul '11

Dear all, I am delighted to announce release of Nipype version 0.4. Nipype, an open-source, community-developed initiative under the umbrella of NiPy, is a Python project that provides a uniform interface to existing neuroimaging software and facilitates interaction between these packages within a single workflow. Nipype provides an environment that encourages interactive exploration of algorithms from different packages (e.g., SPM, FSL, FreeSurfer, Camino, AFNI, Slicer), eases the design of workflows within and between packages, and reduces the learning curve necessary to use different packages. Nipype is creating a collaborative platform for neuroimaging software development in a high-level language and addressing limitations of existing pipeline systems. This release brings plenty of improvements. Among the most important are: new modular executions system (direct support for PBS, SGE, and multi-processing), support for Camino, Camino2Trackvis and Connectome Viewer, improved parallel performance of MapNode, and growing collection of ready to use pipelines (have a look at nipype.workflows). Grab it from https://github.com/nipy/nipype/tarball/0.4 For support please use our mailing list: nipy-users(a)googlegroups.com Full changelog: * API: Timestamp hashing does not use ctime anymore. Please update your hashes by running workflows with updatehash=True option NOTE: THIS IS THE DEFAULT CONFIG NOW, so unless you updatehash, workflows will rerun * API: Workflow run function no longer supports (inseries, createdirsonly). Functions used in connect string must be pickleable * API: SPM EstimateContrast: ignore_derivs replaced by use_derivs * API: All interfaces: added new config option ignore_exception * API: SpecifModel no longer supports (concatenate_runs, output_specs). high_pass_filter cutoff is mandatory (even if its set to np.inf). Additional interfaces SpecifySPMModel and SpecifySparseModel support other types of data. * API: fsl.DTIFit input "save" is now called "save_tensor" * API: All inputs of IdentityInterfaces are mandatory by default. You can turn this off by specifying mandatory_inputs=False to the constructor. * API: fsl FILMGLS input "autocorr_estimate" is now called "autocorr_estimate_only" * API: fsl ContrastMgr now requires access to specific files (no longer accepts the result directory) * API: freesurfer.GLMFit input "surf" is now a boolean with three corresponding inputs -- subject_id, hemi, and surf_geo * ENH: All commandline interfaces display stdout and stderr * ENH: All interfaces raise exceptions on error with an option to suppress * ENH: Supports a plugin interface for execution (current support for multiprocessing, IPython, SGE, PBS) * ENH: MapNode runs in parallel under IPython, SGE, MultiProc, PBS * ENH: Optionally allows keeping only required outputs * ENH: New interface: utility.Rename to change the name of files, optionally using python string-formatting with inputs or regular expressions matching * ENH: New interface: freesurfer.ApplyMask (mri_mask) * ENH: New FSL interface -- SwapDimensions (fslswapdim) * ENH: Sparse models allow regressor scaling and temporal derivatives * ENH: Added support for the component parts of FSL's TBSS workflow (TBSSSkeleton and DistanceMap) * ENH: dcm2nii interface exposes bvals, bvecs, reoriented and cropped images * ENH: Added several higher-level interfaces to the fslmaths command: - ChangeDataType, Threshold, MeanImage, IsotropicSmooth, ApplyMask, TemporalFilter DilateImage, ErodeImage, SpatialFilter, UnaryMaths, BinaryMaths, MultiImageMaths * ENH: added support for networx 1.4 and improved iterable expansion * ENH: Replaced BEDPOSTX and EddyCurrent with nipype pipelines * ENH: Ability to create a hierarchical dot file * ENH: Improved debugging information for rerunning nodes * ENH: Added 'stop_on_first_rerun' option * ENH: Added support for Camino * ENH: Added support for Camino2Trackvis * ENH: Added support for Connectome Viewer * BF: dcm2nii interface handles gzipped files correctly * BF: FNIRT generates proper outputs * BF: fsl.DTIFit now properly collects tensor volume * BF: updatehash now removes old result hash file Enjoy! Chris Gorgolewski on behalf of Team Nipype ( https://www.ohloh.net/p/nipype/contributors )

1 0

V1 dimensions
by Ritobrato Datta 11 Jul '11

11 Jul '11

Hello All, Is there a way to calculate the length and breadth of V1 in mm defined by the Fischl method ? How do I do it ? Thanks Ri

1 0

interpolation during conform step of oblique acquisitions
by Michael Harms 11 Jul '11

11 Jul '11

Hi guys, I'm curious why the conform step of mri_convert (in generating mri/orig.mgz) automatically interpolates oblique acquisitions. Is this a historical legacy? Something mandated by other elements of the FS pipeline? As a consequence of this behavior, if you have an oblique acquisition that was intentionally aligned to the actual anatomy of a given subject's brain (e.g., using AutoAlign to generate a AC-PC aligned acquisition), unless one manually alters the qform in the input NIFTI file to remove the "oblique" components of the xform, there will be an interpolation in the generation of the mri/orig.mgz, which brings with it blurring (i.e., the same sort of concerns that prompt one to use a single MPRAGE, rather than the average of two MPRAGEs) Just curious... thanks, -MH -- Michael Harms, Ph.D. -------------------------------------------------------------------- Conte Center for the Neuroscience of Mental Disorders Washington University School of Medicine Department of Psychiatry, Box 8134 Renard Hospital, Room 6604 Tel: 314-747-6173 660 South Euclid Ave. Fax: 314-747-2182 St. Louis, MO 63110 Email: mharms(a)wustl.edu --------------------------------------------------------------------

2 2

Brain Volume in FreeSurfer5.1
by Justin Eisenberg 11 Jul '11

11 Jul '11

Hi Fellow FreeSurfers, How do you calculate Brain Volume in FS5.1? In 4.5 there was the BrainSegNotVent statistic in aseg.stats, but I'm not seeing that in 5.1. I did find something about the SupraTentorialVol, but that would exclude the brainstem and cerebellum. I'm not sure if that also includes the ventricles, but that would need to be factored in as well. I did some math to compare values between 4.5 and 5.1. I took the SupraTentorialVol from 5.1, added Left-Cerebellum-White-Matter, Left-Cerebellum-Cortex, Right-Cerebellum-White-Matter, Right-Cerebellum-Cortex, and Brain-Stem. I then subtracted out the ventricles (Left/Right-Lateral-Ventricle, Left/Right-Inf-Lat-Vent, 3rd/4th/5th-Ventricle). The end result of my 5.1 volume is 51,429 voxels larger than the value from 4.5. Thanks in advance Justin -- Justin Eisenberg Candidate for B.A. in Biology | 2013 Washington University in St. Louis JEisenberg(a)wustl.edu 262.914.4648

1 0

fscalc size mismatch error
by Corinna Bauer 11 Jul '11

11 Jul '11

When running fscalc, I get the following error on some of my subjects but not all of them, mris_calc: Sorry, but I seem to have encountered an error. While checking on input filetype sizes, I found a size mismatch, i.e. len(input1)!=len(input2) Any suggestions? Thanks, Corinna

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