vtk-m/docs/changelog
Kenneth Moreland a195ce883a Fix Flying Edges z-boundary condition with non-square input
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.
2022-09-29 08:39:52 -06:00
..
1.3 docs: update gitlab links to include /-/ component 2020-05-26 14:48:49 -04:00
1.4 Add release notes for v1.4.0 2019-06-26 12:13:47 -04:00
1.5 Add release notes for v1.5.0 2019-10-15 13:40:46 -04:00
1.5.1 Add release notes for v1.5.1 2020-03-13 12:55:43 -04:00
1.6 1.6.0-rc1 is our 7th official release of VTK-m. 2021-04-06 18:28:53 -04:00
1.7 Add release notes for 1.7.0-rc1 2021-10-21 13:08:40 -04:00
1.7.1 Add release notes for 1.7.1 2022-01-28 18:16:04 -05:00
flying-edges-z-boundary-fix.md Fix Flying Edges z-boundary condition with non-square input 2022-09-29 08:39:52 -06:00