1. 31 May, 2018 1 commit
  2. 25 May, 2018 1 commit
  3. 24 May, 2018 1 commit
  4. 22 May, 2018 1 commit
  5. 21 May, 2018 1 commit
  6. 17 May, 2018 1 commit
  7. 16 May, 2018 1 commit
    • Allison Vacanti's avatar
      Refactor ArrayHandleCompositeVector to simplify usage and impl. · c3c8d0fd
      Allison Vacanti authored
      - Use tao::tuple instead of FunctionInterface to hold array/portal
        collections.
      - Type signatures are simplified. Now just use:
        - ArrayHandleCompositeVector<ArrayT1, ArrayT2, ...>
        - make_ArrayHandleCompositeVector(array1, array2, ...)
        instead of relying on helper structs to determine types.
      - No longer support component selection from an input array. All
        input arrays must have the same ValueType (See ArrayHandleSwizzle
        and ArrayHandleExtractComponent as the replacements for these
        usecases.
      c3c8d0fd
  8. 10 May, 2018 1 commit
  9. 08 May, 2018 1 commit
  10. 07 May, 2018 2 commits
    • Kenneth Moreland's avatar
      Fix scaling of x/y field of views · 0da55730
      Kenneth Moreland authored
      Prevously, the x field of view was computed by scaling the y field of
      view by the aspect ratio of the canvas. However, this is wrong because
      the field of view angles do not scale linearly with the aspect ratio.
      Fix this issue by using trig functions to convert the angle to distance,
      scale the distance, and then convert back to angle.
      0da55730
    • Kenneth Moreland's avatar
      Fix raytrace using wrong fov with standard camera · 39b347db
      Kenneth Moreland authored
      The raytracing code has its own version of camera that maintains two
      field of view (fov) parameters: one for the x direction and one for the
      y. The standard vtkm::rendering::Camera contains only one fov. As is
      consistent with OpenGL's gluPerspective and VTK's camera, the fov is
      specified in the y direction. However, the raytracing code was
      incorrectly using it in the x direction. That caused it to do a weird
      rescaling when the aspect ratio was not 1.
      39b347db
  11. 04 May, 2018 1 commit
  12. 03 May, 2018 4 commits
  13. 27 Apr, 2018 1 commit
    • Kenneth Moreland's avatar
      Move Scatter from Worklet to Dispatcher · edc4c85f
      Kenneth Moreland authored
      Previously, when a Worklet needed a scatter, the scatter object was
      stored in the Worklet object. That was problematic because that means
      the Scatter, which is a control object, was shoved into the execution
      environment.
      
      To prevent that, move the Scatter into the Dispatcher object. The
      worklet still declares a ScatterType alias, but no longer has a
      GetScatter method. Instead, the Dispatcher now takes a Scatter object in
      its constructor. If using the default scatter (ScatterIdentity), the
      default constructor is used. If using another type of Scatter that
      requires data to set up its state, then the caller of the worklet needs
      to provide that to the dispatcher. For convenience, worklets are
      encouraged to have a MakeScatter method to help construct a proper
      scatter object.
      edc4c85f
  14. 25 Apr, 2018 2 commits
  15. 24 Apr, 2018 2 commits
  16. 10 Apr, 2018 1 commit
  17. 09 Apr, 2018 2 commits
  18. 03 Apr, 2018 1 commit
  19. 02 Apr, 2018 4 commits
  20. 29 Mar, 2018 1 commit
    • Kenneth Moreland's avatar
      Fix off-by-one-overrun of color table map array · 90b925ba
      Kenneth Moreland authored
      The display of a color bar in an OpenGL canvas had an array overrun.
      This method first used ColorTable to create an array of colors. It then
      used the array to look up values for polygons that make up the color
      bar. However, each polygon used indices i and i+1, and on the last value
      the i+1 looked pass the end of the array. This fixes the problem by
      adding one more value to the color array generated.
      90b925ba
  21. 28 Mar, 2018 1 commit
    • Robert Maynard's avatar
      Introduce vtkm::cont::ColorTable replacing vtkm::rendering::ColorTable · 944bc3c0
      Robert Maynard authored
      The new and improved vtkm::cont::ColorTable provides a more feature complete
      color table implementation that is modeled after
      vtkDiscretizableColorTransferFunction. This class therefore supports different
      color spaces ( rgb, lab, hsv, diverging ) and supports execution across all
      device adapters.
      944bc3c0
  22. 23 Mar, 2018 1 commit
    • Kenneth Moreland's avatar
      Resurrect function to get face indices · 1fe78692
      Kenneth Moreland authored
      Due to recent changes to remove static arrays that are not supported on
      some devices, the function to return all the local point indices on a
      face was removed. That left no way to get the structure of cell faces
      short of pulling an internal data structure.
      
      This change resurrects a function to get point indices for a face. The
      interface for this method has necessarily changed, so I also changed the
      corresponding function for getting edge indices.
      1fe78692
  23. 21 Mar, 2018 1 commit
  24. 13 Mar, 2018 1 commit
  25. 10 Mar, 2018 2 commits
  26. 26 Feb, 2018 1 commit
  27. 23 Feb, 2018 1 commit
  28. 12 Feb, 2018 1 commit
  29. 09 Feb, 2018 1 commit