MantisBT - VTK |
View Issue Details |
|
ID | Project | Category | View Status | Date Submitted | Last Update |
0014485 | VTK | (No Category) | public | 2013-12-20 14:52 | 2016-08-12 09:55 |
|
Reporter | Gerrick Bivins | |
Assigned To | Will Schroeder | |
Priority | high | Severity | minor | Reproducibility | have not tried |
Status | closed | Resolution | moved | |
Platform | | OS | | OS Version | |
Product Version | 5.10.1 | |
Target Version | | Fixed in Version | | |
Project | TBD |
Type | incorrect functionality |
|
Summary | 0014485: vtkCutter produces incorrect results (gaps) in output of unstructured grids containing polyhedron cells |
Description | I’ve run into a strange problem where with unstructured grids containing polyhedron cells, vtkCutter is leaving “gaps” in the output polydata.
Attached is a simple 2 cell unstructured grid and example that demonstrates the problem.
|
Steps To Reproduce | |
Additional Information | |
Tags | polyhedron |
Relationships | related to | 0015999 | closed | Kitware Robot | VTK | vtkCutter sometimes incorrectly cuts vtkQuadraticHexahedron when generating polygons | related to | 0013490 | closed | Kitware Robot | ParaView | Cannot slice/contour a data set containg Polyhedron cells where the node values are < 1e-6 | related to | 0015841 | closed | Kitware Robot | VTK | vtkCutter not cutting vtkPolyhedron cells correctly |
|
Attached Files | slicer_gap_example.vtu (1,626) 2013-12-20 14:52 https://www.vtk.org/Bug/file/9580/slicer_gap_example.vtu Cutter2CellPolyhedron-issue.cxx (4,229) 2013-12-20 14:53 https://www.vtk.org/Bug/file/9581/Cutter2CellPolyhedron-issue.cxx |
|
Issue History |
Date Modified | Username | Field | Change |
2013-12-20 14:52 | Gerrick Bivins | New Issue | |
2013-12-20 14:52 | Gerrick Bivins | File Added: slicer_gap_example.vtu | |
2013-12-20 14:53 | Gerrick Bivins | File Added: Cutter2CellPolyhedron-issue.cxx | |
2013-12-20 14:53 | Gerrick Bivins | Tag Attached: polyhedron | |
2014-01-13 17:47 | Gerrick Bivins | Note Added: 0032173 | |
2014-10-06 14:58 | Will Schroeder | Assigned To | => Will Schroeder |
2015-11-18 17:24 | Frank Conradie | Note Added: 0035469 | |
2016-03-24 09:54 | Gerrick Bivins | Note Added: 0035858 | |
2016-03-25 07:30 | Ryo Takayama | Note Added: 0035862 | |
2016-07-06 15:26 | Cory Quammen | Relationship added | related to 0015999 |
2016-07-06 15:26 | Cory Quammen | Relationship added | related to 0013490 |
2016-07-06 15:27 | Cory Quammen | Relationship added | related to 0015841 |
2016-08-12 09:55 | Kitware Robot | Note Added: 0037317 | |
2016-08-12 09:55 | Kitware Robot | Status | backlog => closed |
2016-08-12 09:55 | Kitware Robot | Resolution | open => moved |
Notes |
|
(0032173)
|
Gerrick Bivins
|
2014-01-13 17:47
|
|
The issue is the hard coded tolerance setting in the calculation of vtkPolyhedron::CheckContourDimensions.
By changing the
static const double eigenvalueRatioThresh =.0001
to
static const double eigenvalueRatioThresh =1e-12
using vtkCutter on my models produced the correct output.
The attached model can use a different tolerance but to capture
correct results from all of my models (so far) it needed to be 1e-12;
The reason that it failed has to do with the eigenvalues check and the tolerance.
For my models, the eigenvalues calculated were something like:
420.25,.25,0 (failed to generate)
420.25,225.0,0 (generated)
For the failed case,the ratio calculations passed both of the "if conditions"
because of the low tolerance, thus reducing the dimensions to "1".
I'm not sure of the proper fix but my suggestion would be to change the tolerance to
something much smaller (1e-12) and/or expose a way to
set the tolerance from the mesh or the algorithm. |
|
|
(0035469)
|
Frank Conradie
|
2015-11-18 17:24
|
|
I am experiencing this issue as well, but the suggested "eigenvalueRatioThresh" fix does not work for me. Is there any news on this issue? |
|
|
(0035858)
|
Gerrick Bivins
|
2016-03-24 09:54
|
|
|
|
(0035862)
|
Ryo Takayama
|
2016-03-25 07:30
|
|
With ParaView 5.0.1 RC2, I got the same result as Frank mentioned. |
|
|
(0037317)
|
Kitware Robot
|
2016-08-12 09:55
|
|
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. |
|