MantisBT - VTK
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0004229VTK(No Category)public2006-12-19 07:232016-08-12 09:54
ReporterMichael Knopke 
Assigned ToBerk Geveci 
PrioritynormalSeverityminorReproducibilityalways
StatusclosedResolutionmoved 
PlatformOSOS Version
Product Version 
Target VersionFixed in Version 
Project
Type
Summary0004229: vtkMarchingCubes and vtkImageMarchingCubes fail on large Datasets
Descriptionusing both of these classes can result in a blank screen if the dataset is too big and the threshold value produces alot of "hits" (e.g. CT-scan with threashold around 1000 (bones)). It is not a problem of the amount of Ram, since swap file was set to extreme large value (10GB) for testing.

pipeline is very simple:

// vtkVolume16Reader
v16->SetDataDimensions (lVolumeInfo.XDim,lVolumeInfo.YDim);
 v16->SetImageRange (0,lVolumeInfo.ZDim);
 v16->SetDataByteOrderToLittleEndian();
 v16->SetFilePrefix(filename.c_str());
 v16->SetDataSpacing (lVolumeInfo.XSpacing, lVolumeInfo.YSpacing, lVolumeInfo.ZSpacing);
 v16->ReleaseDataFlagOff();
 v16->Update();

// marching cubes
iso_Extractor->SetInputConnection(median3D->GetOutputPort());
  iso_Extractor->SetValue(0, 1068);
  iso_Extractor->ComputeGradientsOn();
  iso_Extractor->ComputeNormalsOn();
  iso_Extractor->ReleaseDataFlagOff();

// the mapper for the iso_extractor
  iso_Mapper->SetInput(iso_Extractor->GetOutput());
  iso_Mapper->ScalarVisibilityOff();
  iso_Mapper->ReleaseDataFlagOff();


// the actor for the iso_extractor
  iso_Actor->SetMapper(iso_Mapper);
  iso_Actor->SetPosition(0,0,0);

DataSet is 431 slices CT-Data with 512px. (works with oder classes without problems). This behaviour happens on most big DataSets.

Using vtkImageMarchingCubes with Streaming didn't help either.
Steps To Reproduce
Additional Information
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2008-02-06 10:28Jeff BaumesNote Added: 0010388
2008-02-06 10:30Jeff BaumesAssigned ToWill Schroeder => Berk Geveci
2008-02-06 10:30Jeff BaumesSeveritymajor => minor
2008-02-06 11:09Michael KnopkeNote Added: 0010394
2011-06-16 13:11Zack GalbreathCategory => (No Category)
2016-08-12 09:54Kitware RobotNote Added: 0036898
2016-08-12 09:54Kitware RobotStatusexpired => closed
2016-08-12 09:54Kitware RobotResolutionopen => moved

Notes
(0006000)
Michael Knopke   
2006-12-19 07:30   
If the size of the volume is reduced (e.g. with vtkImageRescale or vtkImageShrinker3D) it shows the correct result (with loss of quality of course). So this seems to be a memory problem, but as said swap file is large.
(0010388)
Jeff Baumes   
2008-02-06 10:28   
With a 32-bit build, the size of the swap does not matter. The max is 2GB. Did you try this with a 64-bit build?
(0010394)
Michael Knopke   
2008-02-06 11:09   
No, didn't try 64Build yet, but I guess it's really a 2GB issue and the filter is working fine. There should be some kind of memory management in VTK, since it is quite hard to track the amount of memory that's being used in a complex pipeline and will be used by a filter when updating. Right now alot of filters just crash when exceeding the limit or is there something I missed? Simple Try-catch doesn't prevent crashing.
(0036898)
Kitware Robot   
2016-08-12 09:54   
Resolving issue as `moved`.

This issue tracker is no longer used. Further discussion of this issue may take place in the current VTK Issues page linked in the banner at the top of this page.