I haven't been able to recreate your bug on Windows. We don't have a
64 bit Windows machine at this time. Do you think you could go into
the debugger in visual studio to see what's causing the bug?
Also, do you know that you can select a region of interest in the
image when going into automatic segmentation mode? That will use a lot
less memory, because most of the memory is used in automatic
segmentation mode (10x the memory use in manual mode).
Paul.
--
Paul A. Yushkevich, Ph.D.
Research Assistant Professor
Penn Image Computing and Science Laboratory
Department of Radiology
University of Pennsylvania
Thanks so much for sending me the binary. Indeed, I was able to
recreate the bug with your binary, but not with the version that I
built (and that's on the website). I suppose it may be some change in
ITK that's causing this. Perhaps the level set filter is initializing
the level set image differently (not setting the inside and outside to
positive/negative values as it has done before. I try building against
an older version. The version I currently build against is 2.8.1. The
VTK version is 5.0.4 and FLTK is fltk-1.1.x-r5642 (but that should
matter the least). The code currently in the HEAD branch of CVS should
match the binary on itksnap.org.
Paul.