1. 29 May, 2016 1 commit
  2. 04 Nov, 2015 1 commit
  3. 30 Oct, 2015 1 commit
  4. 22 Jul, 2015 1 commit
  5. 25 Jun, 2015 2 commits
  6. 28 May, 2015 1 commit
  7. 21 May, 2015 1 commit
  8. 05 May, 2015 1 commit
  9. 30 Apr, 2015 1 commit
    • Kenneth Moreland's avatar
      Change interface of ArrayTransfer to be more like ArrayHandle. · ec0adf8b
      Kenneth Moreland authored
      This includes changing methods like LoadDataForInput to PrepareForInput.
      It also changed the interface a bit to save a reference to the storage
      object. (Maybe it would be better to save a pointer?) These changes also
      extend up to the ArrayManagerExecution class, so it can effect device
      adapter implementations.
  10. 20 Jan, 2015 1 commit
    • Robert Maynard's avatar
      Fix multiple issue in the cuda array handle unit tests. · 04bc41ca
      Robert Maynard authored
      The namespaces need to be different for each test, or else only the first
      implementation of the function will be used for all tests that call that
      Also updated the test to verify that we can count starting from a non zero
  11. 19 Dec, 2014 1 commit
    • Robert Maynard's avatar
      Adding a cuda device adapter to vtkm. · d9270e40
      Robert Maynard authored
      Porting the dax device adapter over to vtkm. Unlike the dax version, doesn't
      use the thrust::device_vector, but instead uses thrust::system calls so that
      we can support multiple thrust based backends.
      Also this has Texture Memory support for input array handles. Some more work
      will need to be done to ArrayHandle so that everything works when using an
      ArrayHandle inplace with texture memory bindings.