[vtkusers] problem with marching cubes in VTK 4.0

[Bob Lewis]

VTK folk:

I've got a Python script that makes use of vtkMarchingCubes to
tesselate a stack of confocal microscopic PPM images (of a cell) that
worked just fine in VTK 3.2.  You can see a sample image at:

http://www.tricity.wsu.edu/~bobl/vtk_problem/3_2.gif

After making a necessary slight change in an unrelated part of the
code (replaced vtkScalar with vtkFloatArray as recommended in the
FAQ), I run the code again and get something that looks like the
result of some bizarre indexing problem in vtkMarchingCubes:

http://www.tricity.wsu.edu/~bobl/vtk_problem/4_0.gif

Before I do any more hit-or-miss tweaking of my program, has anyone
else on the list seen this?  Is there a fix?

    - Bob Lewis
      Washington State University

P.S.  Python support seems to have dropped a lot from 3.2 to 4.0.
      One measure: about 30 .py files in 4.0, compared to 399 in 3.2.
      I wonder if I've got a bad release?