MantisBT - ParaView |
View Issue Details |
|
ID | Project | Category | View Status | Date Submitted | Last Update |
0013490 | ParaView | (No Category) | public | 2012-10-03 14:48 | 2016-08-12 09:59 |
|
Reporter | Joel Mayes | |
Assigned To | Kitware Robot | |
Priority | normal | Severity | minor | Reproducibility | have not tried |
Status | closed | Resolution | moved | |
Platform | | OS | | OS Version | |
Product Version | 3.14.1 | |
Target Version | | Fixed in Version | | |
Project | TBD |
Topic Name | |
Type | incorrect functionality |
|
Summary | 0013490: Cannot slice/contour a data set containg Polyhedron cells where the node values are < 1e-6 |
Description | Slicing or contouring a data set containing polyhedron cells where all the nodal vertex locations are less than 1e-6 produces no sliced or contoured results.
I expect there is a problem with contouring or clipping in polyhedron cells. I found a potential problem in VTK source for ver5.10 src/VTK/Filtering/vtkPolyhedron.cxx in the internal section there is a method called RemoveDuplicatedPointsFromFaceArrayAndEdgeTable and within the method a constant value "const double eps = 0.000001;" is used to merge node locations.
I suspect that if all locations are < than this constant all nodes are merged.
I also notices this constant is repeated in several sections through out the vtkPolyhedron.cxx source.
In the uploaded file a single cell polyhedron is given with 6 faces and 4 nodes per face with node values < 1e-6 , when read by Paraview 3.14.1 and sliced, produced no results. If the file is modified where connectivity remains the same but the nodes are changed to 1e-5, then paraview will correctly slice the modifed data set. |
Steps To Reproduce | |
Additional Information | |
Tags | No tags attached. |
Relationships | related to | 0014485 | closed | Will Schroeder | VTK | vtkCutter produces incorrect results (gaps) in output of unstructured grids containing polyhedron cells |
|
Attached Files | simple_1_g.vtu (1,618) 2012-10-03 14:48 https://www.vtk.org/Bug/file/9289/simple_1_g.vtu |
|
Issue History |
Date Modified | Username | Field | Change |
2012-10-03 14:48 | Joel Mayes | New Issue | |
2012-10-03 14:48 | Joel Mayes | File Added: simple_1_g.vtu | |
2016-03-24 08:39 | Ryo Takayama | Note Added: 0035857 | |
2016-03-24 09:56 | Gerrick Bivins | Note Added: 0035859 | |
2016-03-25 04:50 | Ryo Takayama | Note Added: 0035861 | |
2016-07-06 15:26 | Cory Quammen | Relationship added | related to 0014485 |
2016-07-12 11:56 | Cory Quammen | Note Added: 0036341 | |
2016-08-12 09:59 | Kitware Robot | Note Added: 0038256 | |
2016-08-12 09:59 | Kitware Robot | Status | backlog => closed |
2016-08-12 09:59 | Kitware Robot | Resolution | open => moved |
2016-08-12 09:59 | Kitware Robot | Assigned To | => Kitware Robot |
Notes |
|
(0035857)
|
Ryo Takayama
|
2016-03-24 08:39
|
|
Still not fixed in the latest ParaView 5.0.1 RC2.
I also noticed the same problem happened when resulting cross-sectional surface has a high aspect ratio, for example slicing in x normal direction a cuboid whose VTK cell type is polyhedron and lengths are 1, 1 and 0.01 in x, y and z respectively. |
|
|
(0035859)
|
Gerrick Bivins
|
2016-03-24 09:56
|
|
|
|
(0035861)
|
Ryo Takayama
|
2016-03-25 04:50
|
|
Thanks, Gerrick!
I believe this problem is exactly the same as the issue you reported. |
|
|
(0036341)
|
Cory Quammen
|
2016-07-12 11:56
|
|
A workaround could be to use the Transform filter to scale up the coordinates, do the slicing or contouring, then Transform the result by the inverse scale. |
|
|
(0038256)
|
Kitware Robot
|
2016-08-12 09:59
|
|
Resolving issue as `moved`.
This issue tracker is no longer used. Further discussion of this issue may take place in the current ParaView Issues page linked in the banner at the top of this page. |
|