This is necessary since the class has virtual methods, and also
instructs the compiler that the class's vtable is to be stored in the
vtk_rendering library.
- Exception classes cannot be exported due to MSVC's design decisions.
See http://stackoverflow.com/questions/24511376. We must leave these
classes as header only and silence the warnings.
- TransferResource in BufferState.h must remain a header-only class since
there is no vtkm_interop library to compile the class into.
- The VTKDataSetReader hierarchy must similarly remain header-only since
there is no vtkm_io library.
- The OptionParser Action classes are part of a header-only utility and
cannot be easily compiled into a library.
-
5b651172 Merge branch 'master' into extract-subset
6ac23147 Add unit test for Box ImplicitFunction
8190187d Error on empty constructor ExtractGeometryByVOI
836e9472 VTKM_EXEC on operator caused CUDA synchronization error
f3b4b29e Use float not double for defining ImplicitFunctions
c7e03050 Warnings
be977850 Change subset extraction on points to use WorkletMapCellToPoint
11e0a252 Floating point warnings
...
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !736
9e90b31a Merge branch 'tri-tet-fix' of gitlab.kitware.com:Fasel/vtk-m into tri-tet-fix
7c64785f Fix warnings and add to tetrahedralize unit test
7f4d5de2 remove unused code in CMakeList.txt
fb8a8369 update examples/tetrhedra to use filters instead of worklets
8d5ce894 Merge branch 'tri-tet-fix' of gitlab.kitware.com:Fasel/vtk-m into tri-tet-fix
9dcfbf36 Throw error bad type on structured
5ff1d2b1 Use CastAndCall on DynamicCellSet in filters
ee4c3190 fixed compiler errors
...
Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: Robert Maynard <robert.maynard@kitware.com>
Merge-request: !735
b4d542e3 MarchingCubes now merges points correctly when it has multiple iso contours
Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: Kenneth Moreland <kmorel@sandia.gov>
Merge-request: !733
0b12cab1 Fix overshadowing of class member with template parameter
d68b2113 Remove TransportTagReducedValuesIn
dc192b79 Add input range to arguments of transport
Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: Robert Maynard <robert.maynard@kitware.com>
Merge-request: !734
36b48099 Move the processing of scatter cell data to worklet from the filter.
3a1a6aec Added mapping of cell data onto output dataset
984af5a2 Reorganize Triangulate and Tetrahedralize and write filters.
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !732
The previous version of point merging incorrectly merged points across
multiple iso contours, this version fixes that issue.
The marching cubes had a fairly complex block of logic for point merging
since it had to handle numerous runtime switches. This refactor this
logic so it is easier to follow.
Previously the arguments to the operator of a vtkm::cont::arg::Transport
were the control object, the input domain object, and the output range.
If you wanted to, for example, check the size of an input array to make
sure it matched the input range, you would have to know the meaning of
the input domain object to query its range. This made it hard to create
generic transports, like TransportTagArrayIn, that accept data from
multiple different input domains but need to know the input range.
