Freesurfer

freesurfer@nmr.mgh.harvard.edu

16 participants
30084 discussions

voxel value scaling
by Rockers, Elijah D. 25 Nov '15

25 Nov '15

I am interested in finding a way to apply a slope scaling factor to the voxel values in a NIfTI image. I have done this in MATLAB and PMOD so far, but for some reason both methods change the origin or otherwise distort the dimensions of the image and render it impossible for me to process further. Something that simply scales the values without touching the header (or at least as little as possible) would be great. Is anything like this out there? Thanks, Eli Houston Methodist. Leading Medicine. Ranked by U.S.News & World Report as one of America's "Best Hospitals" in 11 specialties. Named to FORTUNE® Magazine's "100 Best Companies to Work For®" list 10 years in a row. Designated as a Magnet hospital for excellence in nursing. Visit us at houstonmethodist.org. Follow us at twitter.com/MethodistHosp and www.facebook.com/HoustonMethodist. ***CONFIDENTIALITY NOTICE*** This e-mail is the property of Houston Methodist Hospital and/or its relevant affiliates and may contain restricted and privileged material for the sole use of the intended recipient(s). Any review, use, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the sender and delete all copies of the message. Thank you.

2 2

Checking optseq efficiency of a custom par file.
by Sam Zorowitz 24 Nov '15

24 Nov '15

Dear Freesurfer list, Using the optseq2 program, is it possible to calculate the efficiency of a custom par file? I have an fMRI task that will be split into three blocks. I want to calculate the overall efficiency of my overall design byconcatenating the best par file from optimizing each individual block. I have already tried doing so by concatenating the three par files (updating the onset times) and inputting this into optseq2 by: >> optseq2 --in new_file.par --nosearch --tr 1.75 --ntp 1080 --psdwin 0 3.5 1.75 --o new_dir If I do this, however, I get a "core dump" error. Does anyone know how I might going about doing this? I've attached the new_par file for convenience. Best, sam

2 1

subjects_dir
by Eric Cunningham 24 Nov '15

24 Nov '15

Greetings Freesurfer experts, The README file in the $SUBJECTS_DIR says that a different directory can be specified by setting the env var SUBJECTS_DIR prior to the 'source $FREESURFER_HOME/FreeSurferEnv.csh' statement. Do the original contents of SUBJECTS_DIR (such as fsaverage) need to be moved into the newly specified SUBJECTS_DIR? Thanks, -Eric

2 3

Edit the number of segments in the segmentation of the corpus callosum
by UQAM 24 Nov '15

24 Nov '15

Hi, This a a "re-posting" of a question I've raised last week ; ) I would like to segment the corpus callosum into *twelve* even lenght segments instead of the five segments that freesurfer includes by default. - First I ran a mri_cc on subject e0070: mri_cc -aseg aseg.auto_noCCseg.mgz -o aseg.12segmentsCC.mgz -d 12 e0070 - Then I edited the ColorLUT.txt file and renamed it CColorLUT.txt (see attachment, segments 251 to 262). - Finally I ran a mri_segstats to compute the statistics on segmented volumes. mri_segstats seg $SUBJECTS_DIR/e0070/mri/aseg.12segmentsCC.mgz --ctab $SUBJECTS_DIR/CColorLUT.txt --nonempty --excludeid 0 sum --e0070_CC12.aseg.stats The e0070_CC12.aseg.stats file still displays only five segments of the corpus callosum. Any tips or clues on how I could do things differently to get 12 segments? Thanks in advance, Geneviève

4 8

Cluster coordinates in QDEC
by henrike.hanssen＠web.de 24 Nov '15

24 Nov '15

1 0

Which is the best volume to use to get intensity statistics?
by Guido Orlando Pascariello 23 Nov '15

23 Nov '15

Hi FS Expert I have just looked for this subject a long the list but I haven't found anything about. I have been working with FreeSurfer and I could get some segmentation from my T1 data. I used 'mri_segstats' to quantify volume of some subcortical region. Also I want to get intensity statistics from these regions, so I used --in parameter. In the 'recon-all' pipeline, you use 'norm.mgz' but.. . I wonder is not better to use nu.mgz in order to get intensity values more related to original data? If is not. Can you explain me what '-canorm' step does? Because I don't get it I'll be grateful if you can help Being all for now, I await a reply Guido PASCARIELLO Facultad de Ingeniería - Universidad Nacional de Entre Ríos Argentina

2 1

Re: [Freesurfer] How to create a 3g4v matrix
by nellie 23 Nov '15

23 Nov '15

Hi Lee, Thank you for your reply. I had read the example tables, but I'm still not sure how to alter them into my study.May be you could help to check the matrix I designed and tell me my mistake? 3 classes ( A / B / C group) and 4 variables (gender, age, education, and Moca test score). group.diff.mtx 1 -1 0 0 0 0 0 0 0 0 0 0 0 0 0 group-x-gender.mtx 0 0 0 1 -1 0 0 0 0 0 0 0 0 0 0 group-x-age.mtx 0 0 0 0 0 0 1 -1 0 0 0 0 0 0 0 group-x-education.mtx 0 0 0 0 0 0 0 0 0 1 -1 0 0 0 0 group-x-moca.mtx 0 0 0 0 0 0 0 0 0 0 0 0 1 -1 0 group-x-gender-x-age-x-education.mtx 0 0 0 1 -1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 -1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 -1 0 0 0 0 group-x-gender-x-age-x-education-x-moca.mtx 0 0 0 1 -1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 -1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 -1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 -1 0 group.diff.mtx also can write as: 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 group-x-age.mtx aslo can write as: 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 Thank you in advence. Wishes, Li > >When replying, please edit your Subject line so it is more specific >than "Re: Contents of Freesurfer digest..." > > >Today's Topics: > > 1. Re: How to create a 3g4v matrix (Lee Tirrell) > > >---------------------------------------------------------------------- > >Message: 1 >Date: Mon, 23 Nov 2015 10:27:42 -0500 (EST) >From: Lee Tirrell <ltirrell(a)nmr.mgh.harvard.edu> >Subject: Re: [Freesurfer] How to create a 3g4v matrix >To: Freesurfer support list <freesurfer(a)nmr.mgh.harvard.edu> >Message-ID: > <alpine.LRH.2.20.1511231020130.5623(a)vermis.nmr.mgh.harvard.edu> >Content-Type: text/plain; charset="iso-8859-7" > >Hi Li, > >You can find some example FSGD tables here, which you can alter to fit your >analyses. > >https://surfer.nmr.mgh.harvard.edu/fswiki/FsgdExamples > >Best, >Lee > >On Sun, 22 Nov 2015, nellie wrote: > >> >> Hi Freesurfer Experts, >> >> I?m a new user of Freesurfer, and I learn how to use this software mainly through Wiki. When I came to the step of using GLM to compare group differences, I was confused on the design of 3g4v matrix. In my study, there were 3 classes ( >> A / B / C group) and 4 concomitant?variables (gender, age, education, and Moca test score). It?s supposed to be 15 regressors in this design, but I don?t know how to use the numbers (like 1, -1, 0, 0.5, -0.5, etc.) to create a correct >> matrix. I wonder if you could provide a 3g4v matrix in detail for me. I?ll be grateful if you can help. I hope I?m not bothering you too much, and I?m looking for your reply. >> >> Best wishes, >> >> Li? >> >> >> >> ? >> >> >> > >------------------------------ > >_______________________________________________ >Freesurfer mailing list >Freesurfer(a)nmr.mgh.harvard.edu >https://mail.nmr.mgh.harvard.edu/mailman/listinfo/freesurfer > >End of Freesurfer Digest, Vol 141, Issue 40 >******************************************* > > >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

Get white and pial surfaces without using aseg.mgz
by Guido Orlando Pascariello 23 Nov '15

23 Nov '15

Hi FS Experts I'm using FreeSurfer to process my T1 data in order to get white and pial surfaces from it. I have a questions about usages of this file 'aseg.mgz'. In the 'recon-all' pipeline, there are some steps in which I can use it or don't use it depend on if I want or don't. I wonder What are the differences in the result in each option? My goal is skip the '-careg' step to save time because I'm not interested in volumetry. I'll be grateful if you can help Being all for now, I await a reply Guido PASCARIELLO Facultad de Ingeniería - Universidad Nacional de Entre Ríos Argentina

2 1

Re: [Freesurfer] fsl_rigid_register fails with wrong orientation
by Caspar M. Schwiedrzik 23 Nov '15

23 Nov '15

Red Hat Enterprise Linux Server release 5.9 (Tikanga) freesurfer-Linux-centos4_x86_64-stable-pub-v5.1.0 Caspar 2015-11-23 14:37 GMT-05:00 <zkaufman(a)nmr.mgh.harvard.edu>: > What system are you running on? Also, what are the contents of your > build-stamp.txt file (in your FREESURFER_HOME directory)? > > -Zeke > > > > Hi Zeke, > > I tried the is new version. Now I am getting: > > > > mri_coreg: /lib64/libuuid.so.1: no version information available > (required > > by mri_coreg) > > mri_coreg: /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.11' not found > > (required by mri_coreg) > > mri_coreg: /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.9' not found > > (required by mri_coreg) > > mri_coreg: /lib64/libc.so.6: version `GLIBC_2.7' not found (required by > > mri_coreg) > > > > Caspar > > > > > > 2015-11-23 14:20 GMT-05:00 <zkaufman(a)nmr.mgh.harvard.edu>: > > > >> There were some recent changes in the build that eliminated the > >> necessity > >> for that library. Casper, can you try using this most recent version and > >> let me know if it works? > >> > >> > >> > ftp://surfer.nmr.mgh.harvard.edu//pub/dist/freesurfer/dev_binaries/centos6_… > >> > >> Thanks, > >> > >> -Zeke > >> > >> > >> > Zeke, is this a new library that we need for v6? > >> > doug > >> > > >> > On 11/20/2015 09:42 AM, Caspar M. Schwiedrzik wrote: > >> >> Hi Doug, > >> >> when I try to execute mri_coreg, I get the following error message: > >> >> > >> >> error while loading shared libraries: libnetcdf.so.6: cannot open > >> >> shared object file: no such file or directory > >> >> > >> >> Caspar > >> >> > >> >> > >> >> 2015-11-19 18:49 GMT-05:00 Douglas Greve <greve(a)nmr.mgh.harvard.edu > >> >> <mailto:greve@nmr.mgh.harvard.edu>>: > >> >> > >> >> > >> >> Can you try mri_coreg instead of fsl? > >> >> > >> ftp://surfer.nmr.mgh.harvard.edu/transfer/outgoing/flat/greve/mri_coreg > >> >> > >> >> > >> >> > >> >> > >> >> On 11/19/15 5:25 PM, Caspar M. Schwiedrzik wrote: > >> >>> Hi! > >> >>> I am trying to align a mean EPI volume and a Bruker magnitude > >> map > >> >>> from a fieldmap measurement using tkregister2, > >> fsl_rigid_register > >> >>> and mri_vol2vol. Unfortunately, it seems that somewhere, most > >> >>> likely during fsl_rigid_register, the image orientation get > >> >>> scrambled, and the output has the wrong orientation. > >> >>> > >> >>> Here is what I get from*tkregister2:* > >> >>> > >> >>> target volume epi.nii > >> >>> movable volume fieldmap0001.nii > >> >>> reg file mag_2_mocovol.register.dat > >> >>> LoadVol 0 > >> >>> ZeroCRAS 0 > >> >>> $Id: tkregister2.c,v 1.121.2.1 2011/03/28 20:25:16 greve Exp $ > >> >>> Diagnostic Level -1 > >> >>> INFO: loading target epi.nii > >> >>> Setting targ orientation to RIA > >> >>> INFO: target does not conform to COR format, so I'm going to > >> >>> reslice to COR. This will not affect the final registration. > >> >>> Ttarg: -------------------- > >> >>> -1.000 0.000 0.000 128.000; > >> >>> 0.000 0.000 1.000 -128.000; > >> >>> 0.000 -1.000 0.000 128.000; > >> >>> 0.000 0.000 0.000 1.000; > >> >>> INFO: loading movable fieldmap0001.nii > >> >>> Setting mov orientation to RIA > >> >>> Tmov: -------------------- > >> >>> -0.547 0.000 0.000 17.500; > >> >>> 0.000 0.000 0.547 -17.500; > >> >>> 0.000 -0.547 0.000 17.500; > >> >>> 0.000 0.000 0.000 1.000; > >> >>> mkheaderreg = 1, float2int = 0 > >> >>> Computing reg from header (and possibly input matrix) > >> >>> ---- Input registration matrix (computed) -------- > >> >>> -1.000 0.000 0.000 -0.587; > >> >>> 0.000 1.000 0.000 -2.150; > >> >>> 0.000 0.000 1.000 -2.188; > >> >>> 0.000 0.000 0.000 1.000; > >> >>> --------------------------------------- > >> >>> ---- Input registration matrix -------- > >> >>> -1.000 0.000 0.000 -0.587; > >> >>> 0.000 1.000 0.000 -2.150; > >> >>> 0.000 0.000 1.000 -2.188; > >> >>> 0.000 0.000 0.000 1.000; > >> >>> Determinant -1 > >> >>> subject = rat > >> >>> RegMat --------------------------- > >> >>> 1.000 0.000 0.000 -0.587; > >> >>> 0.000 1.000 0.000 -2.150; > >> >>> 0.000 0.000 1.000 -2.188; > >> >>> 0.000 0.000 0.000 1.000; > >> >>> FSLOUTPUTTYPE NIFTI_GZ > >> >>> tkreg2FSL: mov det = 0.163555, ref det = 0.154688 > >> >>> INFO: FSL2FreeSurfer: Mov volume is NIFTI with positive det, > >> >>> applying LR flip to registration matrix. > >> >>> INFO: FSL2FreeSurfer: Ref volume is NIFTI with positive det, > >> >>> applying LR flip to registration matrix. > >> >>> > >> >>> here is what I get from fsl_rigid_register: > >> >>> $Id: fsl_rigid_register,v 1.31 2011/03/02 20:16:39 nicks Exp $ > >> >>> Thu Nov 19 17:13:48 EST 2015 > >> >>> fieldmap0001_reg.nii > >> >>> Reference is nifti, not converting > >> >>> Input is nifti, not converting > >> >>> Output is nifti, not converting > >> >>> -------------------------------------- > >> >>> /Freiwald/cschwiedrz/rodent/test/Rat_673b_Baseline/Phasemap > >> >>> calling eval flirt.fsl -in ./fieldmap0001.hdr -out > >> >>> ./fieldmap0001_reg.hdr -bins 256 -cost corratio -searchrx -10 10 > >> >>> -searchry -10 10 -searchrz -10 10 -interp trilinear -dof 6 -ref > >> >>> ./epi.hdr -init initxfm.fslmat -omat ./fieldmap0001_reg.fslmat > >> >>> /Freiwald/cschwiedrz/rodent/test/Rat_673b_Baseline/Phasemap > >> >>> mri_copy_params --pulse fieldmap0001_reg.nii fieldmap0001.nii > >> >>> fieldmap0001_reg.nii > >> >>> only copying pulse parameters > >> >>> WARNING: volume sizes are different > >> >>> in_vol : 80, 80, 22 > >> >>> temp_vol : 64, 64, 64 > >> >>> WARNING: voxel sizes are different > >> >>> in_vol : 0.375, 0.375, 1.1 > >> >>> temp_vol : 0.546875, 0.546875, 0.546875 > >> >>> -------------------------------------- > >> >>> /Freiwald/cschwiedrz/rodent/test/Rat_673b_Baseline/Phasemap > >> >>> tkregister2_cmdl --targ epi.nii --mov fieldmap0001.nii --reg > >> >>> ./fsl_rigid_register.28592/reg.dat --fslreg > >> >>> fieldmap0001_reg.nii.fslmat --noedit > >> >>> tkregister_tcl > >> >>> > >> > /Freiwald/lab_files/opt/freesurfer-Linux-centos4_x86_64-stable-pub-v5.1.0-full/tktools/tkregister2.tcl > >> >>> ---- FSL registration matrix -------- > >> >>> 0.987 -0.164 0.002 0.247; > >> >>> 0.157 0.943 -0.295 -5.691; > >> >>> 0.046 0.291 0.956 7.475; > >> >>> 0.000 0.000 0.000 1.000; > >> >>> --------------------------------------- > >> >>> target volume epi.nii > >> >>> movable volume fieldmap0001.nii > >> >>> reg file ./fsl_rigid_register.28592/reg.dat > >> >>> LoadVol 0 > >> >>> ZeroCRAS 0 > >> >>> $Id: tkregister2.c,v 1.121.2.1 2011/03/28 20:25:16 greve Exp $ > >> >>> Diagnostic Level -1 > >> >>> INFO: loading target epi.nii > >> >>> INFO: target does not conform to COR format, so I'm going to > >> >>> reslice to COR. This will not affect the final registration. > >> >>> Ttarg: -------------------- > >> >>> -1.000 0.000 0.000 128.000; > >> >>> 0.000 0.000 1.000 -128.000; > >> >>> 0.000 -1.000 0.000 128.000; > >> >>> 0.000 0.000 0.000 1.000; > >> >>> INFO: loading movable fieldmap0001.nii > >> >>> Tmov: -------------------- > >> >>> -0.547 0.000 0.000 17.500; > >> >>> 0.000 0.000 0.547 -17.500; > >> >>> 0.000 -0.547 0.000 17.500; > >> >>> 0.000 0.000 0.000 1.000; > >> >>> mkheaderreg = 0, float2int = 0 > >> >>> FSLOUTPUTTYPE NIFTI > >> >>> fsl2TkReg: mov det = 0.163555, ref det = 0.154688 > >> >>> INFO: FSL2FreeSurfer: Mov volume is NIFTI with positive det, > >> >>> applying LR flip to registration matrix. > >> >>> INFO: FSL2FreeSurfer: Ref volume is NIFTI with positive det, > >> >>> applying LR flip to registration matrix. > >> >>> ---- Input registration matrix (computed) -------- > >> >>> -0.987 0.046 -0.157 0.692; > >> >>> -0.002 0.956 0.295 -19.148; > >> >>> -0.164 -0.291 0.943 -0.998; > >> >>> 0.000 0.000 0.000 1.000; > >> >>> --------------------------------------- > >> >>> ---- Input registration matrix -------- > >> >>> -0.987 0.046 -0.157 0.692; > >> >>> -0.002 0.956 0.295 -19.148; > >> >>> -0.164 -0.291 0.943 -0.998; > >> >>> 0.000 0.000 0.000 1.000; > >> >>> Determinant -1 > >> >>> subject = subject-unknown > >> >>> RegMat --------------------------- > >> >>> 0.987 0.046 -0.157 0.692; > >> >>> 0.002 0.956 0.295 -19.148; > >> >>> 0.164 -0.291 0.943 -0.998; > >> >>> 0.000 0.000 0.000 1.000; > >> >>> Cleaning up > >> >>> > >> >>> Started at Thu Nov 19 17:13:48 EST 2015 > >> >>> Ended at Thu Nov 19 17:13:50 EST 2015 > >> >>> > >> >>> fsl_rigid_register Done > >> >>> > >> >>> if I check the results here using tkmedit -f epi.nii -aux > >> >>> fieldmap0001_reg.nii > >> >>> the orientation of fieldmap0001_reg.nii is already wrong. > >> >>> > >> >>> here is what I get from mri_vol2vol: > >> >>> movvol fieldmap_rads.nii.gz > >> >>> targvol epi.nii > >> >>> outvol fieldmap_rads_reg.nii.gz > >> >>> regfile mag_2_mocovol.register.dat > >> >>> invert 0 > >> >>> tal 0 > >> >>> talres 2 > >> >>> regheader 0 > >> >>> noresample 0 > >> >>> interp trilinear (1) > >> >>> precision float (3) > >> >>> Gdiag_no -1 > >> >>> Synth 0 > >> >>> SynthSeed 1448209916 > >> >>> > >> >>> Final tkRAS-to-tkRAS Matrix is: > >> >>> 0.987 0.046 -0.157 0.692; > >> >>> 0.002 0.956 0.295 -19.148; > >> >>> 0.164 -0.291 0.943 -0.998; > >> >>> 0.000 0.000 0.000 1.000; > >> >>> > >> >>> > >> >>> Vox2Vox Matrix is: > >> >>> 0.676 -0.108 -0.093 8.999; > >> >>> 0.112 0.646 0.586 -2.959; > >> >>> -0.002 -0.202 1.922 -16.003; > >> >>> 0.000 0.000 0.000 1.000; > >> >>> > >> >>> Resampling > >> >>> Output registration matrix is identity > >> >>> INFO: wAriting registration matrix to > >> fieldmap_rads_reg.nii.gz.reg > >> >>> > >> >>> checking the result with > >> >>> tkregister2 --mov fieldmap_rads_reg.nii.gz --targ epi.nii --reg > >> >>> fieldmap_rads_reg.nii.gz.reg > >> >>> also yields the wrong orientation, obviously. > >> >>> > >> >>> In this case, I am changing the fieldmap to RIA orientation, > >> >>> although it is actually IPL; doing the same steps with the > >> >>> original IPL orientation gives the same faulty results. > >> >>> > >> >>> this is the code: > >> >>> > >> >>> tkregister2 --s rat \ > >> >>> --targ $epi \ > >> >>> --mov fieldmap0001.nii \ > >> >>> --reg mag_2_mocovol.register.dat \ > >> >>> --fslregout initxfm.fslmat \ > >> >>> --noedit \ > >> >>> --regheader \ > >> >>> --mov-orientation $fieldmap_orient \ > >> >>> --targ-orientation $epi_orient > >> >>> > >> >>> flirt_opts="-maxangle 10 -dof 6 -interp trilinear -bins 256 > >> -cost > >> >>> corratio" > >> >>> fsl_rigid_register -r $epi \ > >> >>> -i fieldmap0001.nii \ > >> >>> -o fieldmap0001_reg.nii \ > >> >>> -regmat mag_2_mocovol.register.dat \ > >> >>> -initxfm initxfm.fslmat \ > >> >>> ${flirt_opts} > >> >>> > >> >>> # apply registration to phase > >> >>> mri_vol2vol --mov fieldmap_rads.nii.gz --targ $epi --o > >> >>> fieldmap_rads_reg.nii.gz --reg mag_2_mocovol.register.dat > >> --trilin > >> >>> > >> >>> Any advice would be appreciated. > >> >>> Thanks! Caspar > >> >>> > >> >>> > >> >>> > >> >>> _______________________________________________ > >> >>> Freesurfer mailing list > >> >>> Freesurfer(a)nmr.mgh.harvard.edu > >> >>> <mailto:Freesurfer@nmr.mgh.harvard.edu> > >> >>> https://mail.nmr.mgh.harvard.edu/mailman/listinfo/freesurfer > >> >> > >> >> > >> >> _______________________________________________ > >> >> Freesurfer mailing list > >> >> Freesurfer(a)nmr.mgh.harvard.edu > >> >> <mailto:Freesurfer@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. > >> >> > >> >> > >> >> > >> >> > >> >> _______________________________________________ > >> >> Freesurfer mailing list > >> >> Freesurfer(a)nmr.mgh.harvard.edu > >> >> https://mail.nmr.mgh.harvard.edu/mailman/listinfo/freesurfer > >> > > >> > -- > >> > 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: https://gate.nmr.mgh.harvard.edu/filedrop2 > >> > www.nmr.mgh.harvard.edu/facility/filedrop/index.html > >> > Outgoing: > >> ftp://surfer.nmr.mgh.harvard.edu/transfer/outgoing/flat/greve/ > >> > > >> > > >> > > >> > >> > > > >

2 2

fsl_rigid_register fails with wrong orientation
by Caspar M. Schwiedrzik 23 Nov '15

23 Nov '15

Hi! I am trying to align a mean EPI volume and a Bruker magnitude map from a fieldmap measurement using tkregister2, fsl_rigid_register and mri_vol2vol. Unfortunately, it seems that somewhere, most likely during fsl_rigid_register, the image orientation get scrambled, and the output has the wrong orientation. Here is what I get from* tkregister2:* target volume epi.nii movable volume fieldmap0001.nii reg file mag_2_mocovol.register.dat LoadVol 0 ZeroCRAS 0 $Id: tkregister2.c,v 1.121.2.1 2011/03/28 20:25:16 greve Exp $ Diagnostic Level -1 INFO: loading target epi.nii Setting targ orientation to RIA INFO: target does not conform to COR format, so I'm going to reslice to COR. This will not affect the final registration. Ttarg: -------------------- -1.000 0.000 0.000 128.000; 0.000 0.000 1.000 -128.000; 0.000 -1.000 0.000 128.000; 0.000 0.000 0.000 1.000; INFO: loading movable fieldmap0001.nii Setting mov orientation to RIA Tmov: -------------------- -0.547 0.000 0.000 17.500; 0.000 0.000 0.547 -17.500; 0.000 -0.547 0.000 17.500; 0.000 0.000 0.000 1.000; mkheaderreg = 1, float2int = 0 Computing reg from header (and possibly input matrix) ---- Input registration matrix (computed) -------- -1.000 0.000 0.000 -0.587; 0.000 1.000 0.000 -2.150; 0.000 0.000 1.000 -2.188; 0.000 0.000 0.000 1.000; --------------------------------------- ---- Input registration matrix -------- -1.000 0.000 0.000 -0.587; 0.000 1.000 0.000 -2.150; 0.000 0.000 1.000 -2.188; 0.000 0.000 0.000 1.000; Determinant -1 subject = rat RegMat --------------------------- 1.000 0.000 0.000 -0.587; 0.000 1.000 0.000 -2.150; 0.000 0.000 1.000 -2.188; 0.000 0.000 0.000 1.000; FSLOUTPUTTYPE NIFTI_GZ tkreg2FSL: mov det = 0.163555, ref det = 0.154688 INFO: FSL2FreeSurfer: Mov volume is NIFTI with positive det, applying LR flip to registration matrix. INFO: FSL2FreeSurfer: Ref volume is NIFTI with positive det, applying LR flip to registration matrix. here is what I get from fsl_rigid_register: $Id: fsl_rigid_register,v 1.31 2011/03/02 20:16:39 nicks Exp $ Thu Nov 19 17:13:48 EST 2015 fieldmap0001_reg.nii Reference is nifti, not converting Input is nifti, not converting Output is nifti, not converting -------------------------------------- /Freiwald/cschwiedrz/rodent/test/Rat_673b_Baseline/Phasemap calling eval flirt.fsl -in ./fieldmap0001.hdr -out ./fieldmap0001_reg.hdr -bins 256 -cost corratio -searchrx -10 10 -searchry -10 10 -searchrz -10 10 -interp trilinear -dof 6 -ref ./epi.hdr -init initxfm.fslmat -omat ./fieldmap0001_reg.fslmat /Freiwald/cschwiedrz/rodent/test/Rat_673b_Baseline/Phasemap mri_copy_params --pulse fieldmap0001_reg.nii fieldmap0001.nii fieldmap0001_reg.nii only copying pulse parameters WARNING: volume sizes are different in_vol : 80, 80, 22 temp_vol : 64, 64, 64 WARNING: voxel sizes are different in_vol : 0.375, 0.375, 1.1 temp_vol : 0.546875, 0.546875, 0.546875 -------------------------------------- /Freiwald/cschwiedrz/rodent/test/Rat_673b_Baseline/Phasemap tkregister2_cmdl --targ epi.nii --mov fieldmap0001.nii --reg ./fsl_rigid_register.28592/reg.dat --fslreg fieldmap0001_reg.nii.fslmat --noedit tkregister_tcl /Freiwald/lab_files/opt/freesurfer-Linux-centos4_x86_64-stable-pub-v5.1.0-full/tktools/tkregister2.tcl ---- FSL registration matrix -------- 0.987 -0.164 0.002 0.247; 0.157 0.943 -0.295 -5.691; 0.046 0.291 0.956 7.475; 0.000 0.000 0.000 1.000; --------------------------------------- target volume epi.nii movable volume fieldmap0001.nii reg file ./fsl_rigid_register.28592/reg.dat LoadVol 0 ZeroCRAS 0 $Id: tkregister2.c,v 1.121.2.1 2011/03/28 20:25:16 greve Exp $ Diagnostic Level -1 INFO: loading target epi.nii INFO: target does not conform to COR format, so I'm going to reslice to COR. This will not affect the final registration. Ttarg: -------------------- -1.000 0.000 0.000 128.000; 0.000 0.000 1.000 -128.000; 0.000 -1.000 0.000 128.000; 0.000 0.000 0.000 1.000; INFO: loading movable fieldmap0001.nii Tmov: -------------------- -0.547 0.000 0.000 17.500; 0.000 0.000 0.547 -17.500; 0.000 -0.547 0.000 17.500; 0.000 0.000 0.000 1.000; mkheaderreg = 0, float2int = 0 FSLOUTPUTTYPE NIFTI fsl2TkReg: mov det = 0.163555, ref det = 0.154688 INFO: FSL2FreeSurfer: Mov volume is NIFTI with positive det, applying LR flip to registration matrix. INFO: FSL2FreeSurfer: Ref volume is NIFTI with positive det, applying LR flip to registration matrix. ---- Input registration matrix (computed) -------- -0.987 0.046 -0.157 0.692; -0.002 0.956 0.295 -19.148; -0.164 -0.291 0.943 -0.998; 0.000 0.000 0.000 1.000; --------------------------------------- ---- Input registration matrix -------- -0.987 0.046 -0.157 0.692; -0.002 0.956 0.295 -19.148; -0.164 -0.291 0.943 -0.998; 0.000 0.000 0.000 1.000; Determinant -1 subject = subject-unknown RegMat --------------------------- 0.987 0.046 -0.157 0.692; 0.002 0.956 0.295 -19.148; 0.164 -0.291 0.943 -0.998; 0.000 0.000 0.000 1.000; Cleaning up Started at Thu Nov 19 17:13:48 EST 2015 Ended at Thu Nov 19 17:13:50 EST 2015 fsl_rigid_register Done if I check the results here using tkmedit -f epi.nii -aux fieldmap0001_reg.nii the orientation of fieldmap0001_reg.nii is already wrong. here is what I get from mri_vol2vol: movvol fieldmap_rads.nii.gz targvol epi.nii outvol fieldmap_rads_reg.nii.gz regfile mag_2_mocovol.register.dat invert 0 tal 0 talres 2 regheader 0 noresample 0 interp trilinear (1) precision float (3) Gdiag_no -1 Synth 0 SynthSeed 1448209916 Final tkRAS-to-tkRAS Matrix is: 0.987 0.046 -0.157 0.692; 0.002 0.956 0.295 -19.148; 0.164 -0.291 0.943 -0.998; 0.000 0.000 0.000 1.000; Vox2Vox Matrix is: 0.676 -0.108 -0.093 8.999; 0.112 0.646 0.586 -2.959; -0.002 -0.202 1.922 -16.003; 0.000 0.000 0.000 1.000; Resampling Output registration matrix is identity INFO: wAriting registration matrix to fieldmap_rads_reg.nii.gz.reg checking the result with tkregister2 --mov fieldmap_rads_reg.nii.gz --targ epi.nii --reg fieldmap_rads_reg.nii.gz.reg also yields the wrong orientation, obviously. In this case, I am changing the fieldmap to RIA orientation, although it is actually IPL; doing the same steps with the original IPL orientation gives the same faulty results. this is the code: tkregister2 --s rat \ --targ $epi \ --mov fieldmap0001.nii \ --reg mag_2_mocovol.register.dat \ --fslregout initxfm.fslmat \ --noedit \ --regheader \ --mov-orientation $fieldmap_orient \ --targ-orientation $epi_orient flirt_opts="-maxangle 10 -dof 6 -interp trilinear -bins 256 -cost corratio" fsl_rigid_register -r $epi \ -i fieldmap0001.nii \ -o fieldmap0001_reg.nii \ -regmat mag_2_mocovol.register.dat \ -initxfm initxfm.fslmat \ ${flirt_opts} # apply registration to phase mri_vol2vol --mov fieldmap_rads.nii.gz --targ $epi --o fieldmap_rads_reg.nii.gz --reg mag_2_mocovol.register.dat --trilin Any advice would be appreciated. Thanks! Caspar

4 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