Freesurfer

freesurfer@nmr.mgh.harvard.edu

6 participants
30056 discussions

subcortical segmentation
by Eliezer Kahn 02 Nov '05

02 Nov '05

Hi, As mentioned in a previous message, running the subcortical segmentation takes 10-15 hours, primarily because of the Cannonical Registration (mri_ca_register) step. However, one the freesurfer papers (Whole Brain Segmentation: Automated Labeling of Neuroanatomical Structures in the Human Brain) states on the very first page that it takes only 30 minutes to label the brain. How essential is the Cannonical Registration part? Can one leave it out and still get a good subcortical segmentation? Thanks, Eli

2 1

Re: [Freesurfer] help with mris_ca_label
by Sasha Wolosin 02 Nov '05

02 Nov '05

is that *_trans_toSulc.gcs or *.atlas2002_simple.gcs? Sasha Wolosin Research Assistant Developmental Cognitive Neurology Kennedy Krieger Institute 707 N. Broadway Baltimore, MD 21205 ph: (443) 923-9270 wolosin(a)kennedykrieger.org >>> "Brian T. Quinn" <btquinn(a)nmr.mgh.harvard.edu> 11/01/05 7:38 PM >>> canonical surface refers to *.sphere.reg (found in $SUBJECTS_DIR/$s/surf) classifier is *.gcs (found in $FREESURFER_HOME/average) On Tue, 1 Nov 2005, Sasha Wolosin wrote: > Dear all, > In calling mris_ca_label, what does 'canonical surface' and > 'classifier' refer to? > Thanks, > Sasha > > Sasha Wolosin > Research Assistant > Developmental Cognitive Neurology > Kennedy Krieger Institute > 707 N. Broadway > Baltimore, MD 21205 > ph: (443) 923-9270 > wolosin(a)kennedykrieger.org > > > > Disclaimer: > The materials in this e-mail are private and may contain Protected Health Information. Please note that e-mail is not necessarily confidential or secure. Your use of e-mail constitutes your acknowledgment of these confidentiality and security limitations. 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 e-mail in error, please immediately notify the sender via telephone or return e-mail. > _______________________________________________ > Freesurfer mailing list > Freesurfer(a)nmr.mgh.harvard.edu > https://mail.nmr.mgh.harvard.edu/mailman/listinfo/freesurfer > > > -- brian t. quinn

2 1

help with mris_ca_label
by Sasha Wolosin 01 Nov '05

01 Nov '05

Dear all, In calling mris_ca_label, what does 'canonical surface' and 'classifier' refer to? Thanks, Sasha Sasha Wolosin Research Assistant Developmental Cognitive Neurology Kennedy Krieger Institute 707 N. Broadway Baltimore, MD 21205 ph: (443) 923-9270 wolosin(a)kennedykrieger.org Disclaimer: The materials in this e-mail are private and may contain Protected Health Information. Please note that e-mail is not necessarily confidential or secure. Your use of e-mail constitutes your acknowledgment of these confidentiality and security limitations. 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 e-mail in error, please immediately notify the sender via telephone or return e-mail.

2 1

mri_normalize errors
by Eric Feczko 01 Nov '05

01 Nov '05

Hi, Just today I started having problems running mri_normalize within the dev environment using either a centOS or RH computer. Every subject I try to process results in the same error: INFO: Modifying talairach volume c_(r,a,s) based on average_305 Segmentation fault ERROR: mri_normalize exited with non-zero status Linux phrenic 2.6.9-11.ELsmp #1 SMP Wed Jun 8 17:54:20 CDT 2005 i686 i686 i386 GNU/Linux recon-all exited with errors at Tue Nov 1 11:09:57 EST 2005 I even tried re-processing a subject that ran mri_normalize successfully yesterday and recieved the same error. I found nothing wrong with the T1 images in any of the subjects, save for one whose intensity values for white matter greatly exceeded 110; using control points has not fixed that situation. If anyone knows of a solution for this problem, that would be great, thanks! -Eric

2 1

Matlab conflicts with FS-FAST
by Andrew H Bell 31 Oct '05

31 Oct '05

Hello, I'm having strange difficulties with FS-FAST and thought that someone out there might have some suggestions: Specifically - one problem I'm having is viewing the data with SLICEVIEW-SESS The error I get is below (I've pasted the output from the Matlab step on). I don't get this error when using an older version of matlab (which is no longer an option). Is there a way to override this "title" business? Thanks! Andy < M A T L A B > Copyright 1984-2005 The MathWorks, Inc. Version 7.0.4.352 (R14) Service Pack 2 January 29, 2005 Toolbox Path Cache read in 0.00 seconds. Warning: Duplicate directory name: /Users/bellah/matlab. MATLAB Path initialized in 0.06 seconds. To get started, type one of these: helpwin, helpdesk, or demo. For product information, visit www.mathworks.com. >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> yvtitle = ruphert100-func_atlas-face_place-sig >> >> >> >> >> yakview: $Id: yakview.m,v 1.4 2003/09/29 00:53:22 greve Exp $ Base /Users/bellah/Documents/HMI_Data/AFNI_Data/Ruphert/face_place1_ru100/ruphert 100/bold/func_atlas//h-offset Overlay /Users/bellah/Documents/HMI_Data/AFNI_Data/Ruphert/face_place1_ru100/ruphert 100/bold/func_atlas//face_place/sig Hemodynamic Data Offset Raw Data RawFunc: Loading Base ... 1.52961 sec Making Base Mosaic ... 0.340587 sec Loading Overlay 1.11081 sec Making Overlay Mosaic ... 0.266878 sec ??? Error: <a href="error:/Applications/freesurfer/fsfast/toolbox/yak.m,427,9">File: yak.m Line: 427 Column: 9</a> "title" previously appeared to be used as a function, conflicting with its use here as the name of a variable. A possible cause of this error is that you forgot to initialize the variable, or you have initialized it implicitly using load or eval. Error in ==> <a href="error:/Applications/freesurfer/fsfast/toolbox/yakview.m,230,1">yakview at 230</a> yak('init',s,'-Nnnc',Nnnc,'-h',hsa,'-dof',dof,... >> > Andrew H. Bell, PhD Laboratory of Brain and Cognition National Institute of Mental Health 49 Convent Drive Building 49, RM 1B80 Bethesda, MD 20892 office: (301) 496-5625 ext.260 mobile: (202) 679-1279 bellah(a)mail.nih.gov

2 1

Re: [Freesurfer] Intensity problems
by Martin Ystad 31 Oct '05

31 Oct '05

Jenni Pacheco wrote: > Hi Martin, > > Control points should fix the problem. Try adding some to this > brighter region, as well as a few to regions currently labeled to > 110. Sometimes this helps. After you've saved your control points (be > sure to save them) then you should run: > > recon-all -normalization -usecontrolpoints -subjid <subjid> > > to make sure that it uses your control points. If you look at your > brain T1 volume now, those bright spots should be taken care of. If > so you'll need to re-run these steps: > recon-all -skullstrip -subcortseg -normalization2 -segmentation > -subjid <subjid> > > If it hasn't worked, let me know, maybe there's another problem. > > good luck, > Jenni > > On Fri, 28 Oct 2005, Martin Ystad wrote: > >> Hi, I'm currently running the latest developmental release for RedHat >> 9, but I seem to have some problems concerning the >> intesity-normalization. Unfortunately, my images have some intensity >> inhomogenities, but the first normalization-step seems to take care >> of most of these. However, some regions inside the white matter has a >> somewhat high value, for example 130 -140. These regions are not >> included in the white matter when I run the recon-all -segmentation >> program. Adding control-points to these areas does not work, >> obviously, since only values lower than 110 are considered when the >> normalization-step is re-runned. (right?) >> Is there any way to include these areas in my final white matter >> whithout manually drawing them onto the wm.mgz -volume? For instance >> raising the threshold for wm-segmentation? >> If so, would this produce any kind new artifacts which I need to be >> aware of? >> >> Thanks, >> >> Martin Ystad >> Medical Student >> University of Bergen >> Institute of Biomedicine >> Jonas Lies vei 91, 5009 >> Bergen, Norway. >> >> _______________________________________________ >> Freesurfer mailing list >> Freesurfer(a)nmr.mgh.harvard.edu >> https://mail.nmr.mgh.harvard.edu/mailman/listinfo/freesurfer >> >> >> > Hi, thanks for your help. I tried what you suggested and it turned out somewhat better. Still, there are large areas that are not included in the wm.mgz. The problem with some of the data sets is that the intensity inhomogenities in the center of the brain also reaches some very low values. I'm worried that if I include these with control-points, some of the gray matter will be misinterpreted as white matter. Is this a legitimate concern, or does the program work in a different way? If so, how low can the control point value be to avoid that this happens? Ps. If I add a control point to one area with a specific high or low value, does this take care of all the other areas with similar values across the brain, or do I have to add a control point to all areas that have discrepancies in intensity? Thanks, Martin

3 4

RE: [Freesurfer] recon-all library dependencies
by James Voyvodic 31 Oct '05

31 Oct '05

Is there a version of Linux that we can get that will be fairly sure to be able to run FreeSurfer's RECON-ALL sequence? We have been using many different versions of FreeSurfer through the old CSURF interface on several different Linux installations (RH 7-9, Fedora Core 1). Now we want to upgrade to a recent recon-all command line version. So far, I've never been able to get recon-all to run successfully (always crashes part way through) on either RedHat 9 or Fedora Core 1. The details of my most recent attempt with the newest RH9 release are shown below. What Linux should I choose to have the best chance of running FreeSurfer? Ideally I would like to install the same version being used at MGH. Is that RH9, CentOS, Fedora? I'm running on a Dell Intel with plenty of power. Alternatively I would be happy to upgrade my RedHat 9 system to the libraries FreeSurfer wants if I knew which versions I should upgrade to (and where to find them). Do other successful recon-all users have any recommendations? thanks, Jim =============== Redhat 9 attempt to run "recon-all" using the recent Dev version: freesurfer-Linux-rh9-dev20051003-full (I had successfully reconstructed this data set using an earlier csurf version). recon-all -subjid k1140 autorecon1 ... (many steps apparently worked, and then we got the following) [jim@hawking:/data2/surfdata/subjects/k1140/mri/] [2005-10-28 14:05:25] running: /usr/local/mni/bin/nu_estimate_np_and_em -parzen -log -sharpen 0.15 0.01 -iterations 50 -stop 0.001 -shrink 4 -auto_mask -nonotify -b_spline 1 -distance 200 -quiet -execute -clobber -nokeeptmp -tmpdir /usr/tmp/nu_correct_14439/ nu0.mnc nu1.imp /usr/local/mni/bin/volume_stats: /lib/libgcc_s.so.1: version `GCC_3.3' not found (required by /usr/lib/libstdc++.so.6) nu_estimate_np_and_em: crashed while running volume_stats (termination status=256) nu_correct: crashed while running nu_estimate_np_and_em (termination status=256) ERROR: nu_correct Linux hawking 2.4.20-31.9 #1 Tue Apr 13 18:04:23 EDT 2004 i686 i686 i386 GNU/Linux recon-all exited with errors at Fri Oct 28 14:05:25 EDT 2005 (The non-development release, freesurfer-Linux-rh9-v2.1, stopped earlier than this with probelms finding tixwish libraries.) -----Original Message----- From: Nick Schmansky [mailto:nicks@nmr.mgh.harvard.edu] Sent: Wednesday, October 26, 2005 5:35 PM To: James Voyvodic Cc: Freesurfer Mailing List Subject: Re: [Freesurfer] recon-all library dependencies Jim, The short answer is that I think you may need to have your Linux installation upgraded with newer versions of the 'base' libraries. Freesurfer requires, but does not include, a number of libraries that are normally included in most Linux installations. The newer 'dev' version of Freesurfer includes the following libraries in its 'lib' directory (which themselves are built against the 'base' libraries, as you have discovered): GSL, Tcl/Tk/Tix/BLT, the MINC tools, and Qt To see which libraries a freesurfer binary depends upon, use the 'ldd' command. On a rh7.3 system of ours (the oldest Linux platform we support), here is the output for one of the binaries, where the 'base' libraries are the ones in the /usr/lib and /usr/X11 directories: [martinos01:~] (nmr-dev-env) ldd `which tkmedit` libtix.so.0 => /usr/local/freesurfer/dev/lib/tcltktixblt/lib/libtix.so.0 (0x40015000) libtk8.4.so => /usr/local/freesurfer/dev/lib/tcltktixblt/lib/libtk8.4.so (0x4004f000) libtcl8.4.so => /usr/local/freesurfer/dev/lib/tcltktixblt/lib/libtcl8.4.so (0x40112000) libglut.so.3 => /usr/lib/libglut.so.3 (0x401c8000) libSM.so.6 => /usr/X11R6/lib/libSM.so.6 (0x40204000) libICE.so.6 => /usr/X11R6/lib/libICE.so.6 (0x4020c000) libXmu.so.6 => /usr/X11R6/lib/libXmu.so.6 (0x40223000) libXi.so.6 => /usr/X11R6/lib/libXi.so.6 (0x40239000) libGLU.so.1 => /usr/lib/libGLU.so.1 (0x40241000) libGL.so.1 => /usr/lib/libGL.so.1 (0x402bc000) libXext.so.6 => /usr/X11R6/lib/libXext.so.6 (0x40318000) libdl.so.2 => /lib/libdl.so.2 (0x40325000) libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x40328000) libgsl.so.0 => /usr/pubsw/packages/gsl/current/lib/libgsl.so.0 (0x403fe000) libgslcblas.so.0 => /usr/pubsw/packages/gsl/current/lib/libgslcblas.so.0 (0x4055a000) libjpeg.so.62 => /usr/lib/libjpeg.so.62 (0x40587000) libtiff.so.3 => /usr/lib/libtiff.so.3 (0x405a5000) libz.so.1 => /usr/lib/libz.so.1 (0x405e9000) libm.so.6 => /lib/i686/libm.so.6 (0x405f7000) libcrypt.so.1 => /lib/libcrypt.so.1 (0x4061a000) libc.so.6 => /lib/i686/libc.so.6 (0x42000000) libXt.so.6 => /usr/X11R6/lib/libXt.so.6 (0x40647000) libstdc++-libc6.2-2.so.3 => /usr/lib/libstdc++-libc6.2-2.so.3 (0x40693000) libGLcore.so.1 => /usr/lib/libGLcore.so.1 (0x406d6000) /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000) So you can see that most of the 'base' libraries are version 6. The same is true for rh9. You can compare this output to your own output from the same command to discover which libraries on your system are old. Also, I noticed that your mni tools seem to be in the /usr/local/mni directory, rather than in the $FREESURFER_HOME/lib/mni directory. You may have a lingering MINC_BIN_DIR statement in your .cshrc file, pointing to a prior installation of the MINC tools, but I don't think this is the heart of your problem (old libraries). Unfortunately, there is no 'universal' freesurfer distribution for this very reason that Linux platforms have varying versions of the base libraries. If you have a sysadmin, perhaps he can upgrade the libs on your rh9 system. The newer Linux installations, like CentOS 4, have automatic upgrade tools, which alleviate this problem, and is why we will soon be abandoning our own rh7.3 and rh9 Linux systems at the MGH NMR center (which require manual upgrade). Lastly, you can restart recon-all from different stages. Run 'recon-all -help' to see the different stages (basically autorecon1, autorecon2 and autorecon3). Nick On Wed, 2005-10-26 at 16:49 -0400, James Voyvodic wrote: > I've upgraded to the latest development release > (freesurfer-Linux-rh9-dev20051003-full.tar.gz) running > on Linux Redhat 9 on an x86 platform. > Recon-all crashes, apparently because of failed library dependencies, with > the following message: > > /usr/local/mni/bin/volume_stats: /usr/lib/libstdc++.so.6: version > `CXXABI_1.3' not found (required by /usr/local/mni/bin/volume_stats) > /usr/local/mni/bin/volume_stats: /usr/lib/libstdc++.so.6: version > `GLIBCXX_3.4' not found (required by /usr/local/mni/bin/volume_stats) > nu_estimate_np_and_em: crashed while running volume_stats (termination > status=256) > nu_correct: crashed while running nu_estimate_np_and_em (termination > status=256) > ERROR: nu_correct > Linux hawking 2.4.20-31.9 #1 Tue Apr 13 18:04:23 EDT 2004 i686 i686 i386 > GNU/Linux > recon-all exited with errors at Wed Oct 26 15:17:17 EDT 2005 > > It had previously crashed because it couldn't find libstdc++.so.6 at all, so > I tried to appease it by using the old trick of linking libstdc++.so.5 to > libstdc++.so.6, but obviously that wasn't enough. > > So the main question is: what libraries are needed to run the new version(s) > of FreeSurfer? > Is there a way to download the missing libraries from somewhere? > > When I installed and tried to run the most recent stable release > (freesurfer-Linux-rh9-v2.1.tar.gz) I was foiled because I didn't have > libtixwish installed, which is why I went to the development release that > had more libraries. Yum says I have libstdc++ and doesn't offer a .so.6 > variant. Do I need a different version of Linux? > > A side question: If recon-all crashes part way through, is there a way to > skip the successful steps when restarting or does it have to redo all the > steps in its autorecon (e.g. autorecon1) script? > > thanks, > Jim > > > ======================== > James T. Voyvodic, Ph.D. > Brain Imaging and Analysis Center > Duke University Medical Center > e-mail: jim.voyvodic(a)duke.edu > > _______________________________________________ > Freesurfer mailing list > Freesurfer(a)nmr.mgh.harvard.edu > https://mail.nmr.mgh.harvard.edu/mailman/listinfo/freesurfer > >

2 1

Re: [Freesurfer] good news and bad news
by Bruce Fischl 28 Oct '05

28 Oct '05

Hi Greg, it's: mris_ca_train lh sphere.reg my_annot_file <subject 1> ... lh.my_annot_atlas.gcs. -autorecon3 won't pick it up, you'll have to specify it by hand I think, but Doug would know. cheers, Bruce On Fri, 28 Oct 2005, Greg Harris wrote: > Hi Bruce. > > mris_sample_parc seems straightforward enough, but I'll need a few > hints about mris_ca_train. I get this usage line: > > usage: mris_ca_train [options] <hemi> <canon surf> <annot file> <subject 1> > <subject 2> ... <output file> > > Apparently, none of the options is '--help' or '-h', so I have no list of > options. > Is <canon surf> a standard component of the freesurfer distribution? > Is <annot file> a table of names, labels and colors? If so, where is the > file that > drives the generation of the file label/aparc_annot.ctab in each subject? > What do I want for <output file>? Presumably this is a special file name > that > will be picked up in -autorecon3. > > Greg > > > Bruce Fischl wrote: > >> Hi Greg, >> >> I'll let someone else answer the download question, as I don't offhand >> remember which site it is. >> >> As for your own atlas, I assume you mean cortical? This shouldn't be a >> problem. We distribute a binary called mris_sample_aparc that will sample >> them onto a surface. You can then use mris_ca_train to build your own >> atlas. >> >> As for the subcortical, this is a tougher question. Note that we are still >> working on it, and it has some sequence dependence. That said though, our >> manually labeled thalamus does extend to caudate, and it also goes pretty >> far lateral where there are some very low contrast thalamic nuclei. I'm not >> really qualified to comment on this - we'll need to get the neuroanatomists >> together. >> >> cheers, >> Bruce >> >> >> On Fri, 28 Oct 2005, Greg Harris wrote: >> >>> Hi Bruce. >>> >>> I need to watch for the source tarball on the website when it appears. >>> Is the correct url for the website something like >>> https://surfer.nmr.mgh.harvard.edu/fswiki/Download >>> i.e., the FreeSurfer Wiki? Or will I need to search for a tarball at >>> ftp://surfer.nmr.mgh.harvard.edu/pub/dist/ ? >>> >>> We will need instructions on how to define our own atlas, or how to >>> vary the existing atlas that is used to produce -autorecon3. We have >>> extensive traces of 50 or more brains to base this on. We want to >>> subdivide the STG-planum area. We also want the Insula, which I can >>> sort of get by clipping the 'unknown' ribbon with a probabilistic >>> talairach mask after mapping the 'aparc' information back into brains2. >>> >>> We have concerns about the 'aseg' information; for example, your >>> Thalamus-Proper is much larger than our gross thalamus, and our >>> thalamus roi does not touch our caudate roi. Do the control points >>> have to make the subcortical neighborhood pretty much of uniform >>> intensity of 110 for the white matter spine to develop into a sphere? >>> >>> Greg Harris >>> University of Iowa Psychiatry Brain Imaging Lab >>> >>> Bruce Fischl wrote: >>> >>>> We will be posting a "read-only" tarball on the website in the next >>>> couple of weeks, and anyone is free to download it and look at it. We >>>> will *not* be supporting a make/configure type env for people to download >>>> and build, as we simply aren't ready to do so. We plan to implement such >>>> a procedure, but it will be a while. Instead of waiting until that was >>>> ready, I thought people would like to have access to the source to at >>>> least see what things are doing, and be able to see file formats and >>>> such. >>> >>> >>>> cheers, >>>> Bruce >>>> >>>> >>>> _______________________________________________ >>>> Freesurfer mailing list >>>> Freesurfer(a)nmr.mgh.harvard.edu >>>> https://mail.nmr.mgh.harvard.edu/mailman/listinfo/freesurfer >>>> >>> >>> >>> >> > > >

1 0

Re: [Freesurfer] good news and bad news
by Bruce Fischl 28 Oct '05

28 Oct '05

Hi Greg, I'll let someone else answer the download question, as I don't offhand remember which site it is. As for your own atlas, I assume you mean cortical? This shouldn't be a problem. We distribute a binary called mris_sample_aparc that will sample them onto a surface. You can then use mris_ca_train to build your own atlas. As for the subcortical, this is a tougher question. Note that we are still working on it, and it has some sequence dependence. That said though, our manually labeled thalamus does extend to caudate, and it also goes pretty far lateral where there are some very low contrast thalamic nuclei. I'm not really qualified to comment on this - we'll need to get the neuroanatomists together. cheers, Bruce On Fri, 28 Oct 2005, Greg Harris wrote: > Hi Bruce. > > I need to watch for the source tarball on the website when it appears. > Is the correct url for the website something like > https://surfer.nmr.mgh.harvard.edu/fswiki/Download > i.e., the FreeSurfer Wiki? Or will I need to search for a tarball at > ftp://surfer.nmr.mgh.harvard.edu/pub/dist/ ? > > We will need instructions on how to define our own atlas, or how to > vary the existing atlas that is used to produce -autorecon3. We have > extensive traces of 50 or more brains to base this on. We want to > subdivide the STG-planum area. We also want the Insula, which I can > sort of get by clipping the 'unknown' ribbon with a probabilistic > talairach mask after mapping the 'aparc' information back into brains2. > > We have concerns about the 'aseg' information; for example, your > Thalamus-Proper is much larger than our gross thalamus, and our > thalamus roi does not touch our caudate roi. Do the control points > have to make the subcortical neighborhood pretty much of uniform > intensity of 110 for the white matter spine to develop into a sphere? > > Greg Harris > University of Iowa Psychiatry Brain Imaging Lab > > Bruce Fischl wrote: > >> We will be posting a "read-only" tarball on the website in the next couple >> of weeks, and anyone is free to download it and look at it. We will *not* >> be supporting a make/configure type env for people to download and build, >> as we simply aren't ready to do so. We plan to implement such a procedure, >> but it will be a while. Instead of waiting until that was ready, I thought >> people would like to have access to the source to at least see what things >> are doing, and be able to see file formats and such. > >> cheers, >> Bruce >> >> >> _______________________________________________ >> Freesurfer mailing list >> Freesurfer(a)nmr.mgh.harvard.edu >> https://mail.nmr.mgh.harvard.edu/mailman/listinfo/freesurfer >> > > >

2 1

Intensity problems
by Martin Ystad 28 Oct '05

28 Oct '05

Hi, I'm currently running the latest developmental release for RedHat 9, but I seem to have some problems concerning the intesity-normalization. Unfortunately, my images have some intensity inhomogenities, but the first normalization-step seems to take care of most of these. However, some regions inside the white matter has a somewhat high value, for example 130 -140. These regions are not included in the white matter when I run the recon-all -segmentation program. Adding control-points to these areas does not work, obviously, since only values lower than 110 are considered when the normalization-step is re-runned. (right?) Is there any way to include these areas in my final white matter whithout manually drawing them onto the wm.mgz -volume? For instance raising the threshold for wm-segmentation? If so, would this produce any kind new artifacts which I need to be aware of? Thanks, Martin Ystad Medical Student University of Bergen Institute of Biomedicine Jonas Lies vei 91, 5009 Bergen, Norway.

1 0

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