Freesurfer August 2013

freesurfer@nmr.mgh.harvard.edu

145 participants
268 discussions

Can I include this pre- vs. post- patient dataset?
by Qi Wu 01 Aug '13

01 Aug '13

Hi Freesurfer experts, I have a difficult decision to make and I don't know which direction is better. Your opinions are needed. We are planning a paper on the treatment effects of a drug on the cortical plasticity in a group of patients ( the pre- vs. post- design). It has been a huge challenge to recruit patients for this subject. So far, after 3 years of active recruitment, we have only 13 complete set of pre- vs. post- data. But , we have another set of data which was collected at the earliest stage of the project with slightly different parameters. The main difference is the in-plane resolution; those 13 patients have a 1mm*1mm*1mm isovoxel resolution and that particular patients has a 1mm*0.86mm*0.86mm resolution. To include the subject increases the power of the pre- vs. post analysis, as we are working in the range of relatively low S/N (only 13 pairs). We also know that we are open to attack if we include the subject with different scan parameters. Anyone knows how big the impact would be. Is there anyway to estimate the impact? Is it easy to get away with the potential critique about this issue? Is it a must-not case? Many thanks Keith Postdoc fellow Toronto Western Hospital Canada

2 2

TR,TE,TI,FA variability w/ mri_ca_train
by Mark Plantz 01 Aug '13

01 Aug '13

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

2 1

Recon-all errors
by Stéphane Poulin 01 Aug '13

01 Aug '13

Dear Freesurfer experts, Regarding recon-all troubleshooting, my understanding is that you can edit wm and complete the pipeline with recon-all –autorecon2-wm. Similarly you can complete the pipeline with recon-all –autorecon2-pial if there is a problem with the pial surface. If there are both white matter and pial surface edits, is there an “efficient” way to correct for both and complete the pipeline. Thanks, Stephane

2 1

Cerebellum Subcortical edits
by Michael Kranz 01 Aug '13

01 Aug '13

Hi guys, I was just wondering approximately how often the aseg volume will need manual edits. I know the tutorial says very rarely but I noticed that most of my subjects have non-brain matter (I think) incorrectly labelled as cerebellum. Attached is a pic of what I mean.[image: Inline image 1] Thanks, Mike

3 4

type of errors
by clelia pellicano 01 Aug '13

01 Aug '13

Dear freesurfers, I have run recon-all -all on some subjects and I got these errors I never had before. mri_ca_register -invert-and-save transforms/talairach.m3z GCAMread(transforms/talairach.m3z): invalid version # 7573008809984.000 Loading, Inverting, Saving, Exiting ... Reading transforms/talairach.m3z ERROR: mri_ca_register with non-zero status 0 Linux wmen-ps2208 2.6.32-358.14.1.el6.x86_64 #1 SMP Mon Jun 17 15:54:20 EDT 2013 x86_64 x86_64 x86_64 GNU/Linux recon-all -s CHWI exited with ERRORS at Thu Aug 1 10:50:29 BST 2013 For another subject: ERROR: talairach_afd: Talairach Transform: transforms/talairach.xfm ***FAILED*** (p=0.0747, pval=0.0034 < threshold=0.0050) Manual Talairach alignment may be necessary, or include the -notal-check flag to skip this test, making sure the -notal-check flag follows -all or -autorecon1 in the command string. See http://surfer.nmr.mgh.harvard.edu/fswiki/FsTutorial/Talairach Linux wmen-ps2208 2.6.32-358.14.1.el6.x86_64 #1 SMP Mon Jun 17 15:54:20 EDT 2013 x86_64 x86_64 x86_64 GNU/Linux recon-all -s ALTH exited with ERRORS at Wed Jul 31 15:34:36 BST 2013 And for another one, I got just this: mri_ca_register -invert-and-save transforms/talairach.m3z Loading, Inverting, Saving, Exiting ... Reading transforms/talairach.m3z Inverting GCAM Saving inverse Could you help me? Thank you so much Clelia

1 0

unpacksdcmdir error for resting state fMRI
by Eli Fredman 31 Jul '13

31 Jul '13

Hi all, I am following the FsFast tutorial ( https://surfer.nmr.mgh.harvard.edu/fswiki/FsFastFunctionalConnectivityWalkt…) for resting state data and I am stuck at the unpacksdcmdir step. When I try and run the command I get an error that says "ERROR: Run ## does not exist in session." I've tried several different combinations of numbers that I thought might be the run ## but I haven't had any success. All the data I am using are in .IMA format, not .dcm (ex. 000001.IMA 000002.IMA 000003.IMA...000140.IMA), so I am unfamiliar with how to find the scan acquisition number. Thanks for the help! P.S. Are there any good video tutorial's out there for resting state data? I have never done any fMRI analysis until now. -- Eli Fredman, BA Research Assistant Psychiatry Neuroimaging Laboratory Harvard Medical School, Brigham and Women's Hospital 1249 Boylston St, 3rd Floor Boston, MA 02215 Office: (617) 525-6118 Cell: (314) 952-8098 Fax: (617) 525-6150

2 1

defect of cerebellar segmentation in the inferior part
by charles laidi 31 Jul '13

31 Jul '13

Dear Freesurfers, **** ** ** I am experiencing recurrent issue while performing cerebellar segmentation on T1 images.**** ** ** These are the characteristics of the acquisition:**** **§ **T1: field of view (FOV) = 230 mm**** **§ **repetition time (TR) = 1140 msec**** **§ **echo time (TE) = 4.38 msec**** **§ **matrix size 256 × 256** **§ ***interpolated to 512 × 512* **§ ***yielding an in-plane voxel size of 0.45 mm × 0.45 mm***** **§ **slice thickness of 0.9 mm**** ** ** After recon-all (ended without errors) I always end up with the same error in segmentation (see attached file) : there is the same defect of segmentation in the inferior part of cerebellum. **** ** ** Are you aware of any way to correct this defect ? (I think this might be related to the low resolution of my images)**** ** ** Thank you for your time. **** Best regards**** Charles**** **

2 1

Fwd: infant atlas segmentation
by Mark Plantz 31 Jul '13

31 Jul '13

---------- 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 medical group<http://www.med.unc.edu/** >> bric/ideagroup/free-softwares/**unc-infant-0-1-2-atla<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<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<greve(a)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<greve(a)nmr.mgh.harvard.edu> >> > >> >> >> <mailto:greve@nmr.mgh.harvard.**edu<greve(a)nmr.mgh.harvard.edu> >> >> >> <mailto:greve@nmr.mgh.harvard.**edu<greve(a)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<greve(a)nmr.mgh.harvard.edu> >> > >> >> >> <mailto:greve@nmr.mgh.harvard.**edu<greve(a)nmr.mgh.harvard.edu> >> >> >> <mailto:greve@nmr.mgh.harvard.**edu<greve(a)nmr.mgh.harvard.edu> >> >> >> >> >> <mailto:greve@nmr.mgh.harvard.**edu<greve(a)nmr.mgh.harvard.edu> >> >> >> <mailto:greve@nmr.mgh.harvard.**edu<greve(a)nmr.mgh.harvard.edu> >> > >> >> >> <mailto:greve@nmr.mgh.harvard.**edu<greve(a)nmr.mgh.harvard.edu> >> >> >> <mailto:greve@nmr.mgh.harvard.**edu<greve(a)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<markplantz2016(a)u.northwestern.edu> >> >> >> <mailto:markplantz2016@u.**northwestern.edu<markplantz2016(a)u.northwestern.edu> >> > >> >> >> <mailto:markplantz2016@u.**northwestern.edu<markplantz2016(a)u.northwestern.edu> >> >> >> <mailto:markplantz2016@u.**northwestern.edu<markplantz2016(a)u.northwestern.edu> >> >> >> >> >> >> <mailto:markplantz2016@u.**northwestern.edu<markplantz2016(a)u.northwestern.edu> >> >> >> <mailto:markplantz2016@u.**northwestern.edu<markplantz2016(a)u.northwestern.edu> >> > >> >> >> <mailto:markplantz2016@u.**northwestern.edu<markplantz2016(a)u.northwestern.edu> >> >> >> <mailto:markplantz2016@u.**northwestern.edu<markplantz2016(a)u.northwestern.edu> >> >>> >> >> >> >> <mailto:markplantz2016@u.**northwestern.edu<markplantz2016(a)u.northwestern.edu> >> >> >> <mailto:markplantz2016@u.**northwestern.edu<markplantz2016(a)u.northwestern.edu> >> > >> >> >> <mailto:markplantz2016@u.**northwestern.edu<markplantz2016(a)u.northwestern.edu> >> >> >> <mailto:markplantz2016@u.**northwestern.edu<markplantz2016(a)u.northwestern.edu> >> >> >> >> >> >> >> <mailto:markplantz2016@u.**northwestern.edu<markplantz2016(a)u.northwestern.edu> >> >> >> <mailto:markplantz2016@u.**northwestern.edu<markplantz2016(a)u.northwestern.edu> >> > >> >> >> <mailto:markplantz2016@u.**northwestern.edu<markplantz2016(a)u.northwestern.edu> >> >> >> <mailto:markplantz2016@u.**northwestern.edu<markplantz2016(a)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<markplantz2016(a)u.northwestern.edu> >> >> >> <mailto:markplantz2016@u.**northwestern.edu<markplantz2016(a)u.northwestern.edu> >> > >> >> >> <mailto:markplantz2016@u.**northwestern.edu<markplantz2016(a)u.northwestern.edu> >> >> >> <mailto:markplantz2016@u.**northwestern.edu<markplantz2016(a)u.northwestern.edu> >> >> >> >> >> >> <mailto:markplantz2016@u.**northwestern.edu<markplantz2016(a)u.northwestern.edu> >> >> >> <mailto:markplantz2016@u.**northwestern.edu<markplantz2016(a)u.northwestern.edu> >> > >> >> >> <mailto:markplantz2016@u.**northwestern.edu<markplantz2016(a)u.northwestern.edu> >> >> >> <mailto:markplantz2016@u.**northwestern.edu<markplantz2016(a)u.northwestern.edu> >> >>> >> >> >> >> <mailto:markplantz2016@u.**northwestern.edu<markplantz2016(a)u.northwestern.edu> >> >> >> <mailto:markplantz2016@u.**northwestern.edu<markplantz2016(a)u.northwestern.edu> >> > >> >> >> <mailto:markplantz2016@u.**northwestern.edu<markplantz2016(a)u.northwestern.edu> >> >> >> <mailto:markplantz2016@u.**northwestern.edu<markplantz2016(a)u.northwestern.edu> >> >> >> >> >> >> >> <mailto:markplantz2016@u.**northwestern.edu<markplantz2016(a)u.northwestern.edu> >> >> >> <mailto:markplantz2016@u.**northwestern.edu<markplantz2016(a)u.northwestern.edu> >> > >> >> >> <mailto:markplantz2016@u.**northwestern.edu<markplantz2016(a)u.northwestern.edu> >> >> >> <mailto:markplantz2016@u.**northwestern.edu<markplantz2016(a)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<markplantz2016(a)u.northwestern.edu> >> >> >> <mailto:markplantz2016@u.**northwestern.edu<markplantz2016(a)u.northwestern.edu> >> > >> >> >> <mailto:markplantz2016@u.**northwestern.edu<markplantz2016(a)u.northwestern.edu> >> >> >> <mailto:markplantz2016@u.**northwestern.edu<markplantz2016(a)u.northwestern.edu> >> >> >> >> >> >> <mailto:markplantz2016@u.**northwestern.edu<markplantz2016(a)u.northwestern.edu> >> >> >> <mailto:markplantz2016@u.**northwestern.edu<markplantz2016(a)u.northwestern.edu> >> > >> >> >> <mailto:markplantz2016@u.**northwestern.edu<markplantz2016(a)u.northwestern.edu> >> >> >> <mailto:markplantz2016@u.**northwestern.edu<markplantz2016(a)u.northwestern.edu> >> >>> >> >> >> >> <mailto:markplantz2016@u.**northwestern.edu<markplantz2016(a)u.northwestern.edu> >> >> >> <mailto:markplantz2016@u.**northwestern.edu<markplantz2016(a)u.northwestern.edu> >> > >> >> >> <mailto:markplantz2016@u.**northwestern.edu<markplantz2016(a)u.northwestern.edu> >> >> >> <mailto:markplantz2016@u.**northwestern.edu<markplantz2016(a)u.northwestern.edu> >> >> >> >> >> >> >> <mailto:markplantz2016@u.**northwestern.edu<markplantz2016(a)u.northwestern.edu> >> >> >> <mailto:markplantz2016@u.**northwestern.edu<markplantz2016(a)u.northwestern.edu> >> > >> >> >> <mailto:markplantz2016@u.**northwestern.edu<markplantz2016(a)u.northwestern.edu> >> >> >> <mailto:markplantz2016@u.**northwestern.edu<markplantz2016(a)u.northwestern.edu> >> >>>>> >> wrote: >> >> >> >> Thanks for >> the reply Doug. I >> >> recently ran >> the >> >> >> bbregister >> >> >> command and >> attempted to view the >> >> results >> >> >> using >> >> >> tkregister2. >> I received the >> >> following >> error: >> >> >> >> >> dhcp-165-124-23-232 >> >> >> <tel:165-124-23-232> >> <tel:165-124-23-232 >> <tel:165-124-23-232>> >> >> >> <tel:165-124-23-232 >> <tel:165-124-23-232> >> >> >> <tel:165-124-23-232 >> <tel:165-124-23-232>>> >> >> >> <tel:165-124-23-232 >> <tel:165-124-23-232> >> >> >> <tel:165-124-23-232 >> <tel:165-124-23-232>> >> >> >> <tel:165-124-23-232 >> <tel:165-124-23-232> >> >> >> <tel:165-124-23-232 >> <tel:165-124-23-232>>>>:Desktop >> >> >> >> >> >> IngvalsonLab$ tkregister2 >> --mov >> >> >> >> /Volumes/Wong_Lab/**CochlearImplant/UNC_NiFTI/** >> infant-1yr-mgz/mri/avgseg.mgz >> >> >> --reg >> >> >> /Users/IngvalsonLab/Desktop/**register.dat >> --surf >> >> >> >> >> tkregister_tcl >> >> >> /Applications/freesurfer/**tktools/tkregister2.tcl >> >> >> INFO: no >> target volume specified, >> >> assuming >> >> >> FreeSurfer orig >> >> >> volume. >> >> >> target >> volume orig >> >> >> movable >> volume >> >> >> >> /Volumes/Wong_Lab/**CochlearImplant/UNC_NiFTI/** >> infant-1yr-mgz/mri/avgseg.mgz >> >> >> reg file >> >> >> /Users/IngvalsonLab/Desktop/**register.dat >> >> >> LoadVol >> 1 >> >> >> ZeroCRAS >> 0 >> >> >> $Id: >> tkregister2.c,v 1.121.2.1 >> >> 2011/03/28 >> >> >> 20:25:16 >> >> >> greve Exp $ >> >> >> Diagnostic >> Level -1 >> >> >> >> regio_read_register(): >> Undefined >> >> error: 0 >> >> >> Error >> reading subject from >> >> >> /Users/IngvalsonLab/Desktop/**register.dat >> >> >> ERROR: >> reading >> >> >> >> /Users/IngvalsonLab/Desktop/**register.dat >> >> >> >> dhcp-165-124-23-232 >> >> >> <tel:165-124-23-232> >> <tel:165-124-23-232 >> <tel:165-124-23-232>> >> >> >> <tel:165-124-23-232 >> <tel:165-124-23-232> >> >> >> <tel:165-124-23-232 >> <tel:165-124-23-232>>> >> >> >> <tel:165-124-23-232 >> <tel:165-124-23-232> >> >> >> <tel:165-124-23-232 >> <tel:165-124-23-232>> >> >> >> <tel:165-124-23-232 >> <tel:165-124-23-232> >> >> >> <tel:165-124-23-232 >> <tel:165-124-23-232>>>>:Desktop >> >> >> >> >> >> IngvalsonLab$ >> >> >> >> I do not >> believe it is a >> >> permissions >> issue? >> >> >> >> Could it >> simply be that the >> >> register was >> >> bad? >> Is >> >> >> there an >> >> >> easy way to >> open up the >> >> >> register.dat.mincost file >> >> >> to check >> >> >> the >> registration? >> >> >> >> Thanks >> again, >> >> >> >> MP >> >> >> >> >> On Tue, Jul >> 23, 2013 at 9:32 PM, >> > >

3 5

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 August 2013