We want to make sure that VariantArrayHandleContainer has as little
overhead when launch worklets as possible. To do so we cache
type information to make deducing the `T` type of ArrayHandles
as fast as possible.
2e93443b1 All bit shifting in vtkm::cont::Logging happens in unsigned space
Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: Allison Vacanti <allison.vacanti@kitware.com>
Merge-request: !1510
543255c37 Move the HumanSize function to Logging.cxx as it is only used by the logger
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !1508
ce95b8f78 VTK-m now supports case-insensitive construction of devices from strings.
Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: Allison Vacanti <allison.vacanti@kitware.com>
Merge-request: !1502
Previously you had to exactly match the case of a device adapter's name to
construct it, which was a source of lots of problems ( OpenMP versus OPENMP, CUDA or Cuda ).
Now `vtkm::cont::make_DeviceAdapterId` and `vtkm::cont::RuntimeDeviceTracker` support
case-insensitive device construction.
The DeepCopy method is used when a ScopedGlobalRuntimeDeviceTracker
is constructed. This in turn causes the rebuilding of the device
names and states which isn't a free operation. Now we copy the already
computed information.
This was noticeable when using ArrayHandleTransform since it uses
ScopedGlobalRuntimeDeviceTracker when construction host side
portals.
7ee51f65d Adding clipping test for volumetric data
f0a342e4d Adding fix for Clip failure
Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: Matt Larsen <mlarsen@cs.uoregon.edu>
Merge-request: !1495
Previously these two functions would give compile errors when asked to
compare against an Array with a different value type. This makes it easier
to write generic code that compares virtual handles.
- Added to detect cases like bug #329https://gitlab.kitware.com/vtk/vtk-m/issues/329
- This is just to execute the clipping filter with a larger
dataset, and to ensure it can pass without failures and crashes.
19c623bfa Add changelogs for ArrayHandleVirtual and VariantArrayHandle
3445047f9 Refactor vtkm::cont::ArrayHandleAny into vtkm::cont::ArrayHandleVirtual
7a5e32be7 Update VTKmCompilerFlags to suppress stack-size-warnings on CUDA 9+
bef70820c Update new worklets to work with ArrayHandleVariant
1f2abbc9c vtkm::cont::IsType and vtkm::cont::Cast support VariantArrayHandle
acf825b27 Correct IsType and Cast on ArrayHandleVirtual to work on OSX.
7b9fa975f Rename: IsVirtualType to IsValueType.
deb4946a4 Make sure vtk-m libraries under CUDA 8 are always built statically
...
Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: Kenneth Moreland <kmorel@sandia.gov>
Merge-request: !1454
ArrayHandleVirtual can automatically be constructed from any ArrayHandle.
In the cases where the input ArrayHandle doesn't derived from ArrayHandleVirtual,
it will automatically construct StorageAny to hold the array.
