Dear all,
I'm encountering following error when running morph_subject <subject>. What is wrong?
............. registration took 0.67 hours writing registered surface to ../surf/lh.rh.sphere.reg... /var/lab-data/genetic/id106 /var/lab-data/genetic/id106/scripts /var/lab-data/genetic/id106/scripts ------------------------------------- /var/lab-data/genetic/id106/scripts mris2rgb -o id106.reg -both -c /var/lab-data/genetic/id106/surf/lh.sulc -canon /var/lab-data/genetic/id106/surf/lh.sphere.reg /var/lab-data/genetic/id106/surf/lh.sphere.reg /var/lab-data/genetic/id106/rgb ------------------------------------- using id106.reg as output stem reading canonical coordinates from /var/lab-data/genetic/id106/surf/lh.sphere.reg. Segmentation fault mris2rgb exited with errors [brain@amygdala genetic]$
Also, when typing check_subject <subject> I get the following warnings: _______ [brain@amygdala genetic]check_subject id106 CHECKING SUBJECT id106 WARN: time for rh.orig is older than rh.qsphere WARN: file rh.inflated is not equal in size to rh.smoothwm WARN: file rh.white is not equal in size to rh.smoothwm WARN: file rh.sphere is not equal in size to rh.smoothwm WARN: file rh.pial is not equal in size to rh.smoothwm WARN: file rh.sphere.reg is not equal in size to rh.smoothwm WARN: time for lh.orig is older than lh.qsphere WARN: file lh.inflated is not equal in size to lh.smoothwm WARN: file lh.white is not equal in size to lh.smoothwm WARN: file lh.sphere is not equal in size to lh.smoothwm WARN: file lh.pial is not equal in size to lh.smoothwm WARN: file lh.sphere.reg is not equal in size to lh.smoothwm WARN: file lh.rh.sphere.reg is not equal in size to lh.smoothwm ---------
My guess is that these problems are connected? Anyone know how to fix this? I am the using the FS version from june (?) 2005 on this project.
Cheers, Lars T .Westlye
Hi Lars,
mris2rgb is deprecated. What version are you running? The new recon-all won't call it - you can comment it out of the script if you want, or update your version.
cheers, Brue
On Mon, 17 Oct 2005, Lars Tjelta Westlye wrote:
Dear all,
I'm encountering following error when running morph_subject <subject>. What is wrong?
............. registration took 0.67 hours writing registered surface to ../surf/lh.rh.sphere.reg... /var/lab-data/genetic/id106 /var/lab-data/genetic/id106/scripts /var/lab-data/genetic/id106/scripts
/var/lab-data/genetic/id106/scripts mris2rgb -o id106.reg -both -c /var/lab-data/genetic/id106/surf/lh.sulc -canon /var/lab-data/genetic/id106/surf/lh.sphere.reg /var/lab-data/genetic/id106/surf/lh.sphere.reg /var/lab-data/genetic/id106/rgb
using id106.reg as output stem reading canonical coordinates from /var/lab-data/genetic/id106/surf/lh.sphere.reg. Segmentation fault mris2rgb exited with errors [brain@amygdala genetic]$
Also, when typing check_subject <subject> I get the following warnings: _______ [brain@amygdala genetic]check_subject id106 CHECKING SUBJECT id106 WARN: time for rh.orig is older than rh.qsphere WARN: file rh.inflated is not equal in size to rh.smoothwm WARN: file rh.white is not equal in size to rh.smoothwm WARN: file rh.sphere is not equal in size to rh.smoothwm WARN: file rh.pial is not equal in size to rh.smoothwm WARN: file rh.sphere.reg is not equal in size to rh.smoothwm WARN: time for lh.orig is older than lh.qsphere WARN: file lh.inflated is not equal in size to lh.smoothwm WARN: file lh.white is not equal in size to lh.smoothwm WARN: file lh.sphere is not equal in size to lh.smoothwm WARN: file lh.pial is not equal in size to lh.smoothwm WARN: file lh.sphere.reg is not equal in size to lh.smoothwm WARN: file lh.rh.sphere.reg is not equal in size to lh.smoothwm
My guess is that these problems are connected? Anyone know how to fix this? I am the using the FS version from june (?) 2005 on this project.
Cheers, Lars T .Westlye
Freesurfer mailing list Freesurfer@nmr.mgh.harvard.edu https://mail.nmr.mgh.harvard.edu/mailman/listinfo/freesurfer
Hi, Is there any way to run autorecon2-cp with an edited brain volume so that it concurrently adjusts the pial surface. Everytime I try to run it, it seems to erase my edits to the brain volume. Howeever, running autorecon2-wm or -pial, uses the brain edits. Some help on this would be much appreciated as it would save me a lot of re-processing time! Thanks, Alex
Alex Fornito M.Psych/PhD (clin. neuro.) candidate Melbourne Neuropsychiatry Centre and Department of Psychology The University of Melbourne alexander.fornito@wh.org.au
Hi Alex,
I've looked into your problem and I do see what you mean. Here's a brief run-down on the different flags.
-autorecon2-cp begins with -normalization2, using your control points. Problem is it WILL write over the brain volume, creating a new one. It then finishes the stream from here, using -keepwmedits when running the -segmentation step to preserve any editing you've done to the wm volume.
-autorecon2-wm begins with a newly edited wm volume and first runs -fill generating a new filled.mgz volume and then completes the stream from here.
-autorecon2-pial simply reruns -makefinalsurfs and -cortribbon to remake the final surfaces, reflecting any editing that was done to the brain volume.
We are currently working on a new flag to combat this problem, but until then - here are my suggestions for you now.
1. If your brain editing is necessary for achieving an accurate wm volume:
a. set your control points and run recon-all -normalization2 -usecontrolpoints to fix the intensity. b. make your edits to the brain.mgz volume c. run recon-all -segmentation -keepwmedits to generate a new wm, reflecting your changes to the brain volume and keeping any previous wm edits. d. you will then still need to complete the rest of the stream. You can do this using this command: recon-all -autorecon2 -nosubcortseg -nonormalization2 -nosegmentation.
2. If your brain editing is only necessary for obtaining an accurate pial surface:
a. set your control points and run recon-all -autorecon2-cp (you can add in -nofinalsurfs and -nocortribbon if you are sure that your control points won't fix your pial surfaces without edits. This will save a little processing time, but those steps don't take a tremendous amount of time) b. make your brain volume edits (if the problem wasn't fixed with the control points) c. run recon-all -autorecon2-pial to regenerate your final surfaces.
hope this helps! Jenni
On Tue, 18 Oct 2005, Fornito, Alexander wrote:
Hi, Is there any way to run autorecon2-cp with an edited brain volume so that it concurrently adjusts the pial surface. Everytime I try to run it, it seems to erase my edits to the brain volume. Howeever, running autorecon2-wm or -pial, uses the brain edits. Some help on this would be much appreciated as it would save me a lot of re-processing time! Thanks, Alex
Alex Fornito M.Psych/PhD (clin. neuro.) candidate Melbourne Neuropsychiatry Centre and Department of Psychology The University of Melbourne alexander.fornito@wh.org.au
Freesurfer mailing list Freesurfer@nmr.mgh.harvard.edu https://mail.nmr.mgh.harvard.edu/mailman/listinfo/freesurfer
freesurfer@nmr.mgh.harvard.edu