1. 22 Apr, 2019 1 commit
    • Robert Maynard's avatar
      For VTK-m libs all includes of DeviceAdapterTagCuda happen from cuda files · ff687016
      Robert Maynard authored
      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.
      ff687016
  2. 17 Apr, 2019 1 commit
  3. 15 Apr, 2019 1 commit
  4. 10 Apr, 2019 3 commits
  5. 09 Apr, 2019 1 commit
  6. 05 Apr, 2019 1 commit
  7. 04 Apr, 2019 1 commit
  8. 03 Apr, 2019 2 commits
  9. 01 Apr, 2019 3 commits
  10. 28 Mar, 2019 1 commit
  11. 18 Mar, 2019 1 commit
  12. 14 Mar, 2019 4 commits
  13. 13 Mar, 2019 1 commit
  14. 25 Feb, 2019 1 commit
    • Kenneth Moreland's avatar
      Add Mask capabilities to worklets · 191d6e55
      Kenneth Moreland authored
      Mask objects allow you to specify which output values should be
      generated when a worklet is run. That is, the Mask allows you to skip
      the invocation of a worklet for any number of outputs.
      191d6e55
  15. 20 Feb, 2019 1 commit
    • Kenneth Moreland's avatar
      Add specialized operators for ArrayPortalValueReference · 1ca55ac3
      Kenneth Moreland authored
      The ArrayPortalValueReference is supposed to behave just like the value
      it encapsulates and does so by automatically converting to the base type
      when necessary. However, when it is possible to convert that to
      something else, it is possible to get errors about ambiguous overloads.
      To avoid these, add specialized versions of the operators to specify
      which ones should be used.
      
      Also consolidated the CUDA version of an ArrayPortalValueReference to the
      standard one. The two implementations were equivalent and we would like
      changes to apply to both.
      1ca55ac3
  16. 01 Feb, 2019 1 commit
  17. 31 Jan, 2019 2 commits
  18. 24 Jan, 2019 2 commits
  19. 17 Jan, 2019 1 commit
  20. 16 Jan, 2019 1 commit
    • Robert Maynard's avatar
      Remove VTK-m TestBuild infrastructure · 4ec5bae0
      Robert Maynard authored
      The purpose of the TestBuild infrastructure was to confirm that
      VTK-m didn't have any lexical issues when it was a pure header
      only project. As we now move to have more compiled components
      the need for this form of testing is mitigated. Combined
      with the issue of TestBuilds causing MSVC issues, we should
      just remove this infrastructure.
      4ec5bae0
  21. 07 Jan, 2019 1 commit
  22. 06 Jan, 2019 1 commit
    • Abhishek Yenpure's avatar
      Updates to the Cell Locators · 62ee1a2c
      Abhishek Yenpure authored
      - Adding updates to uniform grid cell locator
        - adding OpenMP test, updating copyrights
      - Adding rectilinear grid cell locator
        - adding unit tests for serial, tbb, OpenMP, and cuda
      - Updating CMakeLists to honor the alphabetical ordering
      62ee1a2c
  23. 27 Dec, 2018 1 commit
  24. 21 Dec, 2018 1 commit
  25. 03 Dec, 2018 4 commits
    • Sujin Philip's avatar
      Implement extents support · 6d81bc8b
      Sujin Philip authored
      Adds a variable `GlobalPointIndexStart` to `CellSetStructured`.
      Adding this to the cell-set, instead of the coordinate system, enables this
      feature for different types of datasets like uniform grid, rectilinear, etc.,
      with this one change.
      The extents can be computed using `GlobalPointIndexStart` and `PointDimensions`.
      6d81bc8b
    • Kenneth Moreland's avatar
      Rename boundary classes · 82536092
      Kenneth Moreland authored
      Did a bit of renaming of the support classes used for
      WorkletPointNeighborhood. First, the OnBoundary tag is changed to
      Boundary to match other tags and reflect some changes in the resulting
      methods. Also moved the BoundaryState and Neighborhood classes from
      vtkm::exec::arg to vtkm::exec to be more accessible. Finally, the
      Neighborhood class name was changed to FieldNeighborhood to be more
      specific on what role this class plays with neighborhood.
      82536092
    • Kenneth Moreland's avatar
      Change neighborhood parameter from layer to radius · e008aff2
      Kenneth Moreland authored
      It was determined that the word "radius" more clearly described how the
      size of the neighborhood is determined.
      e008aff2
    • Kenneth Moreland's avatar
      Change WorkletPointNeighborhood to specify neighborhood at runtime · 01a9e854
      Kenneth Moreland authored
      Previously, WorkletPointNeighborhood had a template argument to select
      the size of the neighborhood. This change removes that template
      argument. Instead, the vtkm::exec::arg::BoundaryState methods now take
      in a size parameter when determining when it overlaps the boundary.
      
      If in the future we want to add the ability to select the neighborhood
      size at compile-time (for performance reasons), I suggest adding this
      template argument to the OnBoundary tag for ExecutionSignature.
      01a9e854
  26. 13 Nov, 2018 1 commit
    • Kenneth Moreland's avatar
      Add better queries to vtkm::exec::arg::BoundaryState · 3e3baad6
      Kenneth Moreland authored
      Previously, vtkm::exec::arg::BoundaryState only provided methods that
      said whether or not the neighborhood extened past the boundary of a
      mesh. That is fine for a 3x3x3 neighborhood, which can only extend over
      the boundary by one. However, that is problematic for larger
      neighborhoods where you may need to know how far neighborhood extends
      over the boundary.
      
      This changes allows you to query how far the neighborhood extends within
      the constrains of the boundary.
      3e3baad6
  27. 04 Oct, 2018 1 commit