GitLab

63c931e6 Correct location of ThrustPatches which clang formatter moved
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !1653

6fafcf01 correct compile issues caused by clang formatting.
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !1655

A couple of tests require vtkm/testing/Testing to be the first include

90dd8a0e Correct clang formatting in Math.h.in
Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: Robert Maynard <robert.maynard@kitware.com>
Merge-request: !1654

There is a small section in the code generated from Math.h.in that is
subject to clang formatting. A recent change reformatted that bit of
Math.h, so we need to update Math.h.in accordingly.

ff687016 For VTK-m libs all includes of DeviceAdapterTagCuda happen from cuda files
Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: Kenneth Moreland <kmorel@sandia.gov>
Merge-request: !1648

030b03e4 Remove unneeded diy build include directory
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !1652

The diy build configured files are all located by the include
from the root vtkm include directory, so this include isn't needed

It is very easy to cause ODR violations with DeviceAdapterTagCuda.
If you include that header from a C++ file and a CUDA file inside
the same program we an ODR violation. The reasons is that the C++
versions will say the tag is invalid, and the CUDA will say the
tag is valid.

The solution to this is that any compilation unit that includes
DeviceAdapterTagCuda from a version of VTK-m that has CUDA enabled
must be invoked by the cuda compiler.

13ef17ea Remove thread_local from RuntimeDeviceNames
Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: Kenneth Moreland <kmorel@sandia.gov>
Merge-request: !1650

Older Mac compilers that are still supported by VTK don't support
`thread_local`.

d8cc067c Remove DeviceAdapterError as it isn't needed any more.
Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: Kenneth Moreland <kmorel@sandia.gov>
Merge-request: !1649

Fixes #277

DeviceAdapterError existed to make sure that the default device adapter
template was being handled properly. Since the default device adapter doesn't
exist, and nothing is templated over it we can now remove DeviceAdapterError.

21c84798 FieldIn/Out/InOut documentation updated to fact they aren't templated
Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: Kenneth Moreland <kmorel@sandia.gov>
Merge-request: !1647

Fixes #366

5a26051f benchmarking cmake code simplified
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !1646

9c292007 UnitTestBoundingIntervalHierarchy handles systems under load better
671c1df5 Timer logs the proper device name when called with an invalid device
d3d66a33 GameOfLife example always uses the proper device adapter
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !1645

The UnitTestBoundingIntervalHierarchy has historically had problems
when the machine is already under-load when the algorithm is executed.
By limiting the number of openMP threads the test uses we can
reduce the amount of CPU time slicing that this test causes.

Previously the example would only time using the serial device
adapter, which wouldn't work when the user explicitly specified
a device on the command line.

df5765bd update LICENSE.txt file
6d9c2af7 remove warning in file due to non-reference exception catch
fbcea82e conslidate the license statement
fd59fd1d Print error in copyright only on first mis-match
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !1609

047b6465 VTK-m now provides better scheduling parameters controls
Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: Kenneth Moreland <kmorel@sandia.gov>
Merge-request: !1643

VTK-m now offers a more GPU aware set of defaults for kernel scheduling.
When VTK-m first launches a kernel we do system introspection and determine
what GPU's are on the machine and than match this information to a preset
table of values. The implementation is designed in a way that allows for
VTK-m to offer both specific presets for a given GPU ( V100 ) or for
an entire generation of cards ( Pascal ).

Currently VTK-m offers preset tables for the following GPU's:
- Tesla V100
- Tesla P100

If the hardware doesn't match a specific GPU card we than try to find the
nearest know hardware generation and use those defaults. Currently we offer
defaults for
- Older than Pascal Hardware
- Pascal Hardware
- Volta+ Hardware

Some users have workloads that don't align with the defaults provided by
VTK-m. When that is the cause, it is possible to override the defaults
by binding a custom function to `vtkm::cont::cuda::InitScheduleParameters`.
As shown below:

```cpp
  ScheduleParameters CustomScheduleValues(char const* name,
                                          int major,
                                          int minor,
                                          int multiProcessorCount,
                                          int maxThreadsPerMultiProcessor,
                                          int maxThreadsPerBlock)
  {

    ScheduleParameters params  {
        64 * multiProcessorCount,  //1d blocks
        64,                        //1d threads per block
        64 * multiProcessorCount,  //2d blocks
        { 8, 8, 1 },               //2d threads per block
        64 * multiProcessorCount,  //3d blocks
        { 4, 4, 4 } };             //3d threads per block
    return params;
  }
  vtkm::cont::cuda::InitScheduleParameters(&CustomScheduleValues);
```

ff30684c Removes the default device macros from VTK-m
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !1641

Fixes #116

e54cbe85 contourtree_augmented doesn't call abort in VTK-m worklets
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !1642

71018e3b Always export vtkm_cuda no matter VTKm_INSTALL_ONLY_LIBRARIES
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !1640

661fb64d AtomicInterfaceControl functions are marked with VTKM_SUPPRESS_EXEC_WARNINGS
0c70f9b9 Add BitFieldIn/Out/InOut worklet signature tags.
a66510e8 Add ArrayHandleBitField, a boolean-valued AH backed by a BitField.
56cc5c3d Add support for BitFields.
d01b9738 Allow VTKM_SUPPRESS_EXEC_WARNINGS to be used inside macros.
2f2ca937 Add bit operations FindFirstSetBit and CountSetBits to Math.h.
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !1629

46843ff4 CellSetExplicit has no dependency on default vtk-m device
Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: Kenneth Moreland <kmorel@sandia.gov>
Merge-request: !1636

These provide an appropriate BitPortal for use in worklets.