Freesurfer

freesurfer@nmr.mgh.harvard.edu

1 participants
30089 discussions

Re: [Freesurfer] FW: TRACULA some fiber volumes being too small
by Anastasia Yendiki 31 Oct '12

31 Oct '12

If FSL isn't happy with the directions, that's going to be fatal b/c trac-all relies on bedpostx running properly. I'm going to look into this further to try to figure out what it is about this data that's causing the discrepancy. On Wed, 31 Oct 2012, Fernando Ventrice wrote: > Dear Anastasia, > When I open the dtifit_V1 and dtifit_FA with Freeview the vector directions actually are OK, but when I open them with FSLview they are similar to your screen-shot. Here I also send a screen-shot with the comparison between the two softwares in each monitor. > Best, > Fernando > ________________________________________ > From: Anastasia Yendiki [ayendiki(a)nmr.mgh.harvard.edu] > Sent: Tuesday, October 30, 2012 1:24 PM > To: Fernando Ventrice > Cc: freesurfer(a)nmr.mgh.harvard.edu > Subject: Re: [Freesurfer] FW: TRACULA some fiber volumes being too small > > See screenshot now :) > > On Tue, 30 Oct 2012, Anastasia Yendiki wrote: > >> >> Hi Fernando - Thanks for uploading your data. Looking at the primary >> directions from tensor fit on the data that you sent me (see screenshot), >> they seem to be off by a 90 degree angle from what you'd expect them. This >> means that your gradient table is probably off as well. >> >> Hope this helps, >> a.y >> >> On Thu, 18 Oct 2012, Fernando Ventrice wrote: >> >>> Dear Freesurfer/Tracula users, >>> Finally I could successfully test Tracula and I think it is amazing what >>> it can do automatically. These are the commands I used: >>> >>> export FREESURFER_HOME=${HOME}/Programs/freesurfer_510 && source >>> $FREESURFER_HOME/SetUpFreeSurfer.sh >>> source /etc/fsl/fsl.sh >>> export FSLPARALLEL=condor >>> trac-all -prep -c >>> /home/labneuroimg/STATION_FLENI/Tensores/Fernando_Ventrice/dmrirc_Fernando_Ventrice >>> trac-all -bedp -c >>> /home/labneuroimg/STATION_FLENI/Tensores/Fernando_Ventrice/dmrirc_Fernando_Ventrice >>> # "trac-all -bedp" gave some errors so I used bedpostx directly: >>> bedpostx >>> /home/labneuroimg/STATION_FLENI/Tensores/Fernando_Ventrice/20120112_VENTRICE_FERNANDO/dmri >>> trac-all -path -c >>> /home/labneuroimg/STATION_FLENI/Tensores/Fernando_Ventrice/dmrirc_Fernando_Ventrice >>> freeview -tv >>> /home/labneuroimg/STATION_FLENI/Tensores/Fernando_Ventrice/20120112_VENTRICE_FERNANDO/dpath/merged_avg33_mni_flt.mgz >>> -v >>> /home/labneuroimg/STATION_FLENI/Tensores/Fernando_Ventrice/20120112_VENTRICE_FERNANDO/dmri/dtifit_FA.nii.gz >>> & >>> >>> All finished without errors, but there seems to be a problem with CC >>> Forceps Mayor volume, which gave very small values. Is this OK or I made >>> some mistake? First I tested with some patient and other fiber tracks also >>> gave very small volumes. I attached some pictures and the dmrirc and >>> trac-all log files. >>> Best, >>> Fernando Ventrice >>> >>> El contenido del presente mensaje y el de sus adjuntos, es confidencial, >>> privado y de uso exclusivo de los destinatarios a los cuales está >>> dirigido, pudiendo contener información legalmente protegida. Queda >>> prohibida la revisión, divulgación, publicación, modificación, copia, >>> distribución o acción en relación con esta información, por personas o >>> entidades distintas al destinatario. Si usted, por alguna razón, lo ha >>> recibido por error, por favor tenga la amabilidad de eliminarlo de su >>> sistema. Las opiniones contenidas, son exclusivas de su autor, y no >>> representa necesariamente, la opinión de FLENI. >>> http://www.fleni.org.ar >>> >> > > > The information in this e-mail is intended only for the person to whom it is > addressed. If you believe this e-mail was sent to you in error and the e-mail > contains patient information, please contact the Partners Compliance HelpLine at > http://www.partners.org/complianceline . If the e-mail was sent to you in error > but does not contain patient information, please contact the sender and properly > dispose of the e-mail. > > El contenido del presente mensaje y el de sus adjuntos, es confidencial, privado y de uso exclusivo de los destinatarios a los cuales está dirigido, pudiendo contener información legalmente protegida. Queda prohibida la revisión, divulgación, publicación, modificación, copia, distribución o acción en relación con esta información, por personas o entidades distintas al destinatario. Si usted, por alguna razón, lo ha recibido por error, por favor tenga la amabilidad de eliminarlo de su sistema. Las opiniones contenidas, son exclusivas de su autor, y no representa necesariamente, la opinión de FLENI. > http://www.fleni.org.ar > > El contenido del presente mensaje y el de sus adjuntos, es confidencial, privado y de uso exclusivo de los destinatarios a los cuales está dirigido, pudiendo contener información legalmente protegida. Queda prohibida la revisión, divulgación, publicación, modificación, copia, distribución o acción en relación con esta información, por personas o entidades distintas al destinatario. Si usted, por alguna razón, lo ha recibido por error, por favor tenga la amabilidad de eliminarlo de su sistema. Las opiniones contenidas, son exclusivas de su autor, y no representa necesariamente, la opinión de FLENI. > http://www.fleni.org.ar >

1 0

Re: [Freesurfer] average measure of cortical thickness
by Bruce Fischl 31 Oct '12

31 Oct '12

yes, I think so Bruce On Tue, 30 Oct 2012, Daniel Ferreira wrote: > So, as a measure of whole brain cortical thickness average is it better to > "Mean Thickness" from aparc.stats file? > > > 2012/10/30 Bruce Fischl <fischl(a)nmr.mgh.harvard.edu> > Hi Daniel > > the parcellations are not uniform in size, and therefore the > average of them will not be the same as averaging over the > cortex. > > cheers > Bruce > On Tue, 30 Oct 2012, Daniel Ferreira wrote: > > Hi, > I was wondering what should I use as an average of > cortical thickness for > the whole cortex. > > The aparc.stats output gives a value of "Mean > Thickness" for each > hemisphere. But this value does not coincide with > the one I get if I average > the 34 variables from aparc.stats. Do you know why? > > thanks so much in advance > > Daniel > > > > > The information in this e-mail is intended only for the person to whom > it is > addressed. If you believe this e-mail was sent to you in error and the > e-mail > contains patient information, please contact the Partners Compliance > HelpLine at > http://www.partners.org/complianceline . If the e-mail was sent to you > in error > but does not contain patient information, please contact the sender > and properly > dispose of the e-mail. > > > >

3 4

SPM VBM and Freesurfer group analysis
by Infinity 31 Oct '12

31 Oct '12

Hi, I did a SPM VBM (using dartel) analysis as well as a freesurfer group analysis. After correcting for multiple comparisons. Both maps give me pretty different results. From the literature review both sets of results make sense but the fact that the results don't agree is troubling me. I have checked everything multiple times and still get the same results. Is it common that the two methods give different results? I also wanted to know the interpretation of the surface measures that freesurfer reports, especially the curv and sulc measures. What does it mean exactly when two groups have different sulc or curv measures? In my results I get a negative correlation between curv measure and volume measure in the same region. So in that region for curv measure group1 > group 2 while in the same region for the volume measure group1 < group2. How exactly is the curv measure related to volume and area measures? Is there a standard reference where all the details for these measures are mentioned? Thank you.

1 0

Phase-Sensitive Inversion Recovery
by Lena Palaniyappan 31 Oct '12

31 Oct '12

Hi all Our local team of physicists recommend Phase-Sensitive Inversion Recovery instead of MPRAGE for anatomical imaging in 7T. So far, I have had no issues with 7T MPRAGEs with regard to freesurfer processing. I am not sure about PSIR and freesurfer compatibility. Does anyone have experience with PSIR sequences. Any suggestions/thoughts will be helpful. Cheers, Lena Palaniyappan This message and any attachment are intended solely for the addressee and may contain confidential information. If you have received this message in error, please send it back to me, and immediately delete it. Please do not use, copy or disclose the information contained in this message or in any attachment. Any views or opinions expressed by the author of this email do not necessarily reflect the views of the University of Nottingham. This message has been checked for viruses but the contents of an attachment may still contain software viruses which could damage your computer system: you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation.

2 2

recon-all
by Efrat Kliper 31 Oct '12

31 Oct '12

Dear Freesurfer expert, I am using Freesurfer version 5.1.0. After I ran the freesurfer recon-all -autorecon-all and checked the data I saw that the skull wasn't removed as a whole (yet it is not part of the pial or white matter margin). I was wondering if it just doesn't look good or that part of the skull that was not removed was calculated as part of the ICV or somthing else. Thanks in advance, efrat

2 1

Hurricane Sandy
by Ed Gronenschild 31 Oct '12

31 Oct '12

Hi Bruce and colleagues, I hope you did survive Sandy without too much damage. Cheers, Ed

2 1

No result differences v5.1.0 between MacOSX 10.6 and 10.7
by Ed Gronenschild 31 Oct '12

31 Oct '12

Hi, For your information: for version 5.1.0 we have found no differences in the results between MacOSX 10.6 and 10.7 (53 subjects). Cheers, Ed

1 0

Anyone successfully performed probtrackx2 whole brain tractography?
by Alistair Perry 31 Oct '12

31 Oct '12

To FSL/Freesurfer experts, I have been trying for the last few weeks to perform whole-brain probabilistic tractography using FSL's probtrackx2. After solving a number of issues, I believe I am calling the command correctly, but it has already taken 5 days and wondering if I am going in the right direction. Our data compromises of T1-weighted images with spatial resolution of 1x1x1 mm^3. I have called the following command on a 64GB RAM CPU system, using the native-freesurfer Desikan (68 ROI) parcellation. probtrackx2 -s ./merged -m ./nodif_brain_mask.nii -x ./rois.ascii --seedref=./rawavg.nii --xfm=./fs2dti.mat --targetmasks=./rois.ascii --dir=../probtrackresults/ --forcedir --s2tastext --omatrix1 What I would like to know if anyone has successfully performed whole-brain tractography with what certain specifications. For example, the number of parcellations you used, computer speed etc. How long did it take to run, and if it is not an issue, what is the command you used? I am obviously aware by reducing the number of vertices it can significantly decrease the running time, however I do not want to kill the running command. Thanks, Alistair Perry

1 0

Re: [Freesurfer] Total cerebral volume.
by Zheng Hui 30 Oct '12

30 Oct '12

1 0

Re: [Freesurfer] Files
by Douglas N Greve 30 Oct '12

30 Oct '12

See http://surfer.nmr.mgh.harvard.edu/fswiki/RepeatedMeasuresAnova This is for a single group. For two groups with 3 time points. In your case, you only have 2 time points (so no TP1-vs-TP3 variable). To account for the 2nd group, create two variables: TP1-vs-TP2.Group1 and TP1-vs-TP2.Group2. If a subject is in Group1, then set the Group2 variable to 0. doug On 10/30/2012 04:38 PM, Maren Strenziok wrote: > If you don't agree with our matrix and contrasts, can you please send us a matrix example for a 2x2 within and between subjects ANOVA model and contrasts to get the interaction effect? > Maren > > On Oct 30, 2012, at 4:22 PM, Douglas N Greve<greve(a)nmr.mgh.harvard.edu> wrote: > >> Hi Ryan, I don't understand your model. This does not look like a standard repeated measures ANOVA. Is it supposed to be equivalent? >> doug >> >> On 10/30/2012 02:07 PM, Ryan wrote: >>> Doug, >>> Just so our study is understandable, subjects completed a 6 week period of training or no training (i.e. the control condition) with a scan at the beginning and end of the period. Thus, I entered the pre and post-scans for training and control subjects in the input files. The names for all the subjects are kept in an ordered list, referenced by the other two files I describe below. >>> In the Xg.dat file, the first column has a +1 for each control subject's pre-scan and a -1 for each control subject's post-scan. The second column has a +1 for each training subject's pre-scan and a -1 for each training subject's post-scan. The remaining columns each pertain to a specific subject's two scans, with 1's showing FreeSurfer which two scans are being compared pre to post. >>> In the mtx file, the -1 references the first column in Xg.dat (control subjects) and the +1 references the second column in Xg.dat (training subjects). The remaining 0's refer to the other subjects or columns in Xg.dat. >>> So in order to determine whether there's thickening or thinning in the controls and training subjects, would I still need to use an additional analysis with the contrasts [1 0 0 ....] and [0 1 0 ....]? Thank you. >>> >>> >>> On Tue, Oct 30, 2012 at 11:28 AM, Douglas N Greve<greve(a)nmr.mgh.harvard.edu<mailto:greve@nmr.mgh.harvard.edu>> wrote: >>> >>> Hi Ryan, I'm a little lost here. Can you resend your X and >>> contrast matrices and explain what each column is? >>> doug >>> >>> >>> On 10/26/2012 03:45 PM, Ryan wrote: >>> >>> Doug, >>> Actually my input is not the difference map, but the >>> separate time points (it's timepoint 2 weighted with -1 and >>> timepoint 1 weighted with 1, described in the matrix file I >>> sent you). So in order to determine whether there's thickening >>> or thinning in the controls and training subjects, would I >>> still need to use the additional contrasts [1 0 0 ....] and [0 >>> 1 0 ....]? Thank you. >>> >>> On Thu, Oct 25, 2012 at 3:48 PM, Douglas N Greve >>> <greve(a)nmr.mgh.harvard.edu<mailto:greve@nmr.mgh.harvard.edu> >>> <mailto:greve@nmr.mgh.harvard.edu >>> <mailto:greve@nmr.mgh.harvard.edu>>> wrote: >>> >>> And the input is already TimePoint2-TimePoint1? If so, >>> then you >>> will need two more contrasts: [1 0 0 ....] and [0 1 0 >>> ....]. The >>> first tells you if controls are thinning (blue) or thickening >>> (red), the 2nd tells you if the training is doing the same. >>> doug >>> >>> >>> On 10/25/2012 03:34 PM, Ryan wrote: >>> >>> Doug, >>> Yes, it's a longitudinal study since we MRI >>> participants >>> pre-training and post-training. >>> >>> On Thu, Oct 25, 2012 at 2:37 PM, Douglas N Greve >>> <greve(a)nmr.mgh.harvard.edu<mailto:greve@nmr.mgh.harvard.edu> >>> <mailto:greve@nmr.mgh.harvard.edu >>> <mailto:greve@nmr.mgh.harvard.edu>> >>> <mailto:greve@nmr.mgh.harvard.edu >>> <mailto:greve@nmr.mgh.harvard.edu> >>> >>> <mailto:greve@nmr.mgh.harvard.edu >>> <mailto:greve@nmr.mgh.harvard.edu>>>> wrote: >>> >>> I'm not sure I understand. Is this a longitudinal >>> study? >>> >>> >>> On 10/25/2012 01:26 PM, Ryan wrote: >>> >>> Doug, >>> Also, how can I tell if it's thickening or >>> thinning if >>> red/blue corresponds to the group? Thanks for >>> the help. >>> >>> ---------- Forwarded message ---------- >>> From: *Douglas N Greve* >>> <greve(a)nmr.mgh.harvard.edu<mailto:greve@nmr.mgh.harvard.edu> >>> <mailto:greve@nmr.mgh.harvard.edu >>> <mailto:greve@nmr.mgh.harvard.edu>> >>> <mailto:greve@nmr.mgh.harvard.edu >>> <mailto:greve@nmr.mgh.harvard.edu> >>> <mailto:greve@nmr.mgh.harvard.edu >>> <mailto:greve@nmr.mgh.harvard.edu>>> >>> <mailto:greve@nmr.mgh.harvard.edu >>> <mailto:greve@nmr.mgh.harvard.edu> >>> <mailto:greve@nmr.mgh.harvard.edu >>> <mailto:greve@nmr.mgh.harvard.edu>> >>> <mailto:greve@nmr.mgh.harvard.edu >>> <mailto:greve@nmr.mgh.harvard.edu> >>> <mailto:greve@nmr.mgh.harvard.edu >>> <mailto:greve@nmr.mgh.harvard.edu>>>>> >>> Date: Thu, Oct 25, 2012 at 12:20 PM >>> Subject: Re: Files >>> To: Ryan<wmcgarry(a)gmu.edu >>> <mailto:wmcgarry@gmu.edu> <mailto:wmcgarry@gmu.edu >>> <mailto:wmcgarry@gmu.edu>> >>> <mailto:wmcgarry@gmu.edu<mailto:wmcgarry@gmu.edu> >>> <mailto:wmcgarry@gmu.edu<mailto:wmcgarry@gmu.edu>>> >>> <mailto:wmcgarry@gmu.edu<mailto:wmcgarry@gmu.edu> >>> <mailto:wmcgarry@gmu.edu<mailto:wmcgarry@gmu.edu>> >>> <mailto:wmcgarry@gmu.edu<mailto:wmcgarry@gmu.edu> >>> <mailto:wmcgarry@gmu.edu<mailto:wmcgarry@gmu.edu>>>>> >>> >>> >>> That contrast will compute training-controls. >>> In the maps, >>> red/yellow will mean training>controls, blue/cyan >>> otherwise >>> >>> doug >>> >>> >>> >>> On 10/25/2012 12:47 AM, Ryan wrote: >>> >>> Doug, >>> Here are the Xg.dat (where the first >>> column is for >>> controls and >>> the second column is for training >>> subjects) and >>> mtx files, I >>> didn't use the FSGD design. Please let me >>> know if >>> this is >>> sufficient for you to answer my question, >>> thank >>> you very much. >>> >>> -- -Ryan >>> >>> >>> -- Douglas N. Greve, Ph.D. >>> MGH-NMR Center >>> greve(a)nmr.mgh.harvard.edu<mailto:greve@nmr.mgh.harvard.edu> >>> <mailto:greve@nmr.mgh.harvard.edu >>> <mailto:greve@nmr.mgh.harvard.edu>> >>> <mailto:greve@nmr.mgh.harvard.edu >>> <mailto:greve@nmr.mgh.harvard.edu> >>> <mailto:greve@nmr.mgh.harvard.edu >>> <mailto:greve@nmr.mgh.harvard.edu>>> >>> <mailto:greve@nmr.mgh.harvard.edu >>> <mailto:greve@nmr.mgh.harvard.edu> >>> <mailto:greve@nmr.mgh.harvard.edu >>> <mailto:greve@nmr.mgh.harvard.edu>> >>> >>> <mailto:greve@nmr.mgh.harvard.edu >>> <mailto:greve@nmr.mgh.harvard.edu> >>> <mailto:greve@nmr.mgh.harvard.edu >>> <mailto:greve@nmr.mgh.harvard.edu>>>> >>> Phone Number: 617-724-2358<tel:617-724-2358> >>> <tel:617-724-2358<tel:617-724-2358>> >>> <tel:617-724-2358<tel:617-724-2358> <tel:617-724-2358 >>> <tel:617-724-2358>>> >>> <tel:617-724-2358<tel:617-724-2358> <tel:617-724-2358 >>> <tel:617-724-2358>> <tel:617-724-2358<tel:617-724-2358> >>> <tel:617-724-2358<tel:617-724-2358>>>> >>> Fax: 617-726-7422<tel:617-726-7422> >>> <tel:617-726-7422<tel:617-726-7422>> <tel:617-726-7422 >>> <tel:617-726-7422> >>> <tel:617-726-7422<tel:617-726-7422>>> <tel:617-726-7422 >>> <tel:617-726-7422> <tel:617-726-7422<tel:617-726-7422>> >>> >>> <tel:617-726-7422<tel:617-726-7422> <tel:617-726-7422 >>> <tel:617-726-7422>>>> >>> >>> >>> Bugs: >>> surfer.nmr.mgh.harvard.edu/fswiki/BugReporting >>> <http://surfer.nmr.mgh.harvard.edu/fswiki/BugReporting> >>> <http://surfer.nmr.mgh.harvard.edu/fswiki/BugReporting> >>> <http://surfer.nmr.mgh.harvard.edu/fswiki/BugReporting> >>> <http://surfer.nmr.mgh.harvard.edu/fswiki/BugReporting> >>> FileDrop: >>> www.nmr.mgh.harvard.edu/facility/filedrop/index.html >>> <http://www.nmr.mgh.harvard.edu/facility/filedrop/index.html> >>> <http://www.nmr.mgh.harvard.edu/facility/filedrop/index.html> >>> <http://www.nmr.mgh.harvard.edu/facility/filedrop/index.html> >>> <http://www.nmr.mgh.harvard.edu/facility/filedrop/index.html> >>> >>> >>> >>> >>> The information in this e-mail is intended >>> only for >>> the person >>> to whom it is >>> addressed. If you believe this e-mail was sent >>> to you >>> in error >>> and the e-mail >>> contains patient information, please contact >>> the Partners >>> Compliance HelpLine at >>> http://www.partners.org/complianceline . If the e-mail was >>> sent to you in error >>> but does not contain patient information, please >>> contact the >>> sender and properly >>> dispose of the e-mail. >>> >>> >>> >>> >>> -- -Ryan >>> >>> >>> -- Douglas N. Greve, Ph.D. >>> MGH-NMR Center >>> greve(a)nmr.mgh.harvard.edu<mailto:greve@nmr.mgh.harvard.edu> >>> <mailto:greve@nmr.mgh.harvard.edu >>> <mailto:greve@nmr.mgh.harvard.edu>> >>> <mailto:greve@nmr.mgh.harvard.edu >>> <mailto:greve@nmr.mgh.harvard.edu> >>> <mailto:greve@nmr.mgh.harvard.edu >>> <mailto:greve@nmr.mgh.harvard.edu>>> >>> Phone Number: 617-724-2358<tel:617-724-2358> >>> <tel:617-724-2358<tel:617-724-2358>> >>> <tel:617-724-2358<tel:617-724-2358> <tel:617-724-2358 >>> <tel:617-724-2358>>> >>> Fax: 617-726-7422<tel:617-726-7422> >>> <tel:617-726-7422<tel:617-726-7422>> <tel:617-726-7422 >>> <tel:617-726-7422> >>> <tel:617-726-7422<tel:617-726-7422>>> >>> >>> Bugs: >>> surfer.nmr.mgh.harvard.edu/fswiki/BugReporting >>> <http://surfer.nmr.mgh.harvard.edu/fswiki/BugReporting> >>> <http://surfer.nmr.mgh.harvard.edu/fswiki/BugReporting> >>> <http://surfer.nmr.mgh.harvard.edu/fswiki/BugReporting> >>> FileDrop: >>> www.nmr.mgh.harvard.edu/facility/filedrop/index.html >>> <http://www.nmr.mgh.harvard.edu/facility/filedrop/index.html> >>> <http://www.nmr.mgh.harvard.edu/facility/filedrop/index.html> >>> <http://www.nmr.mgh.harvard.edu/facility/filedrop/index.html> >>> >>> >>> >>> >>> -- -Ryan >>> >>> >>> -- Douglas N. Greve, Ph.D. >>> MGH-NMR Center >>> greve(a)nmr.mgh.harvard.edu<mailto:greve@nmr.mgh.harvard.edu> >>> <mailto:greve@nmr.mgh.harvard.edu >>> <mailto:greve@nmr.mgh.harvard.edu>> >>> Phone Number: 617-724-2358<tel:617-724-2358> >>> <tel:617-724-2358<tel:617-724-2358>> >>> Fax: 617-726-7422<tel:617-726-7422> <tel:617-726-7422 >>> <tel:617-726-7422>> >>> >>> Bugs: surfer.nmr.mgh.harvard.edu/fswiki/BugReporting >>> <http://surfer.nmr.mgh.harvard.edu/fswiki/BugReporting> >>> <http://surfer.nmr.mgh.harvard.edu/fswiki/BugReporting> >>> FileDrop: >>> www.nmr.mgh.harvard.edu/facility/filedrop/index.html >>> <http://www.nmr.mgh.harvard.edu/facility/filedrop/index.html> >>> <http://www.nmr.mgh.harvard.edu/facility/filedrop/index.html> >>> >>> >>> >>> >>> -- -Ryan >>> >>> >>> -- Douglas N. Greve, Ph.D. >>> MGH-NMR Center >>> greve(a)nmr.mgh.harvard.edu<mailto:greve@nmr.mgh.harvard.edu> >>> Phone Number: 617-724-2358<tel:617-724-2358> >>> Fax: 617-726-7422<tel:617-726-7422> >>> >>> Bugs: surfer.nmr.mgh.harvard.edu/fswiki/BugReporting >>> <http://surfer.nmr.mgh.harvard.edu/fswiki/BugReporting> >>> FileDrop: www.nmr.mgh.harvard.edu/facility/filedrop/index.html >>> <http://www.nmr.mgh.harvard.edu/facility/filedrop/index.html> >>> >>> >>> >>> >>> -- >>> -Ryan >> -- >> Douglas N. Greve, Ph.D. >> MGH-NMR Center >> greve(a)nmr.mgh.harvard.edu >> Phone Number: 617-724-2358 >> Fax: 617-726-7422 >> >> Bugs: surfer.nmr.mgh.harvard.edu/fswiki/BugReporting >> FileDrop: www.nmr.mgh.harvard.edu/facility/filedrop/index.html >> > -- Douglas N. Greve, Ph.D. MGH-NMR Center greve(a)nmr.mgh.harvard.edu Phone Number: 617-724-2358 Fax: 617-726-7422 Bugs: surfer.nmr.mgh.harvard.edu/fswiki/BugReporting FileDrop: www.nmr.mgh.harvard.edu/facility/filedrop/index.html

2 3

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