1. 04 Oct, 2019 1 commit
  2. 03 Oct, 2019 1 commit
    • Robert Maynard's avatar
      ExecutionSignatures are now optional for simple worklets · 5b403f9d
      Robert Maynard authored
      If a worklet doesn't explicitly state an ExecutionSignature, VTK-m
      assumes the worklet has no return value, and each ControlSignature
      argument is passed to the worklet in the same order.
      
      For example if we had this worklet:
      ```cxx
      struct DotProduct : public vtkm::worklet::WorkletMapField
      {
        using ControlSignature = void(FieldIn, FieldIn, FieldOut);
        using ExecutionSignature = void(_1, _2, _3);
      
        template <typename T, vtkm::IdComponent Size>
        VTKM_EXEC void operator()(const vtkm::Vec<T, Size>& v1,
                                  const vtkm::Vec<T, Size>& v2,
                                  T& outValue) const
        {
          outValue = vtkm::Dot(v1, v2);
        }
      };
      ```
      
      It can be simplified to be:
      
      ```cxx
      struct DotProduct : public vtkm::worklet::WorkletMapField
      {
        using ControlSignature = void(FieldIn, FieldIn, FieldOut);
      
        template <typename T, vtkm::IdComponent Size>
        VTKM_EXEC void operator()(const vtkm::Vec<T, Size>& v1,
                                  const vtkm::Vec<T, Size>& v2,
                                  T& outValue) const
        {
          outValue = vtkm::Dot(v1, v2);
        }
      };
      5b403f9d
  3. 02 Oct, 2019 4 commits
  4. 01 Oct, 2019 2 commits
  5. 30 Sep, 2019 4 commits
    • Kenneth Moreland's avatar
      Update logging for enabled devices · 2ca37707
      Kenneth Moreland authored
      The previous implementation of `RuntimeDeviceTracker` occasionally
      outputted a log at level `Info` about devices being enabled or disabled.
      The problem was that the information given was inconsistent (so it would
      sometimes announce one change but not announce a different corrective
      change). This could cause weird confusions. For example, when you used a
      `ColorTable`, it would use a `ScopedRuntimeDeviceTracker` to temporarily
      force the device to `Serial`. The log will just tell you that the device
      was forced to `Serial` but never tell you that the devices where
      restored to include actual parallel devices.
      
      This change helps correct these with the following changes:
      
      * Added a new log level, `DevicesEnabled`, that is a higher level than
        `Info`. All logging from `RuntimeDeviceTracker` goes to this log
        level.
      * Change the logging output of `RuntimeDeviceTracker` to output a list
        of currently enabled devices whenever a change happens. That way you
        don't have to guess what happend for each change.
      * Change `ScopedRuntimeDeviceTracker` to log whenever the scope is
        entered or left.
      2ca37707
    • Allison Vacanti's avatar
      Refactor CellSetExplicit to remove NumIndices. · 3886b7df
      Allison Vacanti authored
      See #408 for details.
      3886b7df
    • Robert Maynard's avatar
      Merge topic 'mask_supported_by_invoker' · 0ca60236
      Robert Maynard authored and Kitware Robot's avatar Kitware Robot committed
      445e4d81
      
       vtkm::cont::Invoker supports both Masks and Scatter
      Acked-by: Kitware Robot's avatarKitware Robot <kwrobot@kitware.com>
      Acked-by: Kenneth Moreland's avatarKenneth Moreland <kmorel@sandia.gov>
      Merge-request: !1876
      0ca60236
    • Robert Maynard's avatar
      CellSetConnectivity now inherits from FilterDataSet · 25fb666d
      Robert Maynard authored
      Fixes #409
      25fb666d
  6. 29 Sep, 2019 3 commits
  7. 27 Sep, 2019 9 commits
  8. 26 Sep, 2019 4 commits
  9. 25 Sep, 2019 4 commits
  10. 24 Sep, 2019 8 commits