1. 31 May, 2018 1 commit
  2. 30 May, 2018 2 commits
  3. 29 May, 2018 5 commits
  4. 25 May, 2018 1 commit
  5. 24 May, 2018 1 commit
  6. 23 May, 2018 1 commit
  7. 22 May, 2018 1 commit
  8. 21 May, 2018 1 commit
  9. 18 May, 2018 4 commits
  10. 17 May, 2018 3 commits
  11. 16 May, 2018 9 commits
  12. 15 May, 2018 6 commits
    • ayenpure's avatar
      Fixing header guard warning · bc405366
      ayenpure authored
    • ayenpure's avatar
      Fix errors missed/introduced in previous commit. · b39ee80b
      ayenpure authored
      - Missed a ',' to seperate template argument in GridEvaluator
      - Adding initialization of params to Integrators for RK4
      - Fixing ExecutionBaseObject changes for Particles
    • ayenpure's avatar
      Fixing merge mess for particle advection · 24dd0638
      ayenpure authored
      Adding Utkarsh's changes from 86bd81de to Rectilinear grid as well
       - To make rectilinear grids work with any storage type
      Adding Rob's changes from 7d6fe568 to the RK4Integrator
       - Previously the RK4Integrator could compute velocity with uninitialized inputs.
      Adding Rob's changes from a6bf830f to ParticleAdvection
       - Previous ParticleAdvection would dispatch some of the worklets on the default device adapter
         and not the explicitly requested device adapter
      Adding Ken's change from 0753131a
       - For supporting all the previous merge conflicts with the new ExecutionObjectBase change.
    • Haocheng LIU's avatar
      Make vtkm:Math Pi() operations constexpr · 2e62d78b
      Haocheng LIU authored
      If they are used inside other mathematical expressions then the compiler
      has a better chance to perform the operation at compile time.
    • Allison Vacanti's avatar
    • Robert Maynard's avatar
      Re-implement DeviceAdapterRuntimeDetector to avoid ODR violations. · e28244f3
      Robert Maynard authored
      The previous implementation of DeviceAdapterRuntimeDetector caused
      multiple differing definitions of the same class to exist and
      was causing the runtime device tracker to report CUDA as disabled
      when it actually was enabled.
      The ODR was caused by having a default implementation for
      DeviceAdapterRuntimeDetector and a specific specialization for
      CUDA. If a library had both CUDA and C++ sources it would pick up
      both implementations and would have undefined behavior. In general
      it would think the CUDA backend was disabled.
      To avoid this kind of situation in the future I have reworked VTK-m
      so that each device adapter must implement DeviceAdapterRuntimeDetector
      for that device.
  13. 11 May, 2018 1 commit
  14. 10 May, 2018 2 commits
    • Kenneth Moreland's avatar
      Replace ExecutionObjectFactoryBase with ExecutionObjectBase · 0753131a
      Kenneth Moreland authored
      While making changes to how execution objects work, we had agreed to
      name the base object ExecutionObjectBase instead of its original name of
      ExecutionObjectFactoryBase. Somehow that change did not make it through.
    • Robert Maynard's avatar
      CUDA's RuntimeDeviceTracker and Timer are now built as part of vtkm_cont · 571556d9
      Robert Maynard authored
      This is done to not only reduce the amount of code that users need
      to generate but to reduce the amount of errors when using
      the RuntimeDeviceTracker. If the runtime device tracker is initially
      used in a library by a c++ file it will never properly detect the
      cuda backend. By moving the code into vtkm_cont we can make sure
      this problem doesn't occur.
  15. 09 May, 2018 2 commits