Hi everybody,
I tried to run the qdec-tool in the dev-env, but experienced some problems with my last subject. This is the environment, I'm working in:
FREESURFER_HOME: /usr/local/freesurfer/dev Build stamp: freesurfer-Linux-centos4-dev-20070811 RedHat release: CentOS release 4.4 (Final) Kernel info: Linux 2.6.9-42.0.3.ELsmp i686 NMR Center info (/space/freesurfer exists): machine: tkmeg SUBJECTS_DIR: /space/megraid/83/MEG-MRI/seder/freesurfer/ PWD: /space/megraid/83/MEG-MRI/seder/freesurfer
... and here's the error I get when I start the group analysis in qdec, subj nmr00199 is the one I added (after I ran -qcache):
ERROR: dimension mismatch between /autofs/space/megraid_083/MEG-MRI/seder/freesurfer/nm r00188_a/surf/lh.thickness.fwhm10.fsaverage.mgh and /autofs/space/megraid_083/MEG-MRI/s eder/freesurfer/nmr00199/surf/lh.thickness.fwhm10.fsaverage.mgh Error in Analyze: command failed: mri_concat /autofs/space/megraid_083/MEG-MRI/seder/fr eesurfer/nmr00188_a/surf/lh.thickness.fwhm10.fsaverage.mgh /autofs/space/megraid_083/ME G-MRI/seder/freesurfer/nmr00172_a/surf/lh.thickness.fwhm10.fsaverage.mgh /autofs/space/ megraid_083/MEG-MRI/seder/freesurfer/nmr00035/surf/ lh.thickness.fwhm10.fsaverage.mgh /a utofs/space/megraid_083/MEG-MRI/seder/freesurfer/nmr00039_a/surf/ lh.thickness.fwhm10.fs average.mgh /autofs/space/megraid_083/MEG-MRI/seder/freesurfer/nmr00046/surf/ lh.thickne ss.fwhm10.fsaverage.mgh /autofs/space/megraid_083/MEG-MRI/seder/freesurfer/nmr00127/sur f/lh.thickness.fwhm10.fsaverage.mgh /autofs/space/megraid_083/MEG-MRI/seder/freesurfer/ nmr00156/surf/lh.thickness.fwhm10.fsaverage.mgh /autofs/space/megraid_083/MEG-MRI/seder /freesurfer/nmr00158/surf/lh.thickness.fwhm10.fsaverage.mgh /autofs/space/megraid_083/M EG-MRI/seder/freesurfer/nmr00159/surf/lh.thickness.fwhm10.fsaverage.mgh /autofs/space/m egraid_083/MEG-MRI/seder/freesurfer/nmr00180_a/surf/ lh.thickness.fwhm10.fsaverage.mgh / autofs/space/megraid_083/MEG-MRI/seder/freesurfer/nmr00189_a/surf/ lh.thickness.fwhm10.f saverage.mgh /autofs/space/megraid_083/MEG-MRI/seder/freesurfer/nmr00034/surf/ lh.thickn ess.fwhm10.fsaverage.mgh /autofs/space/megraid_083/MEG-MRI/seder/freesurfer/nmr00031_a/ surf/lh.thickness.fwhm10.fsaverage.mgh /autofs/space/megraid_083/MEG-MRI/seder/freesurf er/nmr00070/surf/lh.thickness.fwhm10.fsaverage.mgh /autofs/space/megraid_083/MEG-MRI/se der/freesurfer/nmr00098/surf/lh.thickness.fwhm10.fsaverage.mgh /autofs/space/megraid_08 3/MEG-MRI/seder/freesurfer/nmr00013/surf/ lh.thickness.fwhm10.fsaverage.mgh /autofs/spac e/megraid_083/MEG-MRI/seder/freesurfer/nmr00182_a/surf/ lh.thickness.fwhm10.fsaverage.mg h /autofs/space/megraid_083/MEG-MRI/seder/freesurfer/nmr00052/surf/ lh.thickness.fwhm10. fsaverage.mgh /autofs/space/megraid_083/MEG-MRI/seder/freesurfer/nmr00123/surf/ lh.thick ness.fwhm10.fsaverage.mgh /autofs/space/megraid_083/MEG-MRI/seder/freesurfer/nmr00076/s urf/lh.thickness.fwhm10.fsaverage.mgh /autofs/space/megraid_083/MEG-MRI/seder/freesurfe r/nmr00183_a/surf/lh.thickness.fwhm10.fsaverage.mgh /autofs/space/megraid_083/MEG-MRI/s eder/freesurfer/nmr00184_a/surf/lh.thickness.fwhm10.fsaverage.mgh /autofs/space/megraid _083/MEG-MRI/seder/freesurfer/nmr00181_a/surf/ lh.thickness.fwhm10.fsaverage.mgh /autofs /space/megraid_083/MEG-MRI/seder/freesurfer/nmr00068/surf/ lh.thickness.fwhm10.fsaverage .mgh /autofs/space/megraid_083/MEG-MRI/seder/freesurfer/nmr00073/surf/ lh.thickness.fwhm 10.fsaverage.mgh /autofs/space/megraid_083/MEG-MRI/seder/freesurfer/nmr00199/surf/lh.th ickness.fwhm10.fsaverage.mgh --o /autofs/space/megraid_083/MEG-MRI/seder/freesurfer/qde c/Untitled/y.mgh
Could this be due to the dev-env of the qcache-command (the log says everything went fine)? Autorecon-3 also seems to have run fine in this patient.
Thanks a lot for your help,
Claus
Claus,
Has the recon-all -qcache been run for the subject nmr00199? If so, was there a significant number of days since -qcache was run on the other subjects? If so, you may need to run recon-all -qcache on all the subjects you want to use with qdec.
Nick
On Tue, 2007-08-14 at 18:59 -0400, Claus Reinsberger wrote:
Hi everybody,
I tried to run the qdec-tool in the dev-env, but experienced some problems with my last subject. This is the environment, I'm working in:
FREESURFER_HOME: /usr/local/freesurfer/dev Build stamp: freesurfer-Linux-centos4-dev-20070811 RedHat release: CentOS release 4.4 (Final) Kernel info: Linux 2.6.9-42.0.3.ELsmp i686 NMR Center info (/space/freesurfer exists): machine: tkmeg SUBJECTS_DIR: /space/megraid/83/MEG-MRI/seder/freesurfer/ PWD: /space/megraid/83/MEG-MRI/seder/freesurfer
... and here's the error I get when I start the group analysis in qdec, subj nmr00199 is the one I added (after I ran -qcache):
ERROR: dimension mismatch between /autofs/space/megraid_083/MEG-MRI/seder/freesurfer/nm r00188_a/surf/lh.thickness.fwhm10.fsaverage.mgh and /autofs/space/megraid_083/MEG-MRI/s eder/freesurfer/nmr00199/surf/lh.thickness.fwhm10.fsaverage.mgh Error in Analyze: command failed: mri_concat /autofs/space/megraid_083/MEG-MRI/seder/fr eesurfer/nmr00188_a/surf/lh.thickness.fwhm10.fsaverage.mgh /autofs/space/megraid_083/ME G- MRI/seder/freesurfer/nmr00172_a/surf/lh.thickness.fwhm10.fsaverage.mgh /autofs/space/ megraid_083/MEG- MRI/seder/freesurfer/nmr00035/surf/lh.thickness.fwhm10.fsaverage.mgh /a utofs/space/megraid_083/MEG- MRI/seder/freesurfer/nmr00039_a/surf/lh.thickness.fwhm10.fs average.mgh /autofs/space/megraid_083/MEG- MRI/seder/freesurfer/nmr00046/surf/lh.thickne ss.fwhm10.fsaverage.mgh /autofs/space/megraid_083/MEG-MRI/seder/freesurfer/nmr00127/sur f/lh.thickness.fwhm10.fsaverage.mgh /autofs/space/megraid_083/MEG-MRI/seder/freesurfer/ nmr00156/surf/lh.thickness.fwhm10.fsaverage.mgh /autofs/space/megraid_083/MEG-MRI/seder /freesurfer/nmr00158/surf/lh.thickness.fwhm10.fsaverage.mgh /autofs/space/megraid_083/M EG- MRI/seder/freesurfer/nmr00159/surf/lh.thickness.fwhm10.fsaverage.mgh /autofs/space/m egraid_083/MEG- MRI/seder/freesurfer/nmr00180_a/surf/lh.thickness.fwhm10.fsaverage.mgh / autofs/space/megraid_083/MEG- MRI/seder/freesurfer/nmr00189_a/surf/lh.thickness.fwhm10.f saverage.mgh /autofs/space/megraid_083/MEG- MRI/seder/freesurfer/nmr00034/surf/lh.thickn ess.fwhm10.fsaverage.mgh /autofs/space/megraid_083/MEG-MRI/seder/freesurfer/nmr00031_a/ surf/lh.thickness.fwhm10.fsaverage.mgh /autofs/space/megraid_083/MEG-MRI/seder/freesurf er/nmr00070/surf/lh.thickness.fwhm10.fsaverage.mgh /autofs/space/megraid_083/MEG-MRI/se der/freesurfer/nmr00098/surf/lh.thickness.fwhm10.fsaverage.mgh /autofs/space/megraid_08 3/MEG- MRI/seder/freesurfer/nmr00013/surf/lh.thickness.fwhm10.fsaverage.mgh /autofs/spac e/megraid_083/MEG- MRI/seder/freesurfer/nmr00182_a/surf/lh.thickness.fwhm10.fsaverage.mg h /autofs/space/megraid_083/MEG- MRI/seder/freesurfer/nmr00052/surf/lh.thickness.fwhm10. fsaverage.mgh /autofs/space/megraid_083/MEG- MRI/seder/freesurfer/nmr00123/surf/lh.thick ness.fwhm10.fsaverage.mgh /autofs/space/megraid_083/MEG-MRI/seder/freesurfer/nmr00076/s urf/lh.thickness.fwhm10.fsaverage.mgh /autofs/space/megraid_083/MEG-MRI/seder/freesurfe r/nmr00183_a/surf/lh.thickness.fwhm10.fsaverage.mgh /autofs/space/megraid_083/MEG-MRI/s eder/freesurfer/nmr00184_a/surf/lh.thickness.fwhm10.fsaverage.mgh /autofs/space/megraid _083/MEG- MRI/seder/freesurfer/nmr00181_a/surf/lh.thickness.fwhm10.fsaverage.mgh /autofs /space/megraid_083/MEG- MRI/seder/freesurfer/nmr00068/surf/lh.thickness.fwhm10.fsaverage .mgh /autofs/space/megraid_083/MEG- MRI/seder/freesurfer/nmr00073/surf/lh.thickness.fwhm 10.fsaverage.mgh /autofs/space/megraid_083/MEG-MRI/seder/freesurfer/nmr00199/surf/lh.th ickness.fwhm10.fsaverage.mgh --o /autofs/space/megraid_083/MEG-MRI/seder/freesurfer/qde c/Untitled/y.mgh
Could this be due to the dev-env of the qcache-command (the log says everything went fine)? Autorecon-3 also seems to have run fine in this patient.
Thanks a lot for your help,
Claus
Freesurfer mailing list Freesurfer@nmr.mgh.harvard.edu https://mail.nmr.mgh.harvard.edu/mailman/listinfo/freesurfer
Yea, sorry, a few months ago I changed the way we store surface overlay files. I used to try to "reshape" them so that no dimension was greater than 32k (a nifti/analyze limit), but it just kept creating problems. If you're going to nifti/analyze, you can still reshape them, but you have to specify it explicitly.
doug
On Tue, 14 Aug 2007, Nick Schmansky wrote:
Claus,
Has the recon-all -qcache been run for the subject nmr00199? If so, was there a significant number of days since -qcache was run on the other subjects? If so, you may need to run recon-all -qcache on all the subjects you want to use with qdec.
Nick
On Tue, 2007-08-14 at 18:59 -0400, Claus Reinsberger wrote:
Hi everybody,
I tried to run the qdec-tool in the dev-env, but experienced some problems with my last subject. This is the environment, I'm working in:
FREESURFER_HOME: /usr/local/freesurfer/dev Build stamp: freesurfer-Linux-centos4-dev-20070811 RedHat release: CentOS release 4.4 (Final) Kernel info: Linux 2.6.9-42.0.3.ELsmp i686 NMR Center info (/space/freesurfer exists): machine: tkmeg SUBJECTS_DIR: /space/megraid/83/MEG-MRI/seder/freesurfer/ PWD: /space/megraid/83/MEG-MRI/seder/freesurfer
... and here's the error I get when I start the group analysis in qdec, subj nmr00199 is the one I added (after I ran -qcache):
ERROR: dimension mismatch between /autofs/space/megraid_083/MEG-MRI/seder/freesurfer/nm r00188_a/surf/lh.thickness.fwhm10.fsaverage.mgh and /autofs/space/megraid_083/MEG-MRI/s eder/freesurfer/nmr00199/surf/lh.thickness.fwhm10.fsaverage.mgh Error in Analyze: command failed: mri_concat /autofs/space/megraid_083/MEG-MRI/seder/fr eesurfer/nmr00188_a/surf/lh.thickness.fwhm10.fsaverage.mgh /autofs/space/megraid_083/ME G- MRI/seder/freesurfer/nmr00172_a/surf/lh.thickness.fwhm10.fsaverage.mgh /autofs/space/ megraid_083/MEG- MRI/seder/freesurfer/nmr00035/surf/lh.thickness.fwhm10.fsaverage.mgh /a utofs/space/megraid_083/MEG- MRI/seder/freesurfer/nmr00039_a/surf/lh.thickness.fwhm10.fs average.mgh /autofs/space/megraid_083/MEG- MRI/seder/freesurfer/nmr00046/surf/lh.thickne ss.fwhm10.fsaverage.mgh /autofs/space/megraid_083/MEG-MRI/seder/freesurfer/nmr00127/sur f/lh.thickness.fwhm10.fsaverage.mgh /autofs/space/megraid_083/MEG-MRI/seder/freesurfer/ nmr00156/surf/lh.thickness.fwhm10.fsaverage.mgh /autofs/space/megraid_083/MEG-MRI/seder /freesurfer/nmr00158/surf/lh.thickness.fwhm10.fsaverage.mgh /autofs/space/megraid_083/M EG- MRI/seder/freesurfer/nmr00159/surf/lh.thickness.fwhm10.fsaverage.mgh /autofs/space/m egraid_083/MEG- MRI/seder/freesurfer/nmr00180_a/surf/lh.thickness.fwhm10.fsaverage.mgh / autofs/space/megraid_083/MEG- MRI/seder/freesurfer/nmr00189_a/surf/lh.thickness.fwhm10.f saverage.mgh /autofs/space/megraid_083/MEG- MRI/seder/freesurfer/nmr00034/surf/lh.thickn ess.fwhm10.fsaverage.mgh /autofs/space/megraid_083/MEG-MRI/seder/freesurfer/nmr00031_a/ surf/lh.thickness.fwhm10.fsaverage.mgh /autofs/space/megraid_083/MEG-MRI/seder/freesurf er/nmr00070/surf/lh.thickness.fwhm10.fsaverage.mgh /autofs/space/megraid_083/MEG-MRI/se der/freesurfer/nmr00098/surf/lh.thickness.fwhm10.fsaverage.mgh /autofs/space/megraid_08 3/MEG- MRI/seder/freesurfer/nmr00013/surf/lh.thickness.fwhm10.fsaverage.mgh /autofs/spac e/megraid_083/MEG- MRI/seder/freesurfer/nmr00182_a/surf/lh.thickness.fwhm10.fsaverage.mg h /autofs/space/megraid_083/MEG- MRI/seder/freesurfer/nmr00052/surf/lh.thickness.fwhm10. fsaverage.mgh /autofs/space/megraid_083/MEG- MRI/seder/freesurfer/nmr00123/surf/lh.thick ness.fwhm10.fsaverage.mgh /autofs/space/megraid_083/MEG-MRI/seder/freesurfer/nmr00076/s urf/lh.thickness.fwhm10.fsaverage.mgh /autofs/space/megraid_083/MEG-MRI/seder/freesurfe r/nmr00183_a/surf/lh.thickness.fwhm10.fsaverage.mgh /autofs/space/megraid_083/MEG-MRI/s eder/freesurfer/nmr00184_a/surf/lh.thickness.fwhm10.fsaverage.mgh /autofs/space/megraid _083/MEG- MRI/seder/freesurfer/nmr00181_a/surf/lh.thickness.fwhm10.fsaverage.mgh /autofs /space/megraid_083/MEG- MRI/seder/freesurfer/nmr00068/surf/lh.thickness.fwhm10.fsaverage .mgh /autofs/space/megraid_083/MEG- MRI/seder/freesurfer/nmr00073/surf/lh.thickness.fwhm 10.fsaverage.mgh /autofs/space/megraid_083/MEG-MRI/seder/freesurfer/nmr00199/surf/lh.th ickness.fwhm10.fsaverage.mgh --o /autofs/space/megraid_083/MEG-MRI/seder/freesurfer/qde c/Untitled/y.mgh
Could this be due to the dev-env of the qcache-command (the log says everything went fine)? Autorecon-3 also seems to have run fine in this patient.
Thanks a lot for your help,
Claus
Freesurfer mailing list Freesurfer@nmr.mgh.harvard.edu https://mail.nmr.mgh.harvard.edu/mailman/listinfo/freesurfer
Freesurfer mailing list Freesurfer@nmr.mgh.harvard.edu https://mail.nmr.mgh.harvard.edu/mailman/listinfo/freesurfer
freesurfer@nmr.mgh.harvard.edu