- 12 Apr, 2018 1 commit
-
-
Robert Maynard authored
Previously we only printed out the error numbers on MSVC.
-
- 10 Apr, 2018 3 commits
-
-
James Kress authored
a79b4c2f Removing move command to remove warnings. e19e61f1 Merge branch 'rendering-label-leak' of https://gitlab.kitware.com/jameskress/vtk-m into rendering-label-leak 02a67d64 Merge remote-tracking branch 'upstream/master' into rendering-label-leak 3bab4087 Adding delete and assignment oeprators to annotations. e3ccd7f8 Adding previous cmake fix. 9f32bbe0 Merge branch 'rendering-label-leak' of https://gitlab.kitware.com/jameskress/vtk-m into rendering-label-leak 7906e89e Updating leak fix to use uniq_ptr. b92c4801 Update CMakeLists.txt ... Acked-by:
Kitware Robot <kwrobot@kitware.com> Acked-by:
Robert Maynard <robert.maynard@kitware.com> Merge-request: !1131
-
James Kress authored
-
Robert Maynard authored
d7ce601c To allow compiled in virtuals we need to only build for actual sm archs. Acked-by:
Kitware Robot <kwrobot@kitware.com> Merge-request: !1146
-
- 09 Apr, 2018 13 commits
-
-
Robert Maynard authored
a37a3f39 Examples that use glu functions now properly link to OpenGL::GLU a44ad273 Make sure Rendering example doesn't conflict with rendering testing name Acked-by:
Kitware Robot <kwrobot@kitware.com> Acked-by:
Utkarsh Ayachit <utkarsh.ayachit@kitware.com> Merge-request: !1147
-
Robert Maynard authored
-
Robert Maynard authored
-
James Kress authored
Merge branch 'rendering-label-leak' of https://gitlab.kitware.com/jameskress/vtk-m into rendering-label-leak
-
James Kress authored
-
James Kress authored
-
James Kress authored
-
Robert Maynard authored
c6dcbc1f Check for git version only once f2f8796d Properly install all required cmake files needed by vtk-m b658a72a Fix broken VTK-m PyExpander functin Acked-by:
Kitware Robot <kwrobot@kitware.com> Merge-request: !1144
-
Kenneth Moreland authored
The check to determine the version of VTK-m from git was duplicated in CMakeLists.txt. Although pointless, it generally was not a big deal (only an extra check when running CMake). Except for some reason with the latest changes to the CMake build the second time find_package(Git) was called on my system the GIT_EXECUTABLE variable got cleared out and that caused the configure to fail. I have no idea why this happens (and running CMake again seems to fix the problem), but simply removing the extraneous find seems fix the problem.
-
Robert Maynard authored
CUDA currently doesn't support building for `compute_` and having compiled in virtuals ( using separable compilation ). So we need to transition everything over to `sm_`
-
Robert Maynard authored
-
Robert Maynard authored
Fixes #216
-
Robert Maynard authored
86c487e6 Properly clean up ColorTable's memory. Acked-by:
Kitware Robot <kwrobot@kitware.com> Acked-by:
Kenneth Moreland <kmorel@sandia.gov> Acked-by:
James Kress <james@jameskress.com> Merge-request: !1141
-
- 06 Apr, 2018 1 commit
-
-
Matt Larsen authored
efdf8543 Misc. Typos Acked-by:
Kitware Robot <kwrobot@kitware.com> Acked-by:
Matt Larsen <mlarsen@cs.uoregon.edu> Merge-request: !1113
-
- 05 Apr, 2018 14 commits
-
-
Utkarsh Ayachit authored
6938b05c Remove GetBounds methods from MultiBlock. c4970604 Add `BoundsCompute` and `BoundsGlobalCompute` f966a362 Remove MultiBlock::GetGlobalNumberOfBlocks. f37e6425 Remove `MultiBlock::GetGlobalRange` API. 20a052f4 add FieldRangeCompute. 50bfb1d2 Add utility to serialize ArrayHandles for DIY. Acked-by:
Kitware Robot <kwrobot@kitware.com> Acked-by:
Kenneth Moreland <kmorel@sandia.gov> Merge-request: !1142
-
Utkarsh Ayachit authored
Removing GetBounds and related methods from MultiBlock. These have been replaced by BoundsCompute and BoundsGlobalCompute.
-
Utkarsh Ayachit authored
Adding compute function to compute local and global bounds for datasets and multiblocks alike.
-
Utkarsh Ayachit authored
Removing another API that need not be on MultiBlock. There's generally no need for apps to know this. If needed, we can add `...Compute` function. This removes another API on MultiBlock that could trigger parallel communication/synchronization.
-
Utkarsh Ayachit authored
Removing MultiBlock::GetGlobalRange API to keep things consistent with DataSet API. Instead, one should use `FieldRangeCompute` or `FieldRangeGlobalCompute` as appropriate.
-
Utkarsh Ayachit authored
-
Utkarsh Ayachit authored
-
Robert Maynard authored
-
Robert Maynard authored
8472b64e Suppress more CUDA host function from a host/device function warnings cd333bf8 Remove unneeded semicolon after closing parentheses on a some methods. 84311a24 Merge branch 'master' into cmake_refactor 83b360f1 vtkm::Lerp now casts integer types to an appropriate scalar type. 0d45c5cf Correct warnings found after disabling all warning when CUDA is enabled. 8808b41f Merge branch 'master' into vtk-m-cmake_refactor d205f953 Update the documentation on when we need CMake 3.9+ e630ac5a Merge branch 'master' into vtk-m-cmake_refactor ... Acked-by:
Kitware Robot <kwrobot@kitware.com> Acked-by:
Kenneth Moreland <kmorel@sandia.gov> Merge-request: !1135
-
Kenneth Moreland authored
3dd66e85 Do not use __assume for icc in gcc compatability mode Acked-by:
Kitware Robot <kwrobot@kitware.com> Acked-by:
Robert Maynard <robert.maynard@kitware.com> Merge-request: !1139
-
Robert Maynard authored
-
Robert Maynard authored
-
Robert Maynard authored
-
Robert Maynard authored
c1237969 VTK-m ArrayHandle can now take ownership of a user allocated memory location 707970f4 VTK-m StorageBasic is now able to give/take ownership of user allocated memory. Acked-by:
Kitware Robot <kwrobot@kitware.com> Acked-by:
Kenneth Moreland <kmorel@sandia.gov> Merge-request: !1137
-
- 04 Apr, 2018 5 commits
-
-
Kenneth Moreland authored
When using the GNU header files on a system, the icc compiler emulates the behavior of the gcc compiler on the system. (See https:// software.intel.com/en-us/node/522750) This appears to mean that icc features that are not available in gcc could get turned off. In particular, we found that the __assume feature stopped working. To get around this problem, do not use __assume when compiling with icc and __GNUC__ is defined. Instead, use the available gcc features.
-
Robert Maynard authored
Previously memory that was allocated outside of VTK-m was impossible to transfer to VTK-m as we didn't know how to free it. By extending the ArrayHandle constructors to support a Storage object that is being moved, we can clearly express that the ArrayHandle now owns memory it didn't allocate. Here is an example of how this is done: ```cpp T* buffer = new T[100]; auto user_free_function = [](void* ptr) { delete[] static_cast<T*>(ptr); }; vtkm::cont::internal::Storage<T, vtkm::cont::StorageTagBasic> storage(buffer, 100, user_free_function); vtkm::cont::ArrayHandle<T> arrayHandle(std::move(storage)); ```
-
Robert Maynard authored
This fixes the three following issues with StorageBasic. 1. Memory that was allocated by VTK-m and Stolen by the user needed the proper free function called which is generally StorageBasicAllocator::deallocate. But that was hard for the user to hold onto. So now we provide a function pointer to the correct free function. 2. Memory that was allocated outside of VTK-m was impossible to transfer to VTK-m as we didn't know how to free it. This is now resolved by allowing the user to specify a free function to be called on release. 3. When the CUDA backend allocates memory for an ArrayHandle that has no control representation, and the location we are running on supports concurrent managed access we want to specify that cuda managed memory as also the host memory. This requires that StorageBasic be able to call an arbitrary new delete function which is chosen at runtime.
-
Robert Maynard authored
Previously types such as vtkm::Id or vtkm::U/Int32 would be cast to whatever the weight type was. This is problematic as they should actually be casted to a double type as the weight type could be a float and therefore the results
-
Robert Maynard authored
-
- 03 Apr, 2018 3 commits
-
-
Utkarsh Ayachit authored
3da8b5be Remove `vtkm::filter::Result` cebe6820 add `vtkm::cont::ErrorFilterExecution` 68d43a61 Demo: fix `filter::Execute` API usage. ff94622c fix README.md based on changes to Filter API. Acked-by:
Kitware Robot <kwrobot@kitware.com> Acked-by:
Kenneth Moreland <kmorel@sandia.gov> Merge-request: !1136
-
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`.
-
Utkarsh Ayachit authored
Adding a new exception type `vtkm::cont::ErrorFilterExecution`. Unlike existing exceptions, when thrown in `TryExecute`, this exception causes the call to not attempt to execute on any other devices and let it be thrown so that the application can catch it.
-