f5a95046a Disabled a few contour tree tests to reduce time needed
8f3e86170 Minor refactoring of tests for contour tree.
237b5ad66 Add pre-simplification for contour tree
809127ed9 (Bug)fix to suppress off-block regular nodes in Augmented Tree
Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: Gunther Weber <ghweber@lbl.gov>
Merge-request: !3227
Add pre-simplification as mitigation for memory usage and scaling issues
when running distributed contour tree algorithm on highly complex data
sets.
Co-authored-by: Mingzhe Li <mingzhefluorite@gmail.com>
There was a use of a deprecated method buried in a support class of
`WorkletCellNeighborhood`. This fixes that deprecation and also adds a
missing test for `WorkletCellNeighborhood` to prevent such things in the
future.
The flying edges implementation has an optimization where it will traverse
meshes in the Y direction rather than the X direction on the GPU. It
created mostly correct results, but the triangles' winding was the opposite
from the CPU. This was mostly problematic when normals were generated from
the gradients. In this case, the gradient would point from the "back" of
the face, and that can cause shading problems with some renderers.
This has been fixed to make the windings consistent on the GPU with the CPU
and the gradients.
Fixes#825
The flying edges code has two main implementations: one where it
traverses the mesh in the X direction (for CPU) and one where it
traverses the mesh in the Y direction (for GPU). There were several
places in the code where the device was checked for the case to use.
This resulted in several places where the "GPU" devices had to be
listed.
Improve the code by consolidate the check to a single piece of code in
`FlyingEdgesHelpers.h` where the axis to sum structure is selected. Make
the overloads based on this structure rather than directly on the
devices.
ea44b4b50 Better document the creation of Field and CoordinateSystem
Acked-by: Kitware Robot <kwrobot@kitware.com>
Reviewed-by: Vicente Bolea <vicente.bolea@kitware.com>
Merge-request: !3262
The constructors for `vtkm::cont::Field` and `vtkm::cont::CoordinateSystem`
were missing from the built user's guide. The construction of these classes
from names, associations, and arrays are now provided in the documentation.
Also added new versions of `AddField` and `AddCoordinateSystem` to
`vtkm::cont::DataSet` that mimic the constructors. This adds some sytatic
sugar so you can just emplace the field instead of constructing and
passing.
Fix to remedy https://gitlab.kitware.com/vtk/vtk-m/-/issues/808
This fix changes on Case 5 to use quads instead of triangles to remedy
the airtightness of clipping. Case 10 -- which is isometric is left
untouched as it may cause overlaps in clip and clip inverse
intersection.
This MR causes the output of VTK-m to be different than VisIt and VTK
as they suffer similar problems described in the issue.
9efc8712d Add a form of CellInterpolate that operates on whole cell sets
Acked-by: Kitware Robot <kwrobot@kitware.com>
Reviewed-by: Vicente Bolea <vicente.bolea@kitware.com>
Merge-request: !3253
23bf92a51 Move the flow test data set header
Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: Dave Pugmire <dpugmire@gmail.com>
Merge-request: !3252
The initial implementation of `CellInterpolate` takes arguments that are
expected from a topology map worklet. However, sometimes you want to
interplate cells that are queried from locators or otherwise come from a
`WholeCellSet` control signature argument.
A new form of `CellInterpolate` is added to handle this case.
The header file `GenerateTestDataSets.h` was located in
`vtkm/worklet/testing`. However, the only tests that used this header
are in `vtkm/filter/flow/testing`. Thus, the header file is moved to where
it is used.
