Freesurfer

freesurfer@nmr.mgh.harvard.edu

4 participants
30090 discussions

longitudinal generic-time and spc
by Kasper Jessen 23 Aug '17

23 Aug '17

Dear Freesurfer, The following is a follow-up, on a previous discussion (http://www.mail-archive.com/freesurfer@nmr.mgh.harvard.edu/msg51582.html) but i am still left with some uncertain and unanswered questions. My design: Patients and Controls, MRI scanned at baseline and after 6 weeks (only two time points). The average follow-up time is about 7 weeks when using the exact time. 1) I understand that the if you pass the --generic-time in the long_stats_slopes command, the 'time' column should not be in the qdec table as it assumes the values are 1,2,3,4 (subjects are ordered in TP1, TP2). However, if there is an exact time, then a 'time column' should be in the qdec table and the --generic-time should not be passed in the long_stats_slopes command. Is this correct? 2) If the exact time is not present, how is the symmetrized precent change calculated? Since it is calculated spc = 100 * rate / avg, and rate is calculated: rate = ( thick2 - thick1 ) / (time2 - time1) then there must be a time right? Thanks in advance. I hope some of you have find the time to help :-) I am a little stuck with these details. Best regards, Kasper Sent from [ProtonMail](https://protonmail.com), Swiss-based encrypted email.

2 1

Error after manual edits in freesurfer 6
by Chethana 23 Aug '17

23 Aug '17

To, The Freesurfer experts, I am analysing a set of MRI images in freesurfer 6. In the step 1 of freesurfer data processing the dura and skull are stripped and during the process of inspection with manual edits of the aux volume if I save the progress and reopen the same image for review they appear very brightly intense and unable to differentiate grey from white matter. Attaching two pictures for the same the first picture is without saving The second brightly intense picture attached is when the edit is opened for review after saving the volume where the grey white matter differentiation is difficult to see Can you kindly suggest how do I rectify this error or any other solution for the same? Thanks and regards Chethana

2 1

Hard failure via XNAT pipeline (Freesurfer 6)
by Rockers, Elijah D. 23 Aug '17

23 Aug '17

We encountered a hard failure, below is the tail of the log. We are currently running Freesurfer 6 again locally to see if it succeeds on a desktop machine (this is the first time encountering a hard failure on the XNAT server). Any suggestions? -merging segment 180 into 178 160 defects to be corrected 0 vertices coincident reading input surface /data/build/nnac/20170818_114535/alamode_MRI08162017/20170818114538/alamode_MRI08162017/surf/lh.qsphere.nofix... reading brain volume from brain... reading wm segmentation from wm... Computing Initial Surface Statistics -face loglikelihood: -8.7982 (-4.3991) -vertex loglikelihood: -6.2982 (-3.1491) -normal dot loglikelihood: -3.5611 (-3.5611) -quad curv loglikelihood: -6.1931 (-3.0965) Total Loglikelihood : -24.8505 CORRECTING DEFECT 0 (vertices=40706, convex hull=11265, v0=89) XL defect detected... Segmentation fault (core dumped) Linux hhvrixnatp01 2.6.32-431.el6.x86_64 #1 SMP Sun Nov 10 22:19:54 EST 2013 x86_64 x86_64 x86_64 GNU/Linux recon-all -s alamode_MRI08162017 exited with ERRORS at Mon Aug 21 19:27:09 CDT 2017 To report a problem, see http://surfer.nmr.mgh.harvard.edu/fswiki/BugReporting Houston Methodist. Leading Medicine. Houston Methodist is ranked by U.S. News & World Report as the No. 1 hospital in Texas for patient care. Houston Methodist is nationally ranked in 8 specialties and is designated as a Magnet hospital for excellence in nursing. Visit us at houstonmethodist.org. Follow us at twitter.com/MethodistHosp and facebook.com/HoustonMethodist. ***CONFIDENTIALITY NOTICE*** This e-mail is the property of Houston Methodist and/or its relevant affiliates and may contain restricted and privileged material for the sole use of the intended recipient(s). Any review, use, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the sender and delete all copies of the message. Thank you.

2 1

Re: [Freesurfer] hippocampal and amygdalar subregional segmentation
by Iglesias Gonzalez, Eugenio 23 Aug '17

23 Aug '17

Hi Moji: 1. Absolutely. You can use standard FreeSurfer tools for extracting masks from a segmentation, resample them to whatever space, etc. 2. A lot of people have been making this question, so we’re now writing a bunch of merged segmentations to the mri directory of the subjects for convenience. If none of these groupings satisfies you, it is always possible to use standard FreeSurfer tools to do this. 3. Yes, the new atlas includes the nuclei of the amygdala (Saygin, Kliemann et al, NeuroImage, 2017). Features 2 and 3 will be available in the dev version in the next few days; stay tuned! Cheers, /Eugenio -- Juan Eugenio Iglesias ERC Senior Research Fellow Translational Imaging Group University College London http://www.jeiglesias.com http://cmictig.cs.ucl.ac.uk/ From: <freesurfer-bounces(a)nmr.mgh.harvard.edu> on behalf of "Aghajani, Moji" <m.aghajani(a)vumc.nl> Reply-To: Freesurfer support list <freesurfer(a)nmr.mgh.harvard.edu> Date: Wednesday, 23 August 2017 at 12:14 To: "freesurfer(a)nmr.mgh.harvard.edu" <freesurfer(a)nmr.mgh.harvard.edu> Subject: [Freesurfer] hippocampal and amygdalar subregional segmentation Dear Freesurfer Developers, I have some questions regarding hippocampal and amygdalar subregional segmentation in the latest Freesurfer version: 1) Can one use the segmentation outputs as ROI masks, register those to native space functional image, and extract functional time courses in order to perform seed-based subregional functional connectivity analyses? 2) How sensible do you deem it to assess the functional connectivity profiles of all the subregions? Would you argue against grouping some of the subregions into a larger subregion and assess connectional profiles. For instance combining CA 1 to 4 into a CA subgroup? Or the Subiculum and Pre- Parasubiculum into one subgroup? I am asking this because most literature on hippocampal subregional connections focuses on the major subregions (CA, Dentate Gyrus, Subiculum), with very limited knowledge on connectivity profiles of smaller individual subregions. 3) Is it already possible to segment the amygdala subregions as well with this new pipeline? On the Freesurfer website the following is stated: “In addition to the hippocampal subregions, it also simultaneously segments the nuclei of the amygdala”. However, the page also states that this functionality will soon be available in the dev version, so I am not sure whether the amygdala subregional segmentation pipeline is already in place? If not, is there a preliminary release date known already? Thanks for your time and effort!

1 0

hippocampal and amygdalar subregional segmentation
by Aghajani, Moji 23 Aug '17

23 Aug '17

Dear Freesurfer Developers, I have some questions regarding hippocampal and amygdalar subregional segmentation in the latest Freesurfer version: 1) Can one use the segmentation outputs as ROI masks, register those to native space functional image, and extract functional time courses in order to perform seed-based subregional functional connectivity analyses? 2) How sensible do you deem it to assess the functional connectivity profiles of all the subregions? Would you argue against grouping some of the subregions into a larger subregion and assess connectional profiles. For instance combining CA 1 to 4 into a CA subgroup? Or the Subiculum and Pre- Parasubiculum into one subgroup? I am asking this because most literature on hippocampal subregional connections focuses on the major subregions (CA, Dentate Gyrus, Subiculum), with very limited knowledge on connectivity profiles of smaller individual subregions. 3) Is it already possible to segment the amygdala subregions as well with this new pipeline? On the Freesurfer website the following is stated: “In addition to the hippocampal subregions, it also simultaneously segments the nuclei of the amygdala”. However, the page also states that this functionality will soon be available in the dev version, so I am not sure whether the amygdala subregional segmentation pipeline is already in place? If not, is there a preliminary release date known already? Thanks for your time and effort!

1 0

Error after manual edits in freesurfer 6
by Chethana 23 Aug '17

23 Aug '17

To, The Freesurfer experts I am analysing a set of MRI images in freesurfer 6. In the step 1 of freesurfer data processing the dura and skull are stripped and during the process of inspection with manual edits of the aux volume if I save the progress and reopen the same image for review they appear very brightly intense and unable to differentiate grey from white matter. Attaching two pictures for the same the first picture is without saving The second brightly intense picture attached is when the edit is opened for review after saving the volume where the grey white matter differentiation is difficult to see Can you kindly suggest how do I rectify this error or any other solution for the same? Thanks and regards Chethana

1 0

Re: [Freesurfer] FW: CNDA update: Processing failed for SD10013_1
by Iglesias Gonzalez, Eugenio 22 Aug '17

22 Aug '17

Dear Allison, The error happened in the old hippocampal subfield module. I would recommend that you used the new hippocampal subfield code in FreeSurfer 6.0. Having said that, if you really want to run the 5.3 subfield version, Koen Van Leemput maybe knows what the problem might have been. Kind regards, /Eugenio -- Juan Eugenio Iglesias ERC Senior Research Fellow Translational Imaging Group University College London http://www.jeiglesias.com http://cmictig.cs.ucl.ac.uk/ From: <freesurfer-bounces(a)nmr.mgh.harvard.edu> on behalf of "Chen, Allison" <allisonchen(a)wustl.edu> Reply-To: Freesurfer support list <freesurfer(a)nmr.mgh.harvard.edu> Date: Tuesday, 22 August 2017 at 21:06 To: "freesurfer(a)nmr.mgh.harvard.edu" <freesurfer(a)nmr.mgh.harvard.edu> Subject: [Freesurfer] FW: CNDA update: Processing failed for SD10013_1 Hello Team, I have run ”recon-all args -qcache -all -hippo-subfields” command, but there are some errors. I used freesurfer 5.3 on CNDA: https://cnda.wustl.edu Attached and below are the error information. There is no any problem with our image. Could you give me any suggestions? Thanks a lot! Allison From: cnda-ops(a)nrg.wustl.edu [mailto:cnda-ops@nrg.wustl.edu] Sent: Thursday, August 17, 2017 9:21 PM To: Chen, Allison; cnda-ops(a)nrg.wustl.edu Subject: CNDA update: Processing failed for SD10013_1 The pipeline Freesurfer 5.3 encountered an error. * User: achen<mailto:allisonchen@wustl.edu> * Project: MEDEX * Experiment: SD10013_1 * Pipeline Step: RUN_FS The CNDA technical team is aware of the issue and will notify you when it has been resolved. We appreciate your patience. Please contact cnda-ops(a)nrg.wustl.edu with questions or concerns. The stdout and stderr log files are attached. PIPELINE PARAMETERS qc_rating 1 workdir builddir/SD10013_1 logdir workdir/LOGS XNAT_CSRF 7790fecf-8edf-41cc-8b26-caadb8150e06 email_csv_in cnda-ops(a)nrg.wustl.edu<mailto:cnda-ops@nrg.wustl.edu> freesurfer_subjectdir workdir/PROCESSED/SD10013_1 rawdir workdir/RAW id CNDA_E162884 paramsFile workdir/LOGS/SD10013_1.bashparams tempdir workdir/temp qc_rating_scale ' scan_ids [3] recon_all_args -qcache -all -hippo-subfields freesurferdir workdir/PROCESSED adminemail cnda-ops(a)nrg.wustl.edu<mailto:cnda-ops@nrg.wustl.edu> host https://cnda.wustl.edu/ relaunch false use_manual_qc 0 assessorId CNDA_E162884_freesurfer_20170817112729 label SD10013_1 format DICOM workflowid 6438524 freesurfer_tempdir workdir/PROCESSED/temp project MEDEX builddir /data/CNDA/build/MEDEX/20170817_112717/restlaunch u 2be260df-0fcb-4dda-9cdc-1ae13d9f02bd pwd ******** environment LOCAL useremail allisonchen(a)wustl.edu<mailto:allisonchen@wustl.edu> xnatserver CNDA datestamp 20170817112729 user 2be260df-0fcb-4dda-9cdc-1ae13d9f02bd mailhost mail.nrg.wustl.edu userfullname g.chen TAIL stdout Level 2 Warning in ../include/gmm/gmm_precond_diagonal.h, line 57: The matrix has a zero on its diagonal Level 2 Warning in ../include/gmm/gmm_precond_diagonal.h, line 57: The matrix has a zero on its diagonal Level 2 Warning in ../include/gmm/gmm_precond_diagonal.h, line 57: The matrix has a zero on its diagonal Level 2 Warning in ../include/gmm/gmm_precond_diagonal.h, line 57: The matrix has a zero on its diagonal Level 2 Warning in ../include/gmm/gmm_precond_diagonal.h, line 57: The matrix has a zero on its diagonal Level 2 Warning in ../include/gmm/gmm_precond_diagonal.h, line 57: The matrix has a zero on its diagonal Level 2 Warning in ../include/gmm/gmm_precond_diagonal.h, line 57: The matrix has a zero on its diagonal Level 2 Warning in ../include/gmm/gmm_precond_diagonal.h, line 57: The matrix has a zero on its diagonal Level 2 Warning in ../include/gmm/gmm_precond_diagonal.h, line 57: The matrix has a zero on its diagonal Level 2 Warning in ../include/gmm/gmm_precond_diagonal.h, line 57: The matrix has a zero on its diagonal Level 2 Warning in ../include/gmm/gmm_precond_diagonal.h, line 57: The matrix has a zero on its diagonal Level 2 Warning in ../include/gmm/gmm_precond_diagonal.h, line 57: The matrix has a zero on its diagonal Level 2 Warning in ../include/gmm/gmm_precond_diagonal.h, line 57: The matrix has a zero on its diagonal Level 2 Warning in ../include/gmm/gmm_precond_diagonal.h, line 57: The matrix has a zero on its diagonal Level 2 Warning in ../include/gmm/gmm_precond_diagonal.h, line 57: The matrix has a zero on its diagonal Level 2 Warning in ../include/gmm/gmm_precond_diagonal.h, line 57: The matrix has a zero on its diagonal Level 2 Warning in ../include/gmm/gmm_precond_diagonal.h, line 57: The matrix has a zero on its diagonal Level 2 Warning in ../include/gmm/gmm_precond_diagonal.h, line 57: The matrix has a zero on its diagonal Level 2 Warning in ../include/gmm/gmm_precond_diagonal.h, line 57: The matrix has a zero on its diagonal Level 2 Warning in ../include/gmm/gmm_precond_diagonal.h, line 57: The matrix has a zero on its diagonal Level 2 Warning in ../include/gmm/gmm_precond_diagonal.h, line 57: The matrix has a zero on its diagonal Level 2 Warning in ../include/gmm/gmm_precond_diagonal.h, line 57: The matrix has a zero on its diagonal Level 2 Warning in ../include/gmm/gmm_precond_diagonal.h, line 57: The matrix has a zero on its diagonal Level 2 Warning in ../include/gmm/gmm_precond_diagonal.h, line 57: The matrix has a zero on its diagonal Time taken to solve the Levenberg-Marquardt system of equations: 0.09901 ...done! maximalDeformation: 67.1108 Transforming mesh Done transforming mesh Rasterizing Levenberg-Marquardt... numberOfEntries: 24131 /nrgpackages/tools/freesurfer53-patch/bin/kvlSegmentHippocampalSubfields.sh: line 18: 400668 Segmentation fault (core dumped) kvlSegmentWithoutGUI configurationFileSegmentationWithoutPartialVolumingButAfterUpsampling.txt failed to do kvlSegmentWithoutGUI configurationFileSegmentationWithoutPartialVolumingButAfterUpsampling.txt Linux nrglab08.nrg.mir 2.6.32-642.13.1.el6.x86_64 #1 SMP Wed Jan 11 20:56:24 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux recon-all -s SD10013_1 exited with ERRORS at Thu Aug 17 21:20:53 CDT 2017 For more details, see the log file /data/CNDA/build/MEDEX/20170817_112717/restlaunch/SD10013_1/PROCESSED/SD10013_1/scripts/recon-all.log To report a problem, see http://surfer.nmr.mgh.harvard.edu/fswiki/BugReporting TAIL stderr rm: No match. rm: No match. rm: No match. rm: No match. rm: No match. rm: No match. rm: No match. rm: No match. rm: No match. rm: No match. rm: No match. rm: No match. rm: No match. rm: No match. rm: No match. rm: No match. rm: No match. rm: No match. rm: No match. rm: No match. rm: No match. rm: No match. rm: No match. rm: No match. rm: No match. rm: No match. rm: No match. rm: No match. rm: No match. rm: No match. rm: No match. rm: No match. rm: No match. rm: No match. rm: No match. rm: No match. + die 'recon-all failed' + echo 'recon-all failed' recon-all failed + exit 1 ________________________________ The materials in this message are private and may contain Protected Healthcare Information or other information of a sensitive nature. If you are not the intended recipient, be advised that any unauthorized use, disclosure, copying 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 mail.

1 0

FW: CNDA update: Processing failed for SD10013_1
by Chen, Allison 22 Aug '17

22 Aug '17

Hello Team, I have run ”recon-all args -qcache -all -hippo-subfields” command, but there are some errors. I used freesurfer 5.3 on CNDA: https://cnda.wustl.edu Attached and below are the error information. There is no any problem with our image. Could you give me any suggestions? Thanks a lot! Allison From: cnda-ops(a)nrg.wustl.edu [mailto:cnda-ops@nrg.wustl.edu] Sent: Thursday, August 17, 2017 9:21 PM To: Chen, Allison; cnda-ops(a)nrg.wustl.edu Subject: CNDA update: Processing failed for SD10013_1 The pipeline Freesurfer 5.3 encountered an error. * User: achen<mailto:allisonchen@wustl.edu> * Project: MEDEX * Experiment: SD10013_1 * Pipeline Step: RUN_FS The CNDA technical team is aware of the issue and will notify you when it has been resolved. We appreciate your patience. Please contact cnda-ops(a)nrg.wustl.edu with questions or concerns. The stdout and stderr log files are attached. PIPELINE PARAMETERS qc_rating 1 workdir builddir/SD10013_1 logdir workdir/LOGS XNAT_CSRF 7790fecf-8edf-41cc-8b26-caadb8150e06 email_csv_in cnda-ops(a)nrg.wustl.edu<mailto:cnda-ops@nrg.wustl.edu> freesurfer_subjectdir workdir/PROCESSED/SD10013_1 rawdir workdir/RAW id CNDA_E162884 paramsFile workdir/LOGS/SD10013_1.bashparams tempdir workdir/temp qc_rating_scale ' scan_ids [3] recon_all_args -qcache -all -hippo-subfields freesurferdir workdir/PROCESSED adminemail cnda-ops(a)nrg.wustl.edu<mailto:cnda-ops@nrg.wustl.edu> host https://cnda.wustl.edu/ relaunch false use_manual_qc 0 assessorId CNDA_E162884_freesurfer_20170817112729 label SD10013_1 format DICOM workflowid 6438524 freesurfer_tempdir workdir/PROCESSED/temp project MEDEX builddir /data/CNDA/build/MEDEX/20170817_112717/restlaunch u 2be260df-0fcb-4dda-9cdc-1ae13d9f02bd pwd ******** environment LOCAL useremail allisonchen(a)wustl.edu<mailto:allisonchen@wustl.edu> xnatserver CNDA datestamp 20170817112729 user 2be260df-0fcb-4dda-9cdc-1ae13d9f02bd mailhost mail.nrg.wustl.edu userfullname g.chen TAIL stdout Level 2 Warning in ../include/gmm/gmm_precond_diagonal.h, line 57: The matrix has a zero on its diagonal Level 2 Warning in ../include/gmm/gmm_precond_diagonal.h, line 57: The matrix has a zero on its diagonal Level 2 Warning in ../include/gmm/gmm_precond_diagonal.h, line 57: The matrix has a zero on its diagonal Level 2 Warning in ../include/gmm/gmm_precond_diagonal.h, line 57: The matrix has a zero on its diagonal Level 2 Warning in ../include/gmm/gmm_precond_diagonal.h, line 57: The matrix has a zero on its diagonal Level 2 Warning in ../include/gmm/gmm_precond_diagonal.h, line 57: The matrix has a zero on its diagonal Level 2 Warning in ../include/gmm/gmm_precond_diagonal.h, line 57: The matrix has a zero on its diagonal Level 2 Warning in ../include/gmm/gmm_precond_diagonal.h, line 57: The matrix has a zero on its diagonal Level 2 Warning in ../include/gmm/gmm_precond_diagonal.h, line 57: The matrix has a zero on its diagonal Level 2 Warning in ../include/gmm/gmm_precond_diagonal.h, line 57: The matrix has a zero on its diagonal Level 2 Warning in ../include/gmm/gmm_precond_diagonal.h, line 57: The matrix has a zero on its diagonal Level 2 Warning in ../include/gmm/gmm_precond_diagonal.h, line 57: The matrix has a zero on its diagonal Level 2 Warning in ../include/gmm/gmm_precond_diagonal.h, line 57: The matrix has a zero on its diagonal Level 2 Warning in ../include/gmm/gmm_precond_diagonal.h, line 57: The matrix has a zero on its diagonal Level 2 Warning in ../include/gmm/gmm_precond_diagonal.h, line 57: The matrix has a zero on its diagonal Level 2 Warning in ../include/gmm/gmm_precond_diagonal.h, line 57: The matrix has a zero on its diagonal Level 2 Warning in ../include/gmm/gmm_precond_diagonal.h, line 57: The matrix has a zero on its diagonal Level 2 Warning in ../include/gmm/gmm_precond_diagonal.h, line 57: The matrix has a zero on its diagonal Level 2 Warning in ../include/gmm/gmm_precond_diagonal.h, line 57: The matrix has a zero on its diagonal Level 2 Warning in ../include/gmm/gmm_precond_diagonal.h, line 57: The matrix has a zero on its diagonal Level 2 Warning in ../include/gmm/gmm_precond_diagonal.h, line 57: The matrix has a zero on its diagonal Level 2 Warning in ../include/gmm/gmm_precond_diagonal.h, line 57: The matrix has a zero on its diagonal Level 2 Warning in ../include/gmm/gmm_precond_diagonal.h, line 57: The matrix has a zero on its diagonal Level 2 Warning in ../include/gmm/gmm_precond_diagonal.h, line 57: The matrix has a zero on its diagonal Time taken to solve the Levenberg-Marquardt system of equations: 0.09901 ...done! maximalDeformation: 67.1108 Transforming mesh Done transforming mesh Rasterizing Levenberg-Marquardt... numberOfEntries: 24131 /nrgpackages/tools/freesurfer53-patch/bin/kvlSegmentHippocampalSubfields.sh: line 18: 400668 Segmentation fault (core dumped) kvlSegmentWithoutGUI configurationFileSegmentationWithoutPartialVolumingButAfterUpsampling.txt failed to do kvlSegmentWithoutGUI configurationFileSegmentationWithoutPartialVolumingButAfterUpsampling.txt Linux nrglab08.nrg.mir 2.6.32-642.13.1.el6.x86_64 #1 SMP Wed Jan 11 20:56:24 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux recon-all -s SD10013_1 exited with ERRORS at Thu Aug 17 21:20:53 CDT 2017 For more details, see the log file /data/CNDA/build/MEDEX/20170817_112717/restlaunch/SD10013_1/PROCESSED/SD10013_1/scripts/recon-all.log To report a problem, see http://surfer.nmr.mgh.harvard.edu/fswiki/BugReporting TAIL stderr rm: No match. rm: No match. rm: No match. rm: No match. rm: No match. rm: No match. rm: No match. rm: No match. rm: No match. rm: No match. rm: No match. rm: No match. rm: No match. rm: No match. rm: No match. rm: No match. rm: No match. rm: No match. rm: No match. rm: No match. rm: No match. rm: No match. rm: No match. rm: No match. rm: No match. rm: No match. rm: No match. rm: No match. rm: No match. rm: No match. rm: No match. rm: No match. rm: No match. rm: No match. rm: No match. rm: No match. + die 'recon-all failed' + echo 'recon-all failed' recon-all failed + exit 1 ________________________________ The materials in this message are private and may contain Protected Healthcare Information or other information of a sensitive nature. If you are not the intended recipient, be advised that any unauthorized use, disclosure, copying 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 mail.

1 0

Appropriate number of control points
by Huang, Caleb (NIH/NINDS) [F] 22 Aug '17

22 Aug '17

Hi Freesurfer experts, A co-worker and I are having some issues figuring out a consistent Freesurfer editing protocol. How many control points are generally needed for a T1 scan of fair quality? Would there be a problem with consistency if one set of subjects has 10-80 control points and another set of subjects has 500-700 control points? If relevant, our subjects are patients with localized brain atrophy. What is the suggested time/number of edits to reach an acceptable surface quality? Thanks, -Caleb

1 0

Re: [Freesurfer] mri_vol2surf
by John Anderson 22 Aug '17

22 Aug '17

> Thank you for the response > > It is FDG SUV map > > need more info, eg, what kind of map is that? what modality? > >> -------- Original Message -------- >> Subject: mri_vol2surf >> Local Time: August 22, 2017 11:04 AM >> UTC Time: August 22, 2017 3:04 PM >> From: John.anderso(a)protonmail.com >> To: Freesurfer support list <freesurfer(a)nmr.mgh.harvard.edu> >> >> Dear FS experts, >> I ran voxel-wise analysis between two groups using randomise in FSL and the final statistical maps is as attached. >> I aim to to repeat the analysis using surface based analysis. I followed the steps as in wiki. I am not sure what is the correct value for projfrac int he command "mri_vol2surf" that is more appropriate to show the findings that I have in the voxel-wise (more int eh white matter) on surface. >> >> Thank you for any suggestion >> John

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