Freesurfer

freesurfer@nmr.mgh.harvard.edu

15 participants
30097 discussions

Monte Carlo
by Peter Boulos 05 Aug '13

05 Aug '13

Good afternoon, I am getting much different results in my QDEC before and after running monte carlo cluster correction. Upon initially running the QDEC I have what appears to be a significant group difference in the prefrontal region that does not show up after I run the Monte Carlo but at the same time there appears to be no result in the postcentral gyrus region prior to running the Monte Carlo but after running it, there is a huge result in that region. Is there something I missed? Peter

2 1

Error with recon-all: You are trying to re-run an existing subject
by Joseph Andreano 05 Aug '13

05 Aug '13

Hi All, I'm trying to use recon-all on some structural data, and when I drop the command (specifically, recon-all -i /cluster/iaslab/SPAR/mri/recon/3danat/003/001.mgz -subjid SPAR_016_130708), I get this error message: ERROR: You are trying to re-run an existing subject with (possibly) new input data (-i). If this is truly new input data, you should delete the subject folder and re-run, or specify a different subject name. If you are continuing an analysis of an existing subject, then omit all -i flags. I have tried all the options suggested in the error message, and none work. I can't delete the subject folder, because no such folder exists. I tried running the command with a different subject name, and although the command appeared to complete without error, no folder with the new name was created, and no files were generated. I tried removing the -i flags, and I got this: ERROR: nothing to do. Any suggestions? Thanks, Joe Andreano _________________________________ Joseph M. Andreano, PhD Postdoctoral Researcher Interdisciplinary Affective Science Laboratory Massachusetts General Hospital _________________________________

3 2

Re: [Freesurfer] Fwd: infant atlas segmentation
by Mark Plantz 05 Aug '13

05 Aug '13

Just as an update, it turns out that my segmentation volume had been slightly altered during the conversion from .nii to .mgz. I completely forgot to use the -rt nearest flag to prevent the labels from becoming distorted. That is why the segmentation looked so fuzzy with various regions labeled incorrectly. Apparently, I should check the basics before overcomplicating the problem, haha. Thanks for the help everyone! On Thu, Aug 1, 2013 at 9:36 AM, Mark Plantz < markplantz2016(a)u.northwestern.edu> wrote: > Sounds good. I also just realized that the segmentation values are varying > from 0-255, which makes me think that the file is only designed for the > grayscale/heat/etc. settings [where 0 is darkest regions and 255 is > brightest regions]. Is that a valid assumption? Also, if this is the case, > would it be impossible to create a .gca file using mri_ca_train with these > files? > > Thanks for the help. > > MP > > > On Wed, Jul 31, 2013 at 8:43 PM, Douglas Greve <greve(a)nmr.mgh.harvard.edu>wrote: > >> >> Just make sure that you create a new file and do not repeat index numbers. >> >> >> On 7/31/13 2:02 PM, Mark Plantz wrote: >> >> That makes sense. Wouldn't that cause there to be some overlap between >> different regions, since the same index #'s used by the two programs >> (FreeSurfer & MRIcro) correspond to different brain regions? >> >> >> On Tue, Jul 30, 2013 at 12:50 PM, Douglas Greve < >> greve(a)nmr.mgh.harvard.edu> wrote: >> >>> >>> for every line in that file, you will need to create a line in the new >>> LUT, something like >>> >>> >>> 8 Frontal_Mid_R 0 255 0 0 >>> >>> This will make the right mid frontal green = (0,255,0) >>> >>> >>> >>> >>> On 7/30/13 9:55 AM, Mark Plantz wrote: >>> >>> Hmm, so I received the text part of the LUT. Looks like this is >>> completely different from the segmented regions that we would want. >>> [attached]. Can't seem to understand how this text file could be related to >>> the default FreeSurfer LUT. It looks like the labeling for an AAL map. This >>> probably wont' work will it? >>> >>> - Mark >>> >>> >>> On Tue, Jul 30, 2013 at 8:47 AM, Bruce Fischl < >>> fischl(a)nmr.mgh.harvard.edu> wrote: >>> >>>> the UNC one? No, you should ask them >>>> On Tue, 30 Jul 2013, Mark Plantz wrote: >>>> >>>> >>>>> >>>>> ---------- Forwarded message ---------- >>>>> From: Mark Plantz <markplantz2016(a)u.northwestern.edu> >>>>> Date: Tue, Jul 30, 2013 at 8:39 AM >>>>> Subject: Re: [Freesurfer] infant atlas segmentation >>>>> To: Bruce Fischl <fischl(a)nmr.mgh.harvard.edu> >>>>> >>>>> >>>>> Just opened up the default FreeSurferColorLUT.txt file. So it looks >>>>> like all >>>>> I have to change is the #No. column of the file, to match the ones in >>>>> the >>>>> other LUT used. >>>>> I actually just received the MRIcro .lut file from the UNC group. >>>>> [attached] >>>>> >>>>> Hopefully this will help with the conversion. However, I still have to >>>>> figure out how to open the file. Any ideas? >>>>> >>>>> >>>>> >>>>> >>>>> On Tue, Jul 30, 2013 at 8:25 AM, Bruce Fischl < >>>>> fischl(a)nmr.mgh.harvard.edu> >>>>> wrote: >>>>> Hi Mark >>>>> >>>>> creating a FreeSurfer LUT really isn't that hard. Have you >>>>> looked at our standard one? Probably we have the names you >>>>> already want and you just need to change our indices to match >>>>> the ones in your segmentation file (and save it as a different >>>>> LUT) >>>>> >>>>> cheers >>>>> Bruce >>>>> >>>>> On Tue, 30 Jul 2013, Mark Plantz wrote: >>>>> >>>>> Turns out that the files had been labeled using a >>>>> color LUT in a program >>>>> called MRIcro. I am now installing this program >>>>> simply to access the LUT. >>>>> Will it be as simple as exchanging the index values >>>>> from this LUT to a >>>>> custom LUT in FreeSurfer? >>>>> >>>>> >>>>> On Tue, Jul 30, 2013 at 12:35 AM, Douglas Greve >>>>> <greve(a)nmr.mgh.harvard.edu> >>>>> wrote: >>>>> >>>>> The problem is that you need to create a >>>>> completely new LUT. The >>>>> labels that get displayed with the standard >>>>> LUT are going to be >>>>> totally random with respect to what they >>>>> should display. >>>>> >>>>> On 7/29/13 2:20 PM, Mark Plantz wrote: >>>>> Hi Doug, >>>>> Thanks for the reply. I will definitely go into >>>>> the LUT and >>>>> change those values to some specific region. My main >>>>> concern is >>>>> that I think all of these "out of bounds" labels are >>>>> the >>>>> symptoms of some larger problem. The segmentation >>>>> looks very >>>>> strange as compared to a typical segmentation (i.e. >>>>> an >>>>> 'aseg.mgz' file). In fact, the segmentation appears >>>>> to be >>>>> labeling "left-<region" in the right hemisphere. >>>>> Have you seen a >>>>> segmentation file that looks like the once I >>>>> attached before? I >>>>> am used to seeing segmentation files such as the one >>>>> attached to >>>>> this e-mail. >>>>> >>>>> - Mark >>>>> >>>>> >>>>> On Mon, Jul 29, 2013 at 12:28 PM, Douglas Greve >>>>> <greve(a)nmr.mgh.harvard.edu> wrote: >>>>> >>>>> Mark, the only thing that is wrong with the >>>>> out of >>>>> bounds regions is that they are not >>>>> represented in >>>>> the LUT. Once you add an index corresponding >>>>> to the >>>>> index of the segmentation to the LUT, it will >>>>> not >>>>> show up as "out of bounds". The brain mask has >>>>> nothing to do with it. >>>>> best >>>>> doug >>>>> >>>>> >>>>> >>>>> On 7/29/13 12:50 PM, Mark Plantz wrote: >>>>> Sorry about that. I received the manual >>>>> segmentations from a UNC medicalgroup< >>>>> http://www.med.unc.edu/bric/ideagroup/free-softwares/unc-infant-0-1-2 >>>>> -atla >>>>> ses>. I actually asked the main researcher >>>>> about the out of bounds regions. He thinks >>>>> that as long as the segmented file lines up >>>>> with the input volumes, a few out of bounds >>>>> regions might be OK. However, these seg >>>>> volumes look very different from a typical >>>>> .aseg volume that I am used to seeing after >>>>> recon-all is run. >>>>> Maybe the segmentation is simply incompatible with >>>>> FreeSurfer? >>>>> >>>>> Thanks for the help. These files are a nightmare! >>>>> >>>>> - MP >>>>> >>>>> >>>>> On Mon, Jul 29, 2013 at 11:40 AM, Bruce Fischl >>>>> <fischl(a)nmr.mgh.harvard.edu> wrote: >>>>> can you cc the list please? Maybe we >>>>> should start over. Where did you get the >>>>> manual segmentations from? >>>>> >>>>> On Mon, 29 Jul 2013, Mark Plantz wrote: >>>>> >>>>> Ahh, right. So it looks like >>>>> the red regions appear to be >>>>> averaged around 248. I am >>>>> not sure why that is the >>>>> case or if it has >>>>> any significance. I attached >>>>> a screen shot for >>>>> reference. >>>>> >>>>> >>>>> On Mon, Jul 29, 2013 at >>>>> 11:29 AM, Bruce Fischl >>>>> <fischl(a)nmr.mgh.harvard.edu> >>>>> wrote: >>>>> it isn't a >>>>> registration file. You >>>>> should just specify it as a >>>>> volume on the freeview >>>>> command line, the same as >>>>> brainmask.mgz >>>>> >>>>> On Mon, 29 Jul 2013, >>>>> Mark Plantz wrote: >>>>> >>>>> I actually tried >>>>> to view the brainmask.mgz >>>>> file with the segmentation >>>>> file [Freeview calls it >>>>> 'registration >>>>> file' I believe]. >>>>> For some reason, >>>>> the file will load without >>>>> segmentation, but when I >>>>> attempt to add the >>>>> registration >>>>> file, I get an >>>>> error >>>>> message: >>>>> "Failed to load >>>>> MRI >>>>> ~/.../../../brainmask.mgz >>>>> >>>>> Could this >>>>> potentially be part of the >>>>> problem? >>>>> >>>>> Thanks >>>>> >>>>> MP >>>>> >>>>> >>>>> On Mon, Jul 29, >>>>> 2013 at 10:57 AM, Mark >>>>> Plantz >>>>> <markplantz2016(a)u.northwestern.edu> >>>>> wrote: >>>>> >>>>> It looks >>>>> like the values vary from >>>>> 20-120 depending on which >>>>> region I run the cursor >>>>> over. >>>>> However, aren't >>>>> those the >>>>> values >>>>> that correspond to the >>>>> brain.mgz regions? Is there >>>>> another way to find the >>>>> segmentation >>>>> values? >>>>> >>>>> >>>>> On Mon, Jul 29, >>>>> 2013 at 10:37 AM, Bruce >>>>> Fischl >>>>> <fischl(a)nmr.mgh.harvard.edu> >>>>> wrote: >>>>> I mean the >>>>> segmentation values that >>>>> give you the "out of bounds" >>>>> message >>>>> On Mon, 29 >>>>> Jul 2013, Mark Plantz wrote: >>>>> >>>>> Hi >>>>> Bruce, >>>>> Do >>>>> you mean the brainmask.mgz >>>>> values? I'm not sure what >>>>> the segmentation #'s exactly >>>>> are. >>>>> >>>>> >>>>> Thanks! >>>>> >>>>> MP >>>>> >>>>> >>>>> On >>>>> Mon, Jul 29, 2013 at 10:17 >>>>> AM, Bruce Fischl >>>>> <fischl(a)nmr.mgh.harvard.edu> >>>>> wrote: >>>>> >>>>> Hi Mark >>>>> >>>>> >>>>> >>>>> what #s are those >>>>> segmentations? It should be >>>>> trivial to just add them to >>>>> the end of >>>>> the >>>>> LUT. >>>>> I wouldn't let them be >>>>> >>>>> out of bounds as there >>>>> might be code around that >>>>> might ignore them then. >>>>> >>>>> >>>>> cheers >>>>> >>>>> Bruce >>>>> >>>>> >>>>> On Mon, 29 Jul 2013, Mark >>>>> Plantz wrote: >>>>> >>>>> >>>>> Hi Doug, >>>>> >>>>> Thanks for >>>>> the reply. After doing some >>>>> research, it looks like >>>>> messing >>>>> with the >>>>> LUT >>>>> might be a >>>>> >>>>> risky decision [and >>>>> way >>>>> >>>>> out of my >>>>> abilities!]. >>>>> >>>>> >>>>> If I were to use >>>>> this segmentation file to >>>>> create a .gca atlas using >>>>> the >>>>> command >>>>> >>>>> mri_ca_train, do you >>>>> >>>>> think it would yield >>>>> >>>>> problems or be >>>>> inaccurate? I guess what I >>>>> am trying to figure out is >>>>> if the >>>>> color >>>>> >>>>> lookup values are even >>>>> >>>>> significant when >>>>> using >>>>> >>>>> the segmentation >>>>> file to create an atlas? >>>>> >>>>> >>>>> Thanks for all of >>>>> the help with this. >>>>> >>>>> >>>>> Best, >>>>> >>>>> >>>>> MP >>>>> >>>>> >>>>> p.s. I attached the >>>>> photo of the segmentation >>>>> volume because this e-mail >>>>> is sort >>>>> of >>>>> old >>>>> >>>>> >>>>> >>>>> On Wed, Jul 24, 2013 >>>>> at 2:39 PM, Douglas N Greve >>>>> <greve(a)nmr.mgh.harvard.edu> >>>>> wrote: >>>>> >>>>> you need a new >>>>> LUT. See my comment from a >>>>> few emails ago. >>>>> >>>>> On 07/24/2013 >>>>> 03:29 PM, Mark Plantz wrote: >>>>> >>>>> I'm not >>>>> actually quite sure what it >>>>> means either. When I use the >>>>> command >>>>> line: >>>>> >>>>> >>>>> tkmedit >>>>> $Subject brain.mgz >>>>> -segmentation <seg.mgz>, >>>>> >>>>> >>>>> I can run the >>>>> cursor over various regions >>>>> and the name of the region >>>>> should pop >>>>> up. >>>>> For some >>>>> >>>>> reason, the red >>>>> >>>>> regions are >>>>> simply labeled as "out of >>>>> bounds." >>>>> >>>>> >>>>> I'll keep >>>>> messing with tkmedit and let >>>>> you know if I find out what >>>>> the >>>>> problem >>>>> is. >>>>> >>>>> >>>>> Thanks guys! >>>>> >>>>> >>>>> MP >>>>> >>>>> >>>>> >>>>> On Wed, Jul 24, 2013 >>>>> at 2:26 PM, Douglas N Greve >>>>> <greve(a)nmr.mgh.harvard.edu >>>>> >>>>> >>>>> <mailto:greve@nmr.mgh.harvard.edu>> >>>>> >>>>> wrote: >>>>> >>>>> >>>>> what do you mean >>>>> that they are out of bounds? >>>>> >>>>> >>>>> On 07/24/2013 >>>>> 03:25 PM, Mark Plantz wrote: >>>>> >>>>> >>>>> I guess the >>>>> problem is that those >>>>> regions should not be out of >>>>> >>>>> bounds. >>>>> Maybe I need to create a new >>>>> Lookup Table for the >>>>> >>>>> infant >>>>> mri's? Is that possible to >>>>> do? >>>>> >>>>> >>>>> >>>>> On Wed, Jul >>>>> 24, 2013 at 2:21 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: >>>>> >>>>> >>>>> Hi Mark, >>>>> please post to the list and >>>>> not to me. >>>>> >>>>> thanks >>>>> >>>>> doug >>>>> >>>>> >>>>> On >>>>> 07/24/2013 03:21 PM, Mark >>>>> Plantz wrote: >>>>> >>>>> >>>>> I >>>>> guess the problem is that >>>>> those regions should not >>>>> >>>>> be out of >>>>> >>>>> >>>>> bounds. Maybe I need to >>>>> create a new Lookup Table >>>>> for the >>>>> >>>>> >>>>> infant mri's? Is that >>>>> possible to do? >>>>> >>>>> >>>>> >>>>> On >>>>> Wed, Jul 24, 2013 at 2:15 >>>>> 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: >>>>> >>>>> >>>>> >>>>> >>>>> what is the problem exactly? >>>>> The fact that there >>>>> >>>>> are red >>>>> >>>>> >>>>> regions >>>>> >>>>> >>>>> or that that the red regions >>>>> are labeled as "Out of >>>>> >>>>> >>>>> Bounds"? If >>>>> >>>>> >>>>> the latter, you will need to >>>>> create a LUT that >>>>> >>>>> matches your >>>>> >>>>> >>>>> regions. the out of bounds >>>>> means that the index in the >>>>> >>>>> >>>>> volume does >>>>> >>>>> >>>>> not match an index in the >>>>> LUT. >>>>> >>>>> >>>>> doug >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> On 07/24/2013 01:26 PM, Mark >>>>> Plantz wrote: >>>>> >>>>> >>>>> >>>>> Finally got the >>>>> registration to work. >>>>> However, it >>>>> >>>>> >>>>> looks like >>>>> >>>>> >>>>> the out of bounds >>>>> regions (in red) are still >>>>> >>>>> present >>>>> (even >>>>> >>>>> >>>>> though the regions are >>>>> well within our >>>>> >>>>> boundaries). >>>>> Is >>>>> >>>>> that >>>>> >>>>> >>>>> expected since they were >>>>> labeled in the original >>>>> >>>>> >>>>> segmentation >>>>> >>>>> >>>>> volume? Is there anyway >>>>> to correct those? >>>>> >>>>> >>>>> >>>>> Thanks for all of the >>>>> help! >>>>> >>>>> >>>>> >>>>> - Mark >>>>> >>>>> >>>>> p.s. I attached a >>>>> picture of the original >>>>> >>>>> brain.mgz >>>>> file >>>>> >>>>> >>>>> viewed with the >>>>> corrected segmentation >>>>> volume >>>>> >>>>> >>>>> >>>>> >>>>> On Wed, Jul 24, 2013 at >>>>> 12:22 PM, Mark Plantz >>>>> >>>>> >>>>> >>>>> <markplantz2016(a)u.northwestern.edu >>>>> >>>>> >>>>> >>>>> <mailto:markplantz2016@u.northwestern.edu> >>>>> >>>>> >>>>> >>>>> <mailto:markplantz2016@u.northwestern.edu >>>>> >>>>> >>>>> >>>>> <mailto:markplantz2016@u.northwestern.edu>> >>>>> >>>>> >>>>> >>>>> >>>>> <mailto:markplantz2016@u.northwestern.edu >>>>> >>>>> >>>>> >>>>> <mailto:markplantz2016@u.northwestern.edu> >>>>> >>>>> >>>>> >>>>> <mailto:markplantz2016@u.northwestern.edu >>>>> >>>>> >>>>> >>>>> <mailto:markplantz2016@u.northwestern.edu>>> >>>>> >>>>> >>>>> >>>>> >>>>> <mailto:markplantz2016@u.northwestern.edu >>>>> >>>>> >>>>> >>>>> <mailto:markplantz2016@u.northwestern.edu> >>>>> >>>>> >>>>> >>>>> <mailto:markplantz2016@u.northwestern.edu >>>>> >>>>> >>>>> >>>>> <mailto:markplantz2016@u.northwestern.edu>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> <mailto:markplantz2016@u.northwestern.edu >>>>> >>>>> >>>>> >>>>> <mailto:markplantz2016@u.northwestern.edu> >>>>> >>>>> >>>>> >>>>> <mailto:markplantz2016@u.northwestern.edu >>>>> >>>>> >>>>> >>>>> <mailto:markplantz2016@u.northwestern.edu>>>>> >>>>> wrote: >>>>> >>>>> >>>>> >>>>> Finally got the >>>>> registration to work. >>>>> >>>>> However, it >>>>> >>>>> >>>>> looks >>>>> >>>>> >>>>> like the >>>>> >>>>> >>>>> out of bound regions >>>>> (in red) are still >>>>> >>>>> prevalent. >>>>> >>>>> >>>>> Is >>>>> that >>>>> >>>>> >>>>> expected since they >>>>> were present in the >>>>> >>>>> original >>>>> >>>>> >>>>> segmentation >>>>> >>>>> >>>>> volume? Would there >>>>> >>>>> be anyway to correct >>>>> >>>>> those? >>>>> >>>>> >>>>> >>>>> Thanks for all the >>>>> help! >>>>> >>>>> >>>>> >>>>> - MP >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> On Wed, Jul 24, 2013 >>>>> at 11:11 AM, Mark Plantz >>>>> >>>>> >>>>> >>>>> >>>>> <markplantz2016(a)u.northwestern.edu >>>>> >>>>> >>>>> >>>>> <mailto:markplantz2016@u.northwestern.edu> >>>>> >>>>> >>>>> >>>>> <mailto:markplantz2016@u.northwestern.edu >>>>> >>>>> >>>>> >>>>> <mailto:markplantz2016@u.northwestern.edu>> >>>>> >>>>> >>>>> >>>>> >>>>> <mailto:markplantz2016@u.northwestern.edu >>>>> >>>>> >>>>> >>>>> <mailto:markplantz2016@u.northwestern.edu> >>>>> >>>>> >>>>> >>>>> <mailto:markplantz2016@u.northwestern.edu >>>>> >>>>> >>>>> >>>>> <mailto:markplantz2016@u.northwestern.edu>>> >>>>> >>>>> >>>>> >>>>> >>>>> <mailto:markplantz2016@u.northwestern.edu >>>>> >>>>> >>>>> >>>>> <mailto:markplantz2016@u.northwestern.edu> >>>>> >>>>> >>>>> >>>>> <mailto:markplantz2016@u.northwestern.edu >>>>> >>>>> >>>>> >>>>> <mailto:markplantz2016@u.northwestern.edu>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> <mailto:markplantz2016@u.northwestern.edu >>>>> >>>>> >>>>> >>>>> <mailto:markplantz2016@u.northwestern.edu> >>>>> >>>>> >>>>> >>>>> <mailto:markplantz2016@u.northwestern.edu >>>>> >>>>> >>>>> >>>>> <mailto:markplantz2016@u.northwestern.edu>>>>> >>>>> wrote: >>>>> >>>>> >>>>> >>>>> Nevermind, it >>>>> turned out to be a >>>>> >>>>> permissions >>>>> >>>>> >>>>> issue. >>>>> >>>>> >>>>> Thanks! >>>>> >>>>> >>>>> >>>>> >>>>> On Wed, Jul 24, >>>>> 2013 at 10:12 AM, Mark >>>>> >>>>> >>>>> Plantz >>>>> >>>>> >>>>> >>>>> <markplantz2016(a)u.northwestern.edu >>>>> >>>>> >>>>> >>>>> <mailto:markplantz2016@u.northwestern.edu> >>>>> >>>>> >>>>> >>>>> <mailto:markplantz2016@u.northwestern.edu >>>>> >>>>> >>>>> >>>>> <mailto:markplantz2016@u.northwestern.edu>> >>>>> >>>>> >>>>> >>>>> >>>>> <mailto:markplantz2016@u.northwestern.edu >>>>> >>>>> >>>>> >>>>> <mailto:markplantz2016@u.northwestern.edu> >>>>> >>>>> >>>>> >>>>> <mailto:markplantz2016@u.northwestern.edu >>>>> >>>>> >>>>> >>>>> <mailto:markplantz2016@u.northwestern.edu>>> >>>>> >>>>> >>>>> >>>>> >>>>> <mailto:markplantz2016@u.northwestern.edu >>>>> >>>>> >>>>> >>>>> <mailto:markplantz2016@u.northwestern.edu> >>>>> >>>> >>> >>> >>> _______________________________________________ >>> Freesurfer mailing listFreesurfer@nmr.mgh.harvard.eduhttps://mail.nmr.mgh.harvard.edu/mailman/listinfo/freesurfer >>> >>> >>> >>> _______________________________________________ >>> Freesurfer mailing list >>> Freesurfer(a)nmr.mgh.harvard.edu >>> https://mail.nmr.mgh.harvard.edu/mailman/listinfo/freesurfer >>> >>> >>> 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 8

Controlling for shape (and size) of a ROI in co-registration
by pfotiad＠nmr.mgh.harvard.edu 05 Aug '13

05 Aug '13

Hi FS Community, Is there a way to control for the size and shape of a ROI when applying co-registration? For instance, I drew a ROI in a scan through freesurfer, and then when I coregistered that ROI to another scan, the resulting ROI had a different shape and number of voxels compared to the original ROI. IS there a way to control for that? Thank you for your time. Best, Panos

2 2

trouble with bias correction
by Keith Jamison 05 Aug '13

05 Aug '13

Some of the T1 scans I'm working with have pretty severe intensity inhomogeneity, with the signal dropping off significantly toward the sides of the head. This is not being adequately corrected and the segmentation is missing considerable portions of gray matter in those areas. I've played with some bias correction techniques but so far I have not been very successful. In the attached screenshots, you can see the problem on the left side of the brain. The skull drops down significantly and in the ribbon file we lose all of the gray matter in that area. Is there a way to use control points to specify gray matter as well as white? Is there another obvious fix for this kind of problem? Thanks! -Keith

1 0

long_mris_slopes sign of do-rate
by vbrunsch＠nmr.mgh.harvard.edu 05 Aug '13

05 Aug '13

Dear Freesurfer experts, I have followed the LongitudinalTutorial with two time points + two groups and now, after looking at the output of the qdec analysis, I just want to make sure I haven't made a sign error as for the control group the difference is as expected around 0 but for the experimental group I see negative values (= thinning?) all over the place which seems weird, just want to make sure I got this right: I set the time variable to 0 for the baseline scan and to 1 for the after-intervention-scan. Is it correct that for do-rate the calculation is then only <thickness of tp2> - <thickness of tp1> and not the other way around? I ask because in the long_mris_slopes -help it says that do-rate would yield the "thinning in mm/time" and if this means that a positive value stands for thinning then this would contradict what I understood from the Tutorial where it says for the rate "thick2-thick1" is calculated, so a positive value should mean "thickening". Also, how does long_mris_slopes know which one is tp1 and which one is tp2? I assume it takes the first entry in the fsid column of long.qdec.table.dat as tp1 and the second entry below as tp2? Hm, I see no other possibilities of making a sign error during the whole process, did anyone report a similar issue? Thanks for your help! Best, Vincent

2 1

Re: [Freesurfer] TR,TE,TI,FA variability w/ mri_ca_train
by Mark Plantz 05 Aug '13

05 Aug '13

For some reason, when I run that command, I get the following output: Input volume is : seg_mov Output volume is : seg_mov_2 There are no errors, but when I check "mri_info" of the output file, the TR, TE, etc. values are still non-zero. Any ideas what could cause that to happen? Thanks! MP On Mon, Aug 5, 2013 at 11:35 AM, Bruce Fischl <fischl(a)nmr.mgh.harvard.edu>wrote: > yes, I think so > > On Mon, 5 Aug 2013, Mark Plantz wrote: > > thank you. Would the command simply be something like this: mri_modify >> -tr 0 -te 0 -ti 0 -fa 0 <input.mgz> <output.mgz> ? >> >> >> On Thu, Aug 1, 2013 at 1:41 PM, Bruce Fischl <fischl(a)nmr.mgh.harvard.edu> >> wrote: >> Hi Mark >> >> the formatting got messed up so I can't parse your table. You can >> get around this using mri_modify, and just setting >> everything to 0. As for the effects, look at the images and see >> what you think. >> >> cheers >> Bruce >> >> On Thu, 1 Aug 2013, Mark Plantz wrote: >> >> Hello freesurfers, >> I currently have a series of images with various >> TR,TE,TI,FA values. I >> would like to use mri_ca_train to create a .gca atlas based >> on these >> segmented volumes. Unfortunately, they all have slightly >> different control >> parameters (TR,TE,TI,FA). Is there any way around this >> problem, or would it >> be best to break the subjects into multiple groups with the >> same control >> parameters? >> >> Here are the various parameters: [each row is a subject] >> >> TR >> TE >> TI >> flip angle >> 9.38 >> 3.86 >> 450 >> 12 >> 9.34 >> 3.86 >> 450 >> 12 >> 9.38 >> 3.86 >> 450 >> 12 >> 9.38 >> 3.86 >> 450 >> 12 >> 9.34 >> 3.86 >> 450 >> 12 >> 9.44 >> 3.87 >> 450 >> 12 >> 9.39 >> 3.86 >> 450 >> 12 >> 2065.98 >> 7.61 >> 886.92 >> 90 >> 9.45 >> 3.89 >> 450 >> 12 >> 9.41 >> 3.87 >> 450 >> 12 >> 9.41 >> 3.87 >> 450 >> 12 >> 9.42 >> 3.91 >> 450 >> 12 >> 9.38 >> 3.86 >> 450 >> 12 >> 9.38 >> 3.86 >> 450 >> 12 >> 9.44 >> 3.86 >> 450 >> 12 >> 9.44 >> 3.86 >> 450 >> 12 >> 9.38 >> 3.86 >> 450 >> 12 >> 9.38 >> 3.86 >> 450 >> 12 >> 9.38 >> 3.86 >> 450 >> 12 >> 9.34 >> 3.86 >> 450 >> 12 >> 9.34 >> 3.86 >> 450 >> 12 >> 9.39 >> 3.86 >> 450 >> 12 >> 1900 >> 2.6 >> 900 >> 9 >> 1900 >> 2.6 >> 900 >> 9 >> 1900 >> 2.6 >> 900 >> 9 >> 9.41 >> 3.87 >> 450 >> 12 >> 9.41 >> 3.87 >> 450 >> 12 >> 9.41 >> 3.87 >> 450 >> 12 >> 1900 >> 2.6 >> 900 >> 9 >> 9.41 >> 3.87 >> 450 >> 12 >> 1900 >> 2.6 >> 900 >> 9 >> 1900 >> 2.6 >> 900 >> 9 >> >> Thank you in advance. >> >> -Mark >> >> >> >> >> >> 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<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. >> >> >> >>

2 3

hemispheric masks?
by John Richey 05 Aug '13

05 Aug '13

Dear freesurfer experts, I was wondering whether there is an existing mask for the left and right hemispheres for fsaverage. I can't seem to find any documentation of this, but perhaps I am missing something? Thanks in advance, John.

2 1

Fwd: TR,TE,TI,FA variability w/ mri_ca_train
by Mark Plantz 05 Aug '13

05 Aug '13

---------- Forwarded message ---------- From: Mark Plantz <markplantz2016(a)u.northwestern.edu> Date: Mon, Aug 5, 2013 at 11:32 AM Subject: Re: [Freesurfer] TR,TE,TI,FA variability w/ mri_ca_train To: Bruce Fischl <fischl(a)nmr.mgh.harvard.edu> thank you. Would the command simply be something like this: mri_modify -tr 0 -te 0 -ti 0 -fa 0 <input.mgz> <output.mgz> ? On Thu, Aug 1, 2013 at 1:41 PM, Bruce Fischl <fischl(a)nmr.mgh.harvard.edu>wrote: > Hi Mark > > the formatting got messed up so I can't parse your table. You can get > around this using mri_modify, and just setting everything to 0. As for the > effects, look at the images and see what you think. > > cheers > Bruce > > > On Thu, 1 Aug 2013, Mark Plantz wrote: > > Hello freesurfers, >> I currently have a series of images with various TR,TE,TI,FA values. I >> would like to use mri_ca_train to create a .gca atlas based on these >> segmented volumes. Unfortunately, they all have slightly different control >> parameters (TR,TE,TI,FA). Is there any way around this problem, or would >> it >> be best to break the subjects into multiple groups with the same control >> parameters? >> >> Here are the various parameters: [each row is a subject] >> >> TR >> TE >> TI >> flip angle >> 9.38 >> 3.86 >> 450 >> 12 >> 9.34 >> 3.86 >> 450 >> 12 >> 9.38 >> 3.86 >> 450 >> 12 >> 9.38 >> 3.86 >> 450 >> 12 >> 9.34 >> 3.86 >> 450 >> 12 >> 9.44 >> 3.87 >> 450 >> 12 >> 9.39 >> 3.86 >> 450 >> 12 >> 2065.98 >> 7.61 >> 886.92 >> 90 >> 9.45 >> 3.89 >> 450 >> 12 >> 9.41 >> 3.87 >> 450 >> 12 >> 9.41 >> 3.87 >> 450 >> 12 >> 9.42 >> 3.91 >> 450 >> 12 >> 9.38 >> 3.86 >> 450 >> 12 >> 9.38 >> 3.86 >> 450 >> 12 >> 9.44 >> 3.86 >> 450 >> 12 >> 9.44 >> 3.86 >> 450 >> 12 >> 9.38 >> 3.86 >> 450 >> 12 >> 9.38 >> 3.86 >> 450 >> 12 >> 9.38 >> 3.86 >> 450 >> 12 >> 9.34 >> 3.86 >> 450 >> 12 >> 9.34 >> 3.86 >> 450 >> 12 >> 9.39 >> 3.86 >> 450 >> 12 >> 1900 >> 2.6 >> 900 >> 9 >> 1900 >> 2.6 >> 900 >> 9 >> 1900 >> 2.6 >> 900 >> 9 >> 9.41 >> 3.87 >> 450 >> 12 >> 9.41 >> 3.87 >> 450 >> 12 >> 9.41 >> 3.87 >> 450 >> 12 >> 1900 >> 2.6 >> 900 >> 9 >> 9.41 >> 3.87 >> 450 >> 12 >> 1900 >> 2.6 >> 900 >> 9 >> 1900 >> 2.6 >> 900 >> 9 >> >> Thank you in advance. >> >> -Mark >> >> >> >> > > 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<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. >

1 0

Re: [Freesurfer] Trac-all question
by Anastasia Yendiki 05 Aug '13

05 Aug '13

Hi Alan - On the tutorial page you need to follow the directions under "If you are not at an organized course", and $TUTORIAL_DATA is whatever directory you have downloaded the tutorial data in. Please address questions to the list and not to me personally, as other people may have the same issue and this way the answers get archived. Thanks, a.y On Mon, 5 Aug 2013, Alan Francis wrote: > Hi Anastasia: > > Sorry about being a pest. One more question. I am running the Tutorial data > to get a better understanding of Tracula. When I type $TUTORIAL_DATA, it > keeps saying Undefined variable. Could you please help me. > > Thanks, > > Alan > > csh::alanf@cerebro[/autofs/space/dali_003/users/BW_project_DTI/FreeSurfer_5.3_Data/TUTORIAL_D > ATA/diffusion_recons] : setenv FREESURFER_HOME > /usr/local/freesurfer/stable5_3_0/ > csh::alanf@cerebro[/autofs/space/dali_003/users/BW_project_DTI/FreeSurfer_5.3_Data/TUTORIAL_D > ATA/diffusion_recons] : source $FREESURFER_HOME/Set > SetUpFreeSurfer.csh* SetUpFreeSurfer.sh* > csh::alanf@cerebro[/autofs/space/dali_003/users/BW_project_DTI/FreeSurfer_5.3_Data/TUTORIAL_D > ATA/diffusion_recons] : source $FREESURFER_HOME/SetUpFreeSurfer.csh > -------- freesurfer-Linux-centos6_x86_64-stable-v5.3.0-20130514 -------- > Setting up environment for FreeSurfer/FS-FAST (and FSL) > FREESURFER_HOME /usr/local/freesurfer/stable5_3_0/ > FSFAST_HOME /usr/local/freesurfer/stable5_3_0//fsfast > FSF_OUTPUT_FORMAT nii.gz > SUBJECTS_DIR /usr/local/freesurfer/stable5_3_0//subjects > MNI_DIR /usr/local/freesurfer/stable5_3_0//mni > FSL_DIR /usr/pubsw/packages/fsl/current > csh::alanf@cerebro[/autofs/space/dali_003/users/BW_project_DTI/FreeSurfer_5.3_Data/TUTORIAL_D > ATA/diffusion_recons] : setenv SUBJECTS_DIR $TUTORIAL_DATA/d > $TUTORIAL_DATA/ not found > > csh::alanf@cerebro[/autofs/space/dali_003/users/BW_project_DTI/FreeSurfer_5.3_Data/TUTORIAL_D > ATA/diffusion_recons] : setenv SUBJECTS_DIR /autofs/space/d > dali_001/ dali_002/ dali_003/ > csh::alanf@cerebro[/autofs/space/dali_003/users/BW_project_DTI/FreeSurfer_5.3_Data/TUTORIAL_D > ATA/diffusion_recons] : setenv SUBJECTS_DIR/autofs/space/dali_003/users/BW_project_DTI/FreeSurfer_5.3_Data/TUTORIAL_DA > TA/diffusion_recons/ > csh::alanf@cerebro[/autofs/space/dali_003/users/BW_project_DTI/FreeSurfer_5.3_Data/TUTORIAL_D > ATA/diffusion_recons] : gedit > $TUTORIAL_DATA/diffusion_tutorial/dmrirc.tutorial & > TUTORIAL_DATA: Undefined variable. > csh::alanf@cerebro[/autofs/space/dali_003/users/BW_project_DTI/FreeSurfer_5.3_Data/TUTORIAL_D > ATA/diffusion_recons] : gedit > /TUTORIAL_DATA/diffusion_tutorial/dmrirc.tutorial & > [1] 32742 > csh::alanf@cerebro[/autofs/space/dali_003/users/BW_project_DTI/FreeSurfer_5.3_Data/TUTORIAL_D > ATA/diffusion_recons] : trac-all -prep -c > $TUTORIAL_DATA/diffusion_tutorial/dmrirc.tutorial > TUTORIAL_DATA: Undefined variable. > > > > On Fri, Aug 2, 2013 at 7:16 PM, Alan Francis <alandarkenergy(a)gmail.com> > wrote: > thanks again. > > > On Fri, Aug 2, 2013 at 3:51 PM, Anastasia Yendiki > <ayendiki(a)nmr.mgh.harvard.edu> wrote: > > It can have any name you want. You just have to type the > right name next to the "-c ..." > > On Fri, 2 Aug 2013, Alan Francis wrote: > > Sorry. I have another question. Should I name > the config file dmrirc.txt or > is there any other name? > thank you so much, > > Alan > > > On Fri, Aug 2, 2013 at 2:45 PM, Alan Francis > <alandarkenergy(a)gmail.com> > wrote: > Thanks Anastasia. > > > On Fri, Aug 2, 2013 at 2:26 PM, Anastasia > Yendiki > <ayendiki(a)nmr.mgh.harvard.edu> wrote: > > Hi Alan - All the "set ..." commands for > tracula need to > be in a configuration file. You then > pass that > configuration file as an argument to the > "-c" option of > trac-all. See tutorial: > > > http://surfer.nmr.mgh.harvard.edu/fswiki/FsTutorial/Tracula > > Hope this helps, > a.y > > On Fri, 2 Aug 2013, Alan Francis wrote: > > Hi Anastasia and others: > I have been trying to run Trac all on > five brains. > It keeps giving me the > error message: > > ERROR: run list is longer than subject > list > > My run list is equal to the subject > list: Here is > the environment: > > Thanks for your help, > > Alan > Martinos Center for Biomedical Imaging > > > __________________________________________________________________ > > -------- > > freesurfer-Linux-centos6_x86_64-stable-v5.3.0-20130514 > -------- > > Setting up environment for > FreeSurfer/FS-FAST (and > FSL) > FREESURFER_HOME > /usr/local/freesurfer/stable5_3_0/ > FSFAST_HOME > > /usr/local/freesurfer/stable5_3_0//fsfast > FSF_OUTPUT_FORMAT nii.gz > SUBJECTS_DIR > > /usr/local/freesurfer/stable5_3_0//subjects > MNI_DIR > /usr/local/freesurfer/stable5_3_0//mni > FSL_DIR > /usr/pubsw/packages/fsl/current > csh::alanf@dali[/autofs/space/dali_003/users/BW_project_DTI/FreeSurfer_5.3_ > > Data/diffusion_ > recons] : setenv SUBJECTS_DIR > /autofs/space/d > dali_001/ dali_002/ dali_003/ > csh::alanf@dali[/autofs/space/dali_003/users/BW_project_DTI/FreeSurfer_5.3_ > > Data/diffusion_ > recons] :setenvSUBJECTS_DIR/autofs/space/dali_003/users/BW_project_DTI/FreeSurfer_5. > 3_Data > /diffusion_r > econs/ > csh::alanf@dali[/autofs/space/dali_003/users/BW_project_DTI/FreeSurfer_5.3_ > > Data/diffusion_ > recons] : set dtroot = /autofs/space/d > dali_001/ dali_002/ dali_003/ > csh::alanf@dali[/autofs/space/dali_003/users/BW_project_DTI/FreeSurfer_5.3_ > > Data/diffusion_ > recons] : setdtroot=/autofs/space/dali_003/users/BW_project_DTI/FreeSurfer_5.3_Data/diff > usion_ > r > econs/ > csh::alanf@dali[/autofs/space/dali_003/users/BW_project_DTI/FreeSurfer_5.3_ > > Data/diffusion_ > recons] : set subjlist = (101/ 102/ 103/ > 104/ 105/) > csh::alanf@dali[/autofs/space/dali_003/users/BW_project_DTI/FreeSurfer_5.3_ > > Data/diffusion_ > recons] : set dcmroot = /autofs/space/d > dali_001/ dali_002/ dali_003/ > csh::alanf@dali[/autofs/space/dali_003/users/BW_project_DTI/FreeSurfer_5.3_ > > Data/diffusion_ > recons] : setdcmroot=/autofs/space/dali_003/users/BW_project_DTI/FreeSurfer_5.3_Data/dif > fusion_ > r > econs/ > csh::alanf@dali[/autofs/space/dali_003/users/BW_project_DTI/FreeSurfer_5.3_ > > Data/diffusion_ > recons] : setdcmlist=(101/Diffusion_Recons/20080424_182054563000-000012-000001DTIValeras > 012a001 > . > nii \ > ?102/Diffusion_Recons/20080911_101015358000-000010-000001DIFFUSIONHighResva > > l > erabi1002s010a001.nii \ > ?103/Diffusion_Recons/20080911_140753578000-000010-000001DIFFUSIONHighResva > > l > eraBI1003s010a001.nii \ > ?104/Diffusion_Recons/20080915_160812745000-000010-000001DIFFUSIONHighResVa > > l > eraBI104s010a001.nii \ > ?105/Diffusion_Recons/20080917_190940899000-000016-000001DIFFUSIONHighResVa > > l > eraBI105s016a001.nii \ > ? ) > csh::alanf@dali[/autofs/space/dali_003/users/BW_project_DTI/FreeSurfer_5.3_ > > Data/diffusion_ > recons] : set runlist = (101/ 102/ 103/ 104/ > bem/ mri/ stats/ > > touch/ > Diffusion_Recons/ scripts/ surf/ > > trash/ > label/ src/ tmp/ > > csh::alanf@dali[/autofs/space/dali_003/users/BW_project_DTI/FreeSurfer_5.3_ > > Data/diffusion_ > recons] : set runlist = (101/ 102/ 103/ 104/ > 105/) > csh::alanf@dali[/autofs/space/dali_003/users/BW_project_DTI/FreeSurfer_5.3_ > > Data/diffusion_ > recons] : set bvecfile = > /autofs/space/dbvecs.txt > dali_001/ dali_002/ dali_003/ > csh::alanf@dali[/autofs/space/dali_003/users/BW_project_DTI/FreeSurfer_5.3_ > > Data/diffusion_ > recons] : setbvecfile=/autofs/space/dali_003/users/BW_project_DTI/FreeSurfer_5.3_Data/di > ffusion_ > r > econs/bvecs.txt > csh::alanf@dali[/autofs/space/dali_003/users/BW_project_DTI/FreeSurfer_5.3_ > > Data/diffusion_ > recons] : setbvalfile=/autofs/space/dali_003/users/BW_project_DTI/FreeSurfer_5.3_Data/di > ffusion_ > r > econs/bvals.txt > csh::alanf@dali[/autofs/space/dali_003/users/BW_project_DTI/FreeSurfer_5.3_ > > Data/diffusion_ > recons] : set doeddy = 1 > csh::alanf@dali[/autofs/space/dali_003/users/BW_project_DTI/FreeSurfer_5.3_ > > Data/diffusion_ > recons] : set dorotbvecs = 1 > csh::alanf@dali[/autofs/space/dali_003/users/BW_project_DTI/FreeSurfer_5.3_ > > Data/diffusion_ > recons] : set usemaskanat = 1 > csh::alanf@dali[/autofs/space/dali_003/users/BW_project_DTI/FreeSurfer_5.3_ > > Data/diffusion_ > recons] : set thrbet = 0.3 > csh::alanf@dali[/autofs/space/dali_003/users/BW_project_DTI/FreeSurfer_5.3_ > > Data/diffusion_ > recons] : set doregflt = 0 > csh::alanf@dali[/autofs/space/dali_003/users/BW_project_DTI/FreeSurfer_5.3_ > > Data/diffusion_ > recons] : set doregbbr = 1 > csh::alanf@dali[/autofs/space/dali_003/users/BW_project_DTI/FreeSurfer_5.3_ > > Data/diffusion_ > recons] : set doregmni = 1 > csh::alanf@dali[/autofs/space/dali_003/users/BW_project_DTI/FreeSurfer_5.3_ > > Data/diffusion_ > recons] : set doregcvs = 0 > csh::alanf@dali[/autofs/space/dali_003/users/BW_project_DTI/FreeSurfer_5.3_ > > Data/diffusion_ > recons] : set mnitemp = > $FSLDIR/data/standard/MNI152_T1_1mm_brain.nii.gz > csh::alanf@dali[/autofs/space/dali_003/users/BW_project_DTI/FreeSurfer_5.3_ > > Data/diffusion_ > recons] : set cvstemp = cvs_avg35 > csh::alanf@dali[/autofs/space/dali_003/users/BW_project_DTI/FreeSurfer_5.3_ > > Data/diffusion_ > recons] : set cvstempdir = > $FREESURFER_HOME/subjects > csh::alanf@dali[/autofs/space/dali_003/users/BW_project_DTI/FreeSurfer_5.3_ > > Data/diffusion_ > recons] : set pathlist = ( lh.cst_AS rh.cst_AS > \ > ? lh.ilf_AS rh.ilf_AS \ > ? lh.unc_AS rh.unc_AS \ > ? fmajor_PP fminor_PP \ > ? lh.atr_PP rh.atr_PP \ > ? lh.cab_PP rh.cab_PP \ > ? lh.ccg_PP rh.ccg_PP \ > ? lh.slfp_PP rh.slfp_PP \ > ? lh.slft_PP rh.slft_PP ) > csh::alanf@dali[/autofs/space/dali_003/users/BW_project_DTI/FreeSurfer_5.3_ > > Data/diffusion_ > recons] : set ncpts = (6 6 5 5 5 5 7 5 5 5 5 5 > 4 4 5 5 5 > 5) > csh::alanf@dali[/autofs/space/dali_003/users/BW_project_DTI/FreeSurfer_5.3_ > > Data/diffusion_ > recons] : trac-all -prep -c /autofs/space/d > dali_001/ dali_002/ dali_003/ > csh::alanf@dali[/autofs/space/dali_003/users/BW_project_DTI/FreeSurfer_5.3_ > > Data/diffusion_ > recons] : trac-all-prep-c/autofs/space/dali_003/users/BW_project_DTI/FreeSurfer_5.3_Data/diff > usion > _r > econs/ > > ERROR: run list is longer than subject list > > > > > > 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. > > > > > > > >

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