1. 16 Jan, 2019 1 commit
  2. 27 Dec, 2018 1 commit
  3. 05 Jun, 2018 1 commit
  4. 10 Mar, 2018 1 commit
  5. 30 Jan, 2018 1 commit
    • luz.paz's avatar
      Misc. typos · 80b11afa
      luz.paz authored
      Found via `codespell -q 3` via downstream VTK
      80b11afa
  6. 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
      accordingly.
      c3a3184d
  7. 10 Aug, 2017 1 commit
  8. 26 May, 2017 1 commit
  9. 25 May, 2017 1 commit
  10. 18 May, 2017 1 commit
  11. 15 Feb, 2017 1 commit
  12. 19 Oct, 2016 1 commit
  13. 24 Aug, 2016 1 commit
    • Kenneth Moreland's avatar
      Replace TryAllTypes with trying exemplar tests · f8442903
      Kenneth Moreland authored
      There were many tests that created code paths for every base and Vec
      type that VTK-m supports (up to 4 components). Although this is
      admirable, it is also excessive, and our compile times for the tests are
      very long.
      
      To shorten compile times, remove the TryAllTypes method. Replace it with
      a version of TryTypes that uses a default list of "exemplar" set of
      integers, floats, and Vecs.
      f8442903
  14. 15 Jun, 2016 1 commit
    • Robert Maynard's avatar
      Obey VisualStudio checked iterator levels, and NULL checked iterators · 1e19101e
      Robert Maynard authored
      When compiling under VisualStudio we need to first determine if checked
      iterators are enabled ( _ITERATOR_DEBUG_LEVEL ). We don't want to use the
      NDEBUG key, as we could be inside a project that is in Debug mode with
      disabled checked iterators.
      
      Secondly if they are enabled we need to handle the use case of NULL iterators
      that get advanced by length zero. This last case is valid, but isn't supported
      by the checked iterators so we need to work around it
      1e19101e
  15. 17 Mar, 2016 1 commit
  16. 25 Aug, 2015 1 commit
    • Kenneth Moreland's avatar
      Remove PointCoordinates classes · 91db8ad0
      Kenneth Moreland authored
      The idea of the PointCoordinate classes was to make it easier to define
      new special types of point coordinate arrays. But ultimately you have to
      create an array handle type, and the CoordinateSystem class pretty much
      handles everything else for you. Thus, these classes where being used
      nowhere.
      91db8ad0
  17. 27 Jul, 2015 1 commit
    • Kenneth Moreland's avatar
      Created DynamicCellSet · 6b68666d
      Kenneth Moreland authored
      The DynamicCellSet will be used in place of the pointer to a CellSet
      in a DataSet. This will prevent us from having to cast it all the time
      and also remove reliance on boost smart_ptr.
      6b68666d
  18. 08 Jul, 2015 1 commit
    • Kenneth Moreland's avatar
      Add data size introspection to DynamicArrayHandle. · a7a8248c
      Kenneth Moreland authored
      Sometimes it is useful to know how big an array held in a
      DynamicArrayHandle is. This adds two methods to DynamicArrayHandle:
      GetNumberOfValues and GetNumberOfComponents. They allow you to query the
      size of the array without having to statically cast to the array itself.
      a7a8248c
  19. 21 May, 2015 1 commit
  20. 07 May, 2015 1 commit
    • Kenneth Moreland's avatar
      Fix issues with warnings about data loss from type conversion · 66aa10aa
      Kenneth Moreland authored
      Fix compile warnings that come up with the flags
      
        -Wconversion -Wno-sign-conversion
      
      This catches several instances (mostly in the testing framework) where
      types are implicitly converted. I expect these changes to fix some of
      the warnings we are seeing in MSVC.
      
      I was going to add these flags to the list of extra warning flags, but
      unfortunately the Thrust library has several warnings of these types,
      and I don't know a good way to turn on the warnings for our code but
      turn them off for Thrust.
      66aa10aa
  21. 30 Apr, 2015 2 commits
    • Kenneth Moreland's avatar
      Change storage references to storage pointers. · e14fc427
      Kenneth Moreland authored
      Previously ArrayTransfer and ArrayManagerExecution received a reference
      to a Storage class in their constructor and held the reference as an
      ivar. In retrospect, this is just asking for trouble. First, it is way
      too easy to pass by value when you mean to pass by reference. Second, if
      there ever is a bug where the Storage goes out of scope before the
      classes holding a reference, it is that much harder to debug.
      e14fc427
    • 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.
      ec0adf8b
  22. 28 Apr, 2015 1 commit
  23. 16 Jan, 2015 1 commit
    • Kenneth Moreland's avatar
      Add index tags to FunctionInterface features. · 37dac920
      Kenneth Moreland authored
      The functors in the ForEach, StaticTransform, and DynamicTransform
      methods sometimes can use the index of the parameter that they are
      operating on. This can be a helpful diagnostic in compile and run-time
      errors. It is also helpful when linking parameters from one
      FunctionInterface with those of another.
      
      This new features are now replacing implementations using the Zip
      functionality that was removed earlier. The implementation is actually
      simplified a bit.
      37dac920
  24. 21 Oct, 2014 1 commit
    • Kenneth Moreland's avatar
      Fix MSVC compiler warnings · 7cf25331
      Kenneth Moreland authored
      Generally, the MSVC compiler tends to be more picky about implicit type
      conversions. It warns if there is any possibility of precision loss.
      7cf25331
  25. 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.
      7f94eafc
  26. 08 Oct, 2014 2 commits
  27. 09 Sep, 2014 1 commit
    • Kenneth Moreland's avatar
      Properly check "raw" iterators in MSVC. · 904f5821
      Kenneth Moreland authored
      For MSVC we use the non-portable wrapper stdext::checked_array_iterators
      because the compiler insists on it for safety. When we check to make sure
      our templates are giving us raw pointers, we have to check for this wrapper
      instead of the raw pointer itself.
      904f5821
  28. 08 Sep, 2014 1 commit
  29. 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
      change.
      
      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
      ArrayExecutionManager.
      
      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
      data.
      
      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.
      21823500
  30. 11 Jun, 2014 1 commit
    • Kenneth Moreland's avatar
      Remove CopyInto method from array-support classes · a789d54e
      Kenneth Moreland authored
      It was originally put there to support CopyInto in ArrayHandle, but that
      has already been removed. It really only makes sense for trivial
      examples and testing code, and it sometimes causes complications with
      coding.
      a789d54e
  31. 19 May, 2014 1 commit
  32. 15 May, 2014 1 commit
    • Kenneth Moreland's avatar
      Add classes to manage point coordinates. · 7d769a8f
      Kenneth Moreland authored
      Each type of point coordinates has its own class with the name
      PointCoordinates*. Currently there is a PointCoordiantesArray that contains
      an ArrayHandle holding the point coordinates and a PointCoordinatesUniform
      that takes the standard extent, origin, and spacing for a uniform rectilinear
      grid and defines point coordiantes for that. Creating new PointCoordinates
      arrays is pretty easy, and we will almost definitely add more. For example,
      we should have an elevation version that takes uniform coordinates for
      a 2D grid and then an elevation in the third dimension. We can probably
      also use a basic composite point coordinates that can build them from
      other coordinates.
      
      There is also a DynamicPointCoordinates class that polymorphically stores
      an instance of a PointCoordinates class. It has a CastAndCall method that
      behaves like DynamicArrayHandle; it can call a functor with an array handle
      (possible implicit) that holds the point coordinates.
      7d769a8f
  33. 30 Apr, 2014 1 commit
    • Kenneth Moreland's avatar
      Add DynamicTransform class. · dac47ee5
      Kenneth Moreland authored
      This is used with the FunctionInterface::DynamicTransformCont method to
      convert a call of arguments using dynamic array handles to a function
      templated on concrete types.
      dac47ee5
  34. 11 Feb, 2014 2 commits
  35. 10 Feb, 2014 1 commit