1. 05 Jun, 2018 1 commit
  2. 22 May, 2018 1 commit
  3. 12 Apr, 2018 1 commit
    • Utkarsh Ayachit's avatar
      Filter API enhancements. · 0af0271f
      Utkarsh Ayachit authored
      This revamps Filter API to improve support for multiblock dataset and
      distributed use-cases. Filters now operate on MultiBlock alone thus
      `Filter::Execute(MultiBlock&)` is the primary method.
      `Filter::Execute(DataSet*)` is only provided as an convenience that
      internally puts the dataset into a MultiBlock and calls the primary
      method.
      
      Subclasses can provides PreExecute and PostExecute overrides to handle
      init/reduction operations for filters with operating on multiple blocks.
      Since blocks can be distributed, filters are expected to handle that as
      well.
      
      Subclasses can provide `PrepareForExecution(MultiBlock*..)` to customize
      behavior for handling multiblock inputs. Default is to simply loop
      over blocks.
      0af0271f
  4. 03 Apr, 2018 1 commit
    • Utkarsh Ayachit's avatar
      Remove `vtkm::filter::Result` · 3da8b5be
      Utkarsh Ayachit authored
      This commit removes `vtkm::filter::Result`. All methods that used
      `vtkm::filter::Result` simply change to use `vtkm::cont::Dataset` instead.
      The utility API on `Result` that was used to add fields to the resulting
      dataset is now available via `vtkm::filter::internal::CreateResult`.
      3da8b5be
  5. 02 Apr, 2018 2 commits
    • Utkarsh Ayachit's avatar
      Make `MapFieldOntoOutput` private API. · eda68a6f
      Utkarsh Ayachit authored
      MapFieldOntoOutput is no longer public API. Since `vtkm::cont::Filter`
      invokes it when appropriate, we no longer need to keep it public.
      
      Also removes the overload of MapFieldOntoOutput that doesn't take
      policy. That is no longer needed since vtkm::cont::Filter always can
      provide the current policy being used.
      eda68a6f
    • Utkarsh Ayachit's avatar
      fix `Derived` type propagation in filter inheritance. · dc474eb4
      Utkarsh Ayachit authored
      Filter subclasses were not passing the true derived type up the
      hierarchy. Fixed that.
      dc474eb4
  6. 07 Mar, 2018 1 commit
    • Utkarsh Ayachit's avatar
      enhance filter API · de4e840e
      Utkarsh Ayachit authored
      Filters now support executing on a dataset to produce a result dataset
      with automatic mapping of fields to the output dataset. Fields to map
      can be selected using `vtkm::filter::FieldSelection` class, which provides
      constructors to map all or no fields, along with a selection of fields.
      
      This updates all tests to use the new filter API.
      de4e840e
  7. 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
  8. 12 Sep, 2017 1 commit
    • Kenneth Moreland's avatar
      Make Get/SetActiveCellSetIndex method names match in filter · 0dd1e7ae
      Kenneth Moreland authored
      The filter classes have an internal CellSetIndex member that tracks on
      which cell set to operate on. The get accessor is called
      GetActiveCellSetIndex (note the descriptive "Index" at the end of the
      function name). However, the set accessor was called SetActiveCellSet
      (sans "Index"). This discrepancy does not make a lot of sense.
      
      This commit changes SetActiveCellSet to SetActiveCellSetIndex. Not only
      do I like the extra descriptor (in case we later want to set cells by
      name), it is also used much less than the get method so is less
      disruptive.
      0dd1e7ae
  9. 11 Aug, 2017 1 commit
  10. 26 May, 2017 1 commit
  11. 25 May, 2017 1 commit
  12. 18 May, 2017 1 commit
  13. 23 Feb, 2017 1 commit
    • Kenneth Moreland's avatar
      Update classes using RuntimeDeviceTracker · 18c4190d
      Kenneth Moreland authored
      They now grab the global runtime device tracker. In some cases, I've
      added the ability to set/get the tracker to change it from the global.
      In others I just removed the local copy, since it was just hooked into
      the global tracker.
      18c4190d
  14. 22 Feb, 2017 1 commit
    • Kenneth Moreland's avatar
      Move RuntimeDeviceTracker to vtkm::cont · b9d3206e
      Kenneth Moreland authored
      Before it was in the vtkm::cont::internal namespace. However, we expect
      to be using this feature quite a bit more as we want VTK-m to handle
      multiple devices effectively (as in, just figure it out and go).
      b9d3206e
  15. 16 Nov, 2016 1 commit
    • Kenneth Moreland's avatar
      Remove exports for header-only functions/methods · fdaccc22
      Kenneth Moreland authored
      Change the VTKM_CONT_EXPORT to VTKM_CONT. (Likewise for EXEC and
      EXEC_CONT.) Remove the inline from these macros so that they can be
      applied to everything, including implementations in a library.
      
      Because inline is not declared in these modifies, you have to add the
      keyword to functions and methods where the implementation is not inlined
      in the class.
      fdaccc22
  16. 17 Aug, 2016 1 commit
    • Kenneth Moreland's avatar
      Use general TryExecute for filter execution · e488967c
      Kenneth Moreland authored
      The TryExecute function was based off of the ResolveFieldTypeAnd*
      classes made for filters. To reduce the amount of code duplication,
      modify these two filter classes to use the more general TryExecute
      functionality.
      e488967c
  17. 05 May, 2016 2 commits
    • Kenneth Moreland's avatar
      Give result classes their own header file. · f4362a49
      Kenneth Moreland authored
      VTK-m style guidelines dictate that all classes part of the API should
      be in their own header file. Thus, we have moved the result classes out
      of the filter header files and into their own headers.
      
      We have also renamed these clases to ResultField and ResultDataSet to
      better match the class naming conventions of VTK-m.
      
      Since we are moving around these result classes, we have also revamped
      their structure. They are now in a hierarchy with a common ResultBase
      class. Additionally, all result classes have a reference to a complete
      DataSet that can be considered the output of the filter. This will make
      it easier for users to consistently deal with filter results.
      
      These changes cover issues #60 and #62.
      f4362a49
    • Kenneth Moreland's avatar
      Rename filter base classes to follow VTK-m naming convention · e8d3eda8
      Kenneth Moreland authored
      The base classes for all the filters are named with 'Filter' at the end.
      Generally the convention in VTK-m is to place the most general
      descriptor (in this case Filter) first, which makes it easier to find
      items in ordered lists.
      
      This commit resolves issue #59.
      e8d3eda8
  18. 07 Apr, 2016 1 commit
  19. 14 Mar, 2016 1 commit