1. 05 Jun, 2018 1 commit
  2. 20 Sep, 2017 1 commit
    • Kenneth Moreland's avatar
      Update copyright for Sandia · c3a3184d
      Kenneth Moreland authored
      Sandia National Laboratories recently changed management from the
      Sandia Corporation to the National Technology & Engineering Solutions
      of Sandia, LLC (NTESS). The copyright statements need to be updated
  3. 11 Aug, 2017 1 commit
    • Sujin Philip's avatar
      Streamline CellSetExplicit · 4e1b026c
      Sujin Philip authored
      1) Don't require a DeviceAdapter for the BuildConnectivity function (#131)
      2) Explicitly instantiate default CellSetExplicit and CellSetSingleType
  4. 29 Jun, 2017 1 commit
    • David C. Lonie's avatar
      Refactor array transfer logic for basic storage. · b2c3e416
      David C. Lonie authored
      The old templated array transfer mechanism generated a lot of code
      that ended up doing a simple, type-agnostic memcpy for most devices.
      This patch specialized array handles for basic storage and uses a
      fast-path array transfer implementation. This reduces the size of the
      vtkm_cont library by 27% on gcc (from 6.2MB to 4.5MB).
  5. 25 May, 2017 1 commit
  6. 05 Apr, 2017 2 commits
  7. 26 Jan, 2017 1 commit
    • Kenneth Moreland's avatar
      Add Version.h header file · a6719638
      Kenneth Moreland authored
      This allows source files to use the VTK-m version.
      Note that Configure.h does not include the version. This is intentional.
      First, I don't want the entirety of VTK-m to recompile every time the
      version is updated (which is every time a commit happens in git).
      Second, it is important that external project source files be able to
      get the VTK-m version without actually loading any VTK-m code.
  8. 22 Aug, 2016 1 commit
    • Robert Maynard's avatar
      Examples now call find_package(VTKm) · 88ce3f23
      Robert Maynard authored
      The examples are now written so they can be copied out of the vtk-m
      source and still build properly. This will help new users / developers
      learn how to build projects that use VTK-m.
  9. 19 Jul, 2016 1 commit
  10. 01 Apr, 2016 1 commit
  11. 15 Sep, 2015 1 commit
  12. 25 Jun, 2015 1 commit
  13. 05 Jun, 2015 1 commit
    • Robert Maynard's avatar
      Redesign StorageBasic to allow modification of user provided memory. · b43fb01f
      Robert Maynard authored
      The driving desire for this change was to make vtk-m ArrayHandle behave more
      like the standard vector. The canonical example of what we want to support is:
      std::vector<vtkm::Id> values;
      vtkm::cont::ArrayHandle<vtkm::Id> array = vtkm::cont::make_ArrayHandle(values);
      And with-out the ability to modify user provided memory, this was impossible.
  14. 21 May, 2015 1 commit
  15. 28 Apr, 2015 1 commit
    • Kenneth Moreland's avatar
      Remove UserPortal from ArrayHandle. · a2c28099
      Kenneth Moreland authored
      The UserPortal in ArrayHandle was used to copy a pointer the user
      created into an ArrayHandle to use in VTK-m algorithms. However, this is
      only really valid for a basic storage, so the functionality has been
      moved there, and you have to construct an ArrayHandle with a storage
      instead of an array portal.
  16. 10 Feb, 2015 1 commit
    • Kenneth Moreland's avatar
      Expose allocation in ArrayHandle. · 6141e83b
      Kenneth Moreland authored
      Add an Allocate method in ArrayHandle that basically forwards the
      alllocate request to the storage object. This allows some measure of
      control of the array from the control side. You can allocate the array
      and set values (by getting the control array portal) if you so desire.
  17. 09 Feb, 2015 1 commit
    • Kenneth Moreland's avatar
      Make ArrayHandle work better when uninitialized · c224c2b9
      Kenneth Moreland authored
      Fixed a problem where ArrayHandle would cause a crash if you tried to
      get the control portal on an uninitialized array (it was supposed to
      throw an exception).
      Also changed some methods in ArrayHandle so that they work resonably
      without error when used with an uninitialized array. Specifically, the
      aforementioned behavior was changed to "allocate" an array of size 0
      (that is, call Allocate(0) on the storage object) to return an empty
      array portal rather than throw an error. Although this use of
      ArrayHandle can be considered erroneous, it is convenient the get an
      empty array portal when dealing with a potentially unallocated array
      rather than create a special condition.
  18. 28 Jan, 2015 1 commit
  19. 14 Oct, 2014 1 commit
    • Kenneth Moreland's avatar
      Unify test values. · 10ba2efb
      Kenneth Moreland authored
      Lots of tests have to move values in and out of arrays and check them
      against expected values. It is also often the case that these tests are
      run on lots of different types. There is some repeated code for
      generating known values for particular indices. This change unifies some
      of that. This can probably also encourage making more generic tests.
  20. 09 Oct, 2014 1 commit
    • Kenneth Moreland's avatar
      Remove vtkm::Scalar and vtkm::Vector# types · 7f94eafc
      Kenneth Moreland authored
      Providing these types tends to "lock in" the precision of the algorithms
      used in VTK-m. Since we are using templating anyway, our templates
      should be generic enough to handle difference precision in the data.
      Usually the appropriate type can be determined by the data provided. In
      the case where there is no hint on the precision of data to use (for
      example, in the code that provides coordinates for uniform data), there
      is a vtkm::FloatDefault.
  21. 08 Sep, 2014 1 commit
  22. 12 Aug, 2014 1 commit
  23. 24 Jun, 2014 1 commit
    • Kenneth Moreland's avatar
      Change ArrayContainerControl to Storage. · 21823500
      Kenneth Moreland authored
      After a talk with Robert Maynard, we decided to change the name
      ArrayContainerControl to Storage. There are several reasons for this
      1. The name ArrayContainerControl is unwieldy. It is long, hard for
      humans to parse, and makes for long lines and wraparound. It is also
      hard to distinguish from other names like ArrayHandleFoo and
      2. The word container is getting overloaded. For example, there is a
      SimplePolymorphicContainer. Container is being used for an object that
      literally acts like a container for data. This class really manages
      3. The data does not necessarily have to be on the control side.
      Implicit containers store the data nowhere. Derivative containers might
      have all the real data on the execution side. It is possible in the
      future to have storage on the execution environment instead of the
      control (think interfacing with a simulator on the GPU).
      Storage is not a perfect word (what does implicit storage really mean?),
      but its the best English word we came up with.
  24. 11 Feb, 2014 1 commit
  25. 10 Feb, 2014 1 commit