The CellSetExplicit and CellSetSingleType classes have an ivar that
marks the number of points. There were several instances of code
creating cell sets without specifying the number of points. This can be
very bad if subsequent code needs that information.

Robert Maynard authored Jan 12, 2017 and Kitware Robot committed Jan 12, 2017

35585f39

 Correct a bug in tbb scan exclusive that was found using tbb 2017.
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !652

Fix warnings on GCC6.

See merge request !656

David Lonie authored Jan 11, 2017 and Kitware Robot committed Jan 11, 2017

4a9b8b6f

 Inherit std::exception in vtkm::cont::Error.
Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: Robert Maynard <robert.maynard@kitware.com>
Merge-request: !655

Robert Maynard authored Jan 11, 2017 and Kitware Robot committed Jan 11, 2017

9335e75e

 Fix casting warnings in TestingDeviceAdapter.
Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: Kenneth Moreland <kmorel@sandia.gov>
Merge-request: !659

Kenneth Moreland authored Jan 11, 2017 and Kitware Robot committed Jan 11, 2017

f23ff9fa Fix warnings about assignment operators not being generated
7ec8c034

 Remove warning about constant conditional in VTKM_ASSUME
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !657

For some reason when VTK-m was being compiled as an accelerator in VTK,
Visual Studio 2013 gave a bunch of warnings about not being able to generate
assignment operators for many classes. This happened for classes with a
const ivar that could not be automatically set. (Automatic copy constructors
are fine on this count.) I'm not sure why these warnings did not happen
when just compiling VTK-m, nor am I sure why they were generated at all as
no code actually used the copy constructors.

This commit fixes the problems by adding a private declaration for assignment
operators that cannot be automatically created. No implementation is
provided, nor should any be needed.

Robert Maynard authored Jan 10, 2017 and Kitware Robot committed Jan 10, 2017

ad28ccad

 Update the default ARRAY_SIZE in TestingDeviceAdapter.
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !653

It is common practice to swallow a semicolon in a macro using a do/
while(false) loop that only executes once. However, the Visual Studio
2013 compiler was stupidly warning about having a constant expression
for the loop. Get around the problem by creating our own swallow
semicolon macros that disable this warning as necessary.

Fixes #58.

This will expose bugs inside the tbb backend. We had to use heap allocations
for test arrays, instead of stack as the new array increases started to
cause stack overflow on windows.

Robert Maynard authored Jan 05, 2017 and Kitware Robot committed Jan 05, 2017

a339f3ac Had to rewrite tbb reduce to correct all the problems.
0120157e

 Correct tbb reduction algorithm to be correct when using multiple threads.
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !654

The previous implementation(s) didn't properly handle non identity
initial values properly.

Robert Maynard authored Jan 03, 2017 and Kitware Robot committed Jan 03, 2017

270ece24 Types and Matrix don't emit Wunused-value warnings from __builtin_expect
1052a715 ConnectivityPermuted explicitly suppress cuda host/device warnings
137dffb4

 CellSetPermutation copy constructor to suppress cuda warnings.
Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: Kenneth Moreland <kmorel@sandia.gov>
Merge-request: !651

When using Types or Matrix with the nvcc compiler with Wunused-value
enabled you would get the following warning:
(__builtin_expect(!(rowIndex < (this,NUM_ROWS)), 0)) ?
__assert_rtn(__func__, "vtkm/Matrix.h", 86, "rowIndex < this->NUM_ROWS") :
((void)0);

This is solved by changing this->NUM_ROWS to just NUM_ROWS.

Robert Maynard authored Jan 02, 2017 and Kitware Robot committed Jan 02, 2017

4a870718

 Fix a unused parameter warning in the UnitTestListTag
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !650

The class can emit false positive warnings when being compiled with
cuda but SMP backends.

Without an explicit copy constructor when cuda is used it generates a
copy constructor which is marked up as host/device and than emits warnings.

Robert Maynard authored Jan 01, 2017 and Kitware Robot committed Jan 01, 2017

c27bb01f Introduces ListTagUniversal which represents a list of everything.
9eb28841 vtkm::filter now deduces the subset of valid field types.
49c5e822

 vtkm can now find the intersection of two ListTags.
Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: Kenneth Moreland <kmorel@sandia.gov>
Merge-request: !649

This makes the FilterTraits design simpler and easier to understand.

Previously the ApplyPolicy logic was to use the filters
field set, and ignore the policy field set.

But this caused problems, as a filter couldn't express that
it was able to work on all valid types. This caused
certain complex types Vec of Vec's to fail to work properly,
and would cause compile use code paths that would never
be valid for a given policy.

This is the first step in having filters which obey both
the filters field policy and the users applied policy in
field what fields they can run on.

Robert Maynard authored Dec 29, 2016 and Kitware Robot committed Dec 29, 2016

c064e006

 The Average filters now obey the policy when casting DynamicCellSets.
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !648

Robert Maynard authored Dec 23, 2016 and Kitware Robot committed Dec 23, 2016

66fc2fa5

 PointGradients now use the proper device adapter.
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !647

Ben Boeckel authored Dec 23, 2016 and Kitware Robot committed Dec 23, 2016

b0a6b179 Add support for computing divergence to the gradient filter.
5eade282

 Restrict Gradient to scalar values and vec<3> of scalar values.
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !646

Kenneth Moreland authored Dec 21, 2016 and Kitware Robot committed Dec 21, 2016

eb0691f5 Fix example data set for marching cubes test
a5817da4 Fix cow nose data set
02bf444d Test that the array transports check the size of input arrays
9ea10317

 Add passing input domain to transport operator
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !643

It was not properly setting the number of points.

It was not properly setting the number of points.

Previously, the operator for a Transport class took the object being
transported to the execution environment and the size of the output
domain. This change also passes in the control-side argument for the
input domain. This will help check input array sizes as well as make
other potential transformations based on the input domain.

Robert Maynard authored Dec 19, 2016 and Kitware Robot committed Dec 19, 2016

75288e2d

 Correct location of VTKM_EXEC on Vorticity worklets
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !642