A must-have tool for VTK! It was a long time that I wanted to perform boolean operations using VTK, and finally, here it is.

The authors also explain why using vtkClipPolyData and a vtkPolyData as ImplicitDataSet does not really produce the proper intersection. I met this problem few month ago, and have never understood why it didn't work.

Also tried Lloyd's class using GTS but with poor results...

DataSets must be compounded of triangles only. Just use vtkTriangle before using the filter, just to be sure.

A second assumption is that there is no coplanar triangles in the datasets. This may happens but very very rarely.

Great figures and also examples to test the class.

Perfectly open since there is no licence conflict. Ready to be included into VTK.

I've tried using my own datasets and get equivalent results. I had no problems with my data.

Yes

Paraview, definitely.

The next tool to implement. I will suggest it on the paraview'e user voice.

Great Job!

This is a needed functionality in VTK to do boolean operations on polydata.

All of the source code is available.

I downloaded the code, configured and compiled it without any issues.

Open with no restirctions.

Code was clear and well written

The code has many memeory leaks. The authors should build with VTK_DEBUG_LEAKS:BOOL=ON

As it stands, it has too many memory leaks. I sugeest usgin vtkSmartPointer's for classes that have scope in a single method.

The memory leaks must be addressed before further evalustion.

Update: All of the memory leaks have been resolved. The code is currently under review: http://review.source.kitware.com/#change,3414

Update: The code has been merged into VTK n Dec 6, 2011.

http://vtk.org/gitweb?p=VTK.git;a=commit;h=1bec98ebb0fe3b02c0ac2b6e4ad09e2b6c29f98d

This is a functionality that has been needed in VTK for a long time. It has been called for repeatedly by many people on the mailing list. The implementation seems thorough.

Yes - the examples use generated meshes so everything is availabe.

Yes, the code compiled and ran on the first try. The results were accurate.

Very good.

vtkTypeRevisionMacro should be replaced with vtkTypeMacro in vtkPolyDataDistance.

There is a clear call for this functionality in VTK. I think it should be added ASAP.