1. 30 Nov, 2017 13 commits
  2. 29 Nov, 2017 11 commits
  3. 28 Nov, 2017 12 commits
  4. 27 Nov, 2017 4 commits
    • Kenneth Moreland's avatar
      Remove direct usage of VTK-m in LOD test · 9ccf982a
      Kenneth Moreland authored
      The direct use of VTK-m was to switch the device being used.
      TODO: add a means of specifying the device a VTK-m filter in
      vtkAcceleratorsVTKm should use without directly interfacing with VTK-m.
    • Kenneth Moreland's avatar
      Remove references to VTK-m header files from VTK filters · ec591255
      Kenneth Moreland authored
      For better encapsulation (and simplification of the build), do not
      expose VTK-m code itself from the vtkAcceleratorsVTKm package.
    • Kenneth Moreland's avatar
      Remove VTK-m includes and libs from test compile · ea855589
      Kenneth Moreland authored
      All the VTK-m include and libraries should be hidden from code outward
      facing of the vtkAcceleratorsVTKm library. Besides, the VTK-m
      accelerator tests are not called as a subdirectory from the
      vtkAcceleratorsVTKm code, so the CMake variables specifying the include
      directories and libraries are not set.
      If it is later decided that code using the accelerators library also
      needs to directly compile VTK-m code, it should be specified as PUBLIC
      includes and libraries to the vtkAcceleratorsVTKm library.
    • Allison Vacanti's avatar
      Add a minimum ghost level option to D3. · 50b777ce
      Allison Vacanti authored