Teleconference 2016-01-06

From VTKM
Revision as of 15:48, 6 January 2016 by Kmorel (talk | contribs)
Jump to navigation Jump to search

Attendees: Dave Pugmire (ORNL), Jeremy Meredith (ORNL), Berk Geveci (Kitware), Matt Larsen (LLNL), Chris Sewell (LANL)

Distributed Memory Investigation

Right now primarily interested in Legion integration. LANL is going to pursue that. There is already a Thrust-Legion example, which suggests that there is a good chance of doing something successful.

Dashboard status

From Rob Maynard: Chuck Atkins is going to start managing the dashboards for the project this month, so we should see an increase in stability once the transition is complete.

Copyright Assertion

We need to do a DOE copyright assertion for the V1.0 release of VTK-m. To do this, we need a list of people who have contributed to VTK-m to sign off on it. Berk has volunteered to get someone to go through the git repository for all commits since February 2015 and see who has committed anything.

Point coordinates for rectilinear grids

Dave Pugmire is working on various data set builders. For the rectilinear grid data set builder, he needs to use a special array called ArrayHandleCartesianProduct to represent the point coordinates. This array can be added to the dynamic array handle just fine, but once it is there worklet operations on the array cannot cast it back to the appropriate type. The solution is simple enough: add this array's storage type to the list of storage objects used in DynamicArrayHandleCoordinateSystem. The downside to doing this is that every invocation of a worklet using a coordinate system will add a code path for this type whether it is used or not.

The solution we came to was to add ArrayHandleCartesianProduct as one of the default storage types for coordinate systems, but only for a single floating point type (specifically vtkm::FloatDefault). The DataSetBuilderRectilinear will have to convert incoming arrays to arrays of that type if necessary.

Version 1.0 ToDo List