[MINC-users] "Not implemented yet in cache_volume_range_has_chang ed()"

[Andrew Janke]

On Sun, 30 May 2004 adamt-pub@fmrif.nimh.nih.gov wrote:

> Was there a solution posted for the problem Max posted back in January
> (attached below)? I am encountering the same problem with minctracc:
>
> [adamt@aurum sk-2004-05-27]$ minctracc -verbose 5 -lsq6 -tricubic -step
> 0.4 0.4 0.4 -mi sk-2004-05-27_3.mnc sk-2004-05-27_2.mnc
> sk-2004-05-27_3to2.xfm
> (snip)
> ..................................................................
> Not implemented yet in cache_volume_range_has_changed()
> WARNING: target volume not UNSIGNED_BYTE, will do conversion now.
> Converting:
> ..................................................................
> Not implemented yet in cache_volume_range_has_changed()
> Segmentation fault

Adam,

First, It's likely that the "Not implemented in ..." looking error is not an
error at all.  And thus might be throwwing you off. This is an old debugging
type statement that was never removed from the code.

If your problem is indeed only apparent when you use larger volumes you may be
hitting the volume_io caching limit.  (and caching can be a bit flaky in
volume_io, best to let the OS look after such things...)  So if you read the
volume_io Documentation, you'll note a environment variable:
VOLUME_CACHE_THRESHOLD.  Perhaps try increasing this to something (very) large,
this will force volume_io to never cache (internally)


--
Andrew Janke  ( rotorATcmr.uq.edu.au || www.cmr.uq.edu.au/~rotor )
Australia->University of Queensland->Centre for Magnetic Resonance
W: +61 7 3232 7254  ||  H: +61 7 3800 4042  ||  M: +61 4 2138 8581