1. 01 Jul, 2020 11 commits
  2. 30 Jun, 2020 1 commit
  3. 29 Jun, 2020 3 commits
  4. 25 Jun, 2020 6 commits
    • Kenneth Moreland's avatar
      Work around known bug in LagrangianFilter · 8e1c87b5
      Kenneth Moreland authored
      The implementation of LagrangianFilter uses some `ArrayHandle`s
      declared as `static` in the .hxx header file. One of the bad
      consequences of this is that there is no control over when the
      arrays are freed. We have seen where these arrays get freed
      after the CUDA system is closed, which causes nasty things to
      happen as the program closes.
      
      This works around the problem until a fix is implemnted.
      8e1c87b5
    • Kenneth Moreland's avatar
      Pin user provided memory in ArrayHandle · a47fd42b
      Kenneth Moreland authored
      Often when a user gives memory to an `ArrayHandle`, she wants data to be
      written into the memory given to be used elsewhere. Previously, the
      `Buffer` objects would delete the given buffer as soon as a write buffer
      was created elsewhere. That was a problem if a user wants VTK-m to write
      results right into a given buffer.
      
      Instead, when a user provides memory, "pin" that memory so that the
      `ArrayHandle` never deletes it.
      a47fd42b
    • Kenneth Moreland's avatar
      Replace basic ArrayHandle implementation to use Buffers · 56bec1dd
      Kenneth Moreland authored
      This encapsulates a lot of the required memory management into the
      Buffer object and related code.
      
      Many now unneeded classes were deleted.
      56bec1dd
    • Kenneth Moreland's avatar
      Add Buffer class · 8f7b0d18
      Kenneth Moreland authored
      The buffer class encapsulates the movement of raw C arrays between
      host and devices.
      
      The `Buffer` class itself is not associated with any device. Instead,
      `Buffer` is used in conjunction with a new templated class named
      `DeviceAdapterMemoryManager` that can allocate data on a given
      device and transfer data as necessary. `DeviceAdapterMemoryManager`
      will eventually replace the more complicated device adapter classes
      that manage data on a device.
      
      The code in `DeviceAdapterMemoryManager` is actually enclosed in
      virtual methods. This allows us to limit the number of classes that
      need to be compiled for a device. Rather, the implementation of
      `DeviceAdapterMemoryManager` is compiled once with whatever compiler
      is necessary, and then the `RuntimeDeviceInformation` is used to
      get the correct object instance.
      8f7b0d18
    • Li-Ta Lo's avatar
      Merge topic 'standard_normal' · a338612e
      Li-Ta Lo authored
      365b1bb2 use make_ArrayHandleZip
      980c4864 Merge branch 'master' into standard_normal
      2aea7534 Add ArrayHandleRandomStandardNormal
      Acked-by: Kitware Robot's avatarKitware Robot <kwrobot@kitware.com>
      Acked-by: Robert Maynard's avatarRobert Maynard <robert.maynard@kitware.com>
      Merge-request: !2150
      a338612e
    • Li-Ta Lo's avatar
      use make_ArrayHandleZip · 365b1bb2
      Li-Ta Lo authored
      365b1bb2
  5. 24 Jun, 2020 6 commits
  6. 23 Jun, 2020 2 commits
  7. 22 Jun, 2020 6 commits
  8. 19 Jun, 2020 5 commits