I have always assumed this was a harmless warning because of the following note in the N3 FAQ. (Also because the warning appears even when running bert.)
http://www.bic.mni.mcgill.ca/software/N3/FAQ/
Why does nu_correct print ominous warnings while running? Warning messages like
Not implemented yet in cache_volume_range_has_changed() Not implemented yet in cache_volume_range_has_changed()
are harmless. They refer to a portion of the volume_io libary that N3 does not use.
Ray
On May 27, 2004, at 7:39 AM, Bruce Fischl wrote:
I don't think that's an error, I think it's a warning, isn't it?
On Thu, 27 May 2004 orphoebe@polyu.edu.hk wrote:
Hi Bruce and Yasunari,
Thanks for your suggestions. The setenv LANG C works for 'Out of memory' error. However, after I get through the mritotal, it comes with another error of 'Not implemented yet in cache_volume range...' as follows. I see that somebody asks this question before but I can't find the solution. Any suggestions?
Thanks, Phoebe.
mri_add_xform_to_header /mnt/usb1/uch_language/inflated/040415_ckh/mri/transforms/ talairach.xfm /mnt/usb1/uch_language/inflated/040415_ckh/mri/orig /mnt/usb1/uch_language/inflated/040415_ckh/mri/orig Thu May 27 15:56:30 GMT+8 2004
Nu Intensity Correction Thu May 27 15:56:30 GMT+8 2004 mri_convert orig nu/nu0.mnc mri_convert orig nu/nu0.mnc reading from orig... TR=0.00, te=0.00, flip angle=0.00 i_ras = (-1, 0, 0) j_ras = (0, 0, -1) k_ras = (0, 1, 0) writing to nu/nu0.mnc... nu_correct -clobber nu/nu0.mnc nu/nu1.mnc [phoebe@marvin:/mnt/usb1/uch_language/inflated/040415_ckh/mri/] [2004-05-27 15:56:40] running: /usr/pubsw/packages/mni/current/bin/nu_estimate_np_and_em -parzen -log -sharpen 0.15 0.01 -iterations 50 -stop 0.001 -shrink 4 -auto_mask -nonotify -b_spline 1 -distance 200 -quiet -execute -clobber -nokeeptmp -tmpdir /usr/tmp/nu_correct_6196/ nu/nu0.mnc nu/nu1.imp
Processing:........................................................... ......DoneNot Not implemented yet in cache_volume_range_has_changed() Not implemented yet in cache_volume_range_has_changed() Processing:........................................................... ......DoneNot Not implemented yet in cache_volume_range_has_changed() Not implemented yet in cache_volume_range_has_changed() Processing:........................................................... ......DoneNot Not implemented yet in cache_volume_range_has_changed() Not implemented yet in cache_volume_range_has_changed()
---- Original message ----
Date: Wed, 26 May 2004 14:45:07 -0400 (EDT) From: Bruce Fischl fischl@nmr.mgh.harvard.edu Subject: Re: [Freesurfer] Out of memory error To: orphoebe@polyu.edu.hk Cc: freesurfer@nmr.mgh.harvard.edu
Hi Phoebe,
I think this is a problem with the MNI tools that they know
about. Someone
posted a solution here, which I think involved setting the
LANG env
variable. Check out the MNI website.
Bruce
On Thu, 27 May 2004 orphoebe@polyu.edu.hk wrote:
Hi,
I recently collected a 1-mm anatomical scan and tried to inflate it using the recon-all script. However, I got an error message 'Out of memory!' everytime at mritotal. I tried to increase the output size when I converted the dcm images to COR format, but it didn't work either. Do you have any suggestions?
Thanks, Phoebe.
Phoebe Suk-tak Chan, Ph.D. Assistant Professor Hong Kong Polytechnic University Department of Optometry and Radiography Hunghom, Kowloon Hong Kong SAR Tel: (852) 2766 6095 Fax: (852) 2764 6051 _______________________________________________ Freesurfer mailing list Freesurfer@nmr.mgh.harvard.edu https://mail.nmr.mgh.harvard.edu/mailman/listinfo/freesurfer
Phoebe Suk-tak Chan, Ph.D. Assistant Professor Hong Kong Polytechnic University Department of Optometry and Radiography Hunghom, Kowloon Hong Kong SAR Tel: (852) 2766 6095 Fax: (852) 2764 6051 _______________________________________________ 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