mirror of
https://gitlab.kitware.com/vtk/vtk-m
synced 2024-09-08 13:23:51 +00:00
aaf49915e0
There was a bug with Flying Edges checking the boundary conditions in the z-direction. It was comparing the z index to the size of the y dimension, not the z dimension. This simple typo was probably missed because most of the tests use square meshes. To catch the problem, you need a mesh that has a different number of points in the y and z directions and the contour has to go past the positive z boundary. When this error was hit, the indices for the edges on that boundary were not recorded, and later interpolation used garbage values for edge's point ids. |
||
|---|---|---|
| .. | ||
| amrArrays2D.png | ||
| amrArrays3D.png | ||
| contour-tangle.png | ||
| contour-uniform-boundaries.png | ||
| contour-uniform.png | ||
| contour-wedge.png | ||
| point-transform.png | ||
| slice-structured-points-plane.png | ||
| slice-structured-points-sphere.png | ||
| slice-unstructured-grid-cylinder.png | ||
| slice-unstructured-grid-plane.png | ||
| split-sharp-edges.png | ||
| streamline.png | ||
| surface-normals.png | ||
