1.2.0 is our third official release. This release is stable and should compile
across many platforms. However, note that VTK-m is still under heavy development
and each release contains backward-incompatible changes.

Sujin Philip authored Mar 30, 2018 and Kitware Robot committed Mar 30, 2018

cd69e712

 Fix Unified Memory example

Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: Utkarsh Ayachit <utkarsh.ayachit@kitware.com>
Merge-request: !1126

Robert Maynard authored Mar 30, 2018 and Kitware Robot committed Mar 30, 2018

82163375

 Correct windows compile issues with ColorTable

Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !1128

Robert Maynard authored Mar 30, 2018 and Kitware Robot committed Mar 30, 2018

79d922ee

 Add a filter that uses ColorTable to color any field from a dataset.

Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !1124

Robert Maynard authored Mar 30, 2018 and Kitware Robot committed Mar 30, 2018

c9026870

 CoordinateSystem now links with FloatDefault == 64

Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !1127

Kenneth Moreland authored Mar 29, 2018 and Kitware Robot committed Mar 29, 2018

90b925ba

 Fix off-by-one-overrun of color table map array

Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: Robert Maynard <robert.maynard@kitware.com>
Merge-request: !1125

Update to use the new filter interface

The display of a color bar in an OpenGL canvas had an array overrun.
This method first used ColorTable to create an array of colors. It then
used the array to look up values for polygons that make up the color
bar. However, each polygon used indices i and i+1, and on the last value
the i+1 looked pass the end of the array. This fixes the problem by
adding one more value to the color array generated.

Utkarsh Ayachit authored Mar 29, 2018 and Kitware Robot committed Mar 29, 2018

396f70ed

 remove shadow methods (fixes #210)

Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: Kenneth Moreland <kmorel@sandia.gov>
Merge-request: !1123

Robert Maynard authored Mar 28, 2018 and Kitware Robot committed Mar 28, 2018

944bc3c0

 Introduce vtkm::cont::ColorTable replacing vtkm::rendering::ColorTable

Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !1103

The new and improved vtkm::cont::ColorTable provides a more feature complete
color table implementation that is modeled after
vtkDiscretizableColorTransferFunction. This class therefore supports different
color spaces ( rgb, lab, hsv, diverging ) and supports execution across all
device adapters.

Utkarsh Ayachit authored Mar 26, 2018 and Kitware Robot committed Mar 26, 2018

0208cd76

 fix example after filters API change.

Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: Kenneth Moreland <kmorel@sandia.gov>
Merge-request: !1122

Kenneth Moreland authored Mar 26, 2018 and Kitware Robot committed Mar 26, 2018

fa842725 Enable using coordinates for dot/cross product filters
707eccd3

 Make dot/cross filter interface more consistent

Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: Dave Pugmire <dpugmire@gmail.com>
Merge-request: !1121

Also better supporting policies on secondary field.

Both the dot product filter and the cross product filter require 2
fields to be selected as their input. Previously, you used the
superclass' SetActiveField for the primary field and
SetSecondaryFieldName for the secondary field. This changes adds a
SetPrimaryField method to make the selection more clear. I also changed
SetSecondaryFieldName to SetSecondaryField that optionally takes an
association to make it more consistent.

Kenneth Moreland authored Mar 23, 2018 and Kitware Robot committed Mar 23, 2018

1fe78692

 Resurrect function to get face indices

Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: Robert Maynard <robert.maynard@kitware.com>
Merge-request: !1120

Robert Maynard authored Mar 23, 2018 and Kitware Robot committed Mar 23, 2018

2bfbf0a9

 Transfer of virtuals to the CUDA device now properly uses streams

Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: Sujin Philip <sujin.philip@kitware.com>
Merge-request: !1114

Due to recent changes to remove static arrays that are not supported on
some devices, the function to return all the local point indices on a
face was removed. That left no way to get the structure of cell faces
short of pulling an internal data structure.

This change resurrects a function to get point indices for a face. The
interface for this method has necessarily changed, so I also changed the
corresponding function for getting edge indices.

Kenneth Moreland authored Mar 22, 2018 and Kitware Robot committed Mar 22, 2018

86f6ecbf Add some convenience methods for Filter::SetFieldsToPass
f8237a9d

 Make selection of fields to pass a field member variable

Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: Utkarsh Ayachit <utkarsh.ayachit@kitware.com>
Merge-request: !1118

The first convenience method takes a FieldSelection and a mode. The mode
given will override the mode in the FieldSelection. The intention is to
make it easy to give the constructor argument for FieldSelection and the
mode. For example, if you wanted to pass all variables _except_
"stopfield", you could say

field.SetFieldsToPass("stopfield",
                      vtkm::filter::FieldSelection::MODE_EXCLUDE);

I also added a convenience method that takes the name of a field and an
association.

field.SetFieldsToPass("pointfield",
                      vtkm::cont::Field::ASSOC_POINTS);

Granted, you could get the same effect by wrapping this arguments in
initializer braces, but this is a bit more clear.

Previously you passed a FieldSelection to Filter::Execute to specify
which fields to pass from input to output. There is no real reason for
this as other information about input and output fields are member
variables to Filter. This moves field selection as a member variable as
well. (This should also help confusion when updating old code to new to
prevent users from mistaking field passing with input fields.

Also added a few convenience constructors to FieldSelection so that you
can call Field::SetFieldsToPass() with just the string of what you want
to pass.

Kenneth Moreland authored Mar 22, 2018 and Kitware Robot committed Mar 22, 2018

d74b96ba Support FieldSelection initialization with vtkm::Pair initializer list
8e312f81 Add MODE_EXCLUDE to FieldSelection
9c51de8d Add MODE_NONE to FieldSelection
a4aa42c0 Avoid "weird" arrays in fields
6a6ac7cd

 Change filter to pass all fields by default

Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !1116

It already supported initializer lists of std::pair. It seems weird we
would not also support our own version of pair.

This allows you to turn off the selection of fields rather than turn
them on. It could be helpful, for example, if you were isosurfacing on a
single isovalue and didn't want to pass the field you are contouring on
(because it's all the same value).

This mode forces the selection to be empty. Although there is no
practical difference between having MODE_NONE and having MODE_SELECTED
with nothing selected (which is the default), this is a semantically
nicer way to say you don't want any fields.

Since we have changed the default behavior of Filter::Execute to be
MODE_ALL, this is a nice addition so that you can clearly specify you
don't want to pass any fields by adding
vtkm::filter::FieldSelection::MODE_NONE as the second argument. (Making
it MODE_SELECTED is not clear that you want none.)

In some of the tests there was a field that was using a counting array.
This uses an integer as the value type and has a special implicit
storage type. Currently, this is likely to cause problems whenever it
runs into a cast and call of a dynamic array. For now, let's avoid
these.

In the near future we should have expanded virtual method capabilities
that will make it possible to support these atypical arrays.

You can still select independent fields with a FieldSelection object if
desired.

Kenneth Moreland authored Mar 21, 2018 and Kitware Robot committed Mar 21, 2018

117ce0be

 Add const correctness to MultiBlock method arguments

Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !1115

Several MultiBlock methods take references as arguments. Generally that
is good as some of the arguments take larger data structures like
DataSet and std::vector that can be passed much faster as a reference.
However, the references were not declared const, which means that you
could not use rvalues. This is now fixed.

This way when multiple threads are using VTK-m they all won't block while
one transfer a class with virtuals to the device.

Robert Maynard authored Mar 14, 2018 and Kitware Robot committed Mar 14, 2018

e3961b9c update examples after filter API changes.
9cf5be2f

 Make `Result` constructor as `explicit`.

Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !1112

This avoid accidental conversions from DataSet to Result in return
values. This exposed several issues with filters and their tests. Fixed
those as well.

Robert Maynard authored Mar 13, 2018 and Kitware Robot committed Mar 13, 2018

cbadd3e6

 Make CoordinateSystem not fail on CUDA

Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: Kenneth Moreland <kmorel@sandia.gov>
Acked-by: Matt Larsen <mlarsen@cs.uoregon.edu>
Merge-request: !1108

Fix diy warnings

See merge request !1110