runTimePostProcessing: use existing cutting planes
No child items are currently assigned. Use child items to break down this issue into smaller parts.
Link issues together to show that they're related. Learn more.
Activity
- Mark OLESEN mentioned in issue #1125 (closed)
mentioned in issue #1125 (closed)
- Mark OLESEN mentioned in commit 78430150
mentioned in commit 78430150
- Mark OLESEN mentioned in commit 0cbb07f5
mentioned in commit 0cbb07f5
- Mark OLESEN mentioned in issue #1126
mentioned in issue #1126
- Maintainer
Add direct support for vtp surfaces
- Mark OLESEN mentioned in commit 98fb25e7
mentioned in commit 98fb25e7
- Maintainer
@Prashant - This should now handle vtp properly for current and future. I tested (ellipse tutorial) using surfaceMeshTriangulate to extract the boundary surface.
Another point for checking is the dummy runTimePostProcessing. If you have a system without VTK or ParaView for compilation, it should now create a stub for the functionObject. If you use runTimePP and don't have the proper VTK libs at compile time, it should now just complaint and toss out the function object, but not crash anything.