VTK-m merge requestshttps://gitlab.kitware.com/vtk/vtk-m/-/merge_requests2019-12-22T01:26:10-05:00https://gitlab.kitware.com/vtk/vtk-m/-/merge_requests/1747Particle status rename2019-12-22T01:26:10-05:00Dave PugmireParticle status renamecreate a new status for the integrator
make the particle status more succinct.create a new status for the integrator
make the particle status more succinct.https://gitlab.kitware.com/vtk/vtk-m/-/merge_requests/1924Disable timer for devices that fail at runtime2019-12-12T09:52:28-05:00Kenneth MorelandDisable timer for devices that fail at runtimePreviously the timer would attempt to call the device-specific
implementation of any device compiled for regardless of what the
`RuntimeDeviceTracker` says or if it fails. This caused problems when a
particular device (such as CUDA) was ...Previously the timer would attempt to call the device-specific
implementation of any device compiled for regardless of what the
`RuntimeDeviceTracker` says or if it fails. This caused problems when a
particular device (such as CUDA) was compiled for but run in a system
where the runtime was not available.
Fix this problem by (1) first checking to see if the device is enabled
in the `RuntimeDeviceTracker` before running and (2) if an exception is
thrown catch it and disable the device in the `RuntimeDeviceTracker`.https://gitlab.kitware.com/vtk/vtk-m/-/merge_requests/1806Provide faster compile times2019-10-16T09:44:42-04:00Robert MaynardProvide faster compile timesThis work is designed to improve compile times of worklet unit tests. If we are happy with this I can do the same for filter Unit Tests.
Some of this work is similar to https://gitlab.kitware.com/vtk/vtk-m/merge_requests/1804 as I have...This work is designed to improve compile times of worklet unit tests. If we are happy with this I can do the same for filter Unit Tests.
Some of this work is similar to https://gitlab.kitware.com/vtk/vtk-m/merge_requests/1804 as I have built a single Tangle implementation for all worklet unit tests, I can rebase my changes on the `vtkm/source` work once it is finished.
The importance of this work is to improve wall time of parallel builds. In the first screenshot we see a parallel build of
everything needed to build `UnitTests_vtkm_worklet_testing` with both `CUDA` and `OpenMP` enabled.
![Screenshot_from_2019-08-23_10-25-05](/uploads/8e3d8ea8577ec631d85f71cc5d0650e8/Screenshot_from_2019-08-23_10-25-05.png)
In the second screenshot we see the improved wall time after these changes ( about 130 secs of wall time ).![Screenshot_from_2019-08-23_10-31-43](/uploads/b6432826146c596213f4b123e1c6a6b6/Screenshot_from_2019-08-23_10-31-43.png)https://gitlab.kitware.com/vtk/vtk-m/-/merge_requests/1878Infer execution signature2019-10-07T17:05:42-04:00Robert MaynardInfer execution signaturehttps://gitlab.kitware.com/vtk/vtk-m/-/merge_requests/1869Log information about entering and leaving device scope2019-09-30T16:13:16-04:00Kenneth MorelandLog information about entering and leaving device scopeI was running some rendering examples and I was surprised to
see some log messages stating that my device was being forced
to Serial. Panicked, I opened up a debugger and set a breakpoint
where the device was forced to Serial. Turns out,...I was running some rendering examples and I was surprised to
see some log messages stating that my device was being forced
to Serial. Panicked, I opened up a debugger and set a breakpoint
where the device was forced to Serial. Turns out, the device
was forced to Serial inside of a `ScopedRuntimeDeviceTracker`
(as part of the `ColorTable` operation). However, the log
gave no indication that the default devices were restored.
To prevent further misunderstandings for myself and others,
added some log messages to the `ScopedRuntimeDeviceTracker`
to write when the scope is entered and left at the same logging
level as that of the announcement that the device is forced.https://gitlab.kitware.com/vtk/vtk-m/-/merge_requests/1858WIP: Test Don't Merge2019-09-18T13:58:14-04:00Kenneth MorelandWIP: Test Don't Mergehttps://gitlab.kitware.com/vtk/vtk-m/-/merge_requests/1773Refactor MakeTestDataSet into a separate library2019-08-23T17:18:09-04:00Robert MaynardRefactor MakeTestDataSet into a separate libraryInstead of having every test generate the functions inside this
massive file, build them only once.
Build times for clean build with just OpenMP:
- master: 7:55sec
- this: 7:37secInstead of having every test generate the functions inside this
massive file, build them only once.
Build times for clean build with just OpenMP:
- master: 7:55sec
- this: 7:37sechttps://gitlab.kitware.com/vtk/vtk-m/-/merge_requests/1798Update diy to fix warnings2019-08-22T09:28:57-04:00Sujin PhilipUpdate diy to fix warningsSujin PhilipSujin Philiphttps://gitlab.kitware.com/vtk/vtk-m/-/merge_requests/1783Add changelog for CreateResult changes2019-08-20T10:06:12-04:00Robert MaynardAdd changelog for CreateResult changeshttps://gitlab.kitware.com/vtk/vtk-m/-/merge_requests/1598Rename filter to RemoveGhostZone.2019-08-16T16:43:37-04:00Dave PugmireRename filter to RemoveGhostZone.Rename the GhostZone to RemoveGhostZoneRename the GhostZone to RemoveGhostZonehttps://gitlab.kitware.com/vtk/vtk-m/-/merge_requests/1555Make an OpenGL interop library2019-08-15T11:54:49-04:00Kenneth MorelandMake an OpenGL interop libraryIt has been a while since anyone has really touched the interop library.
These changes add a vtkm-interop library that encapsulates all of the
code to transfer arrays from VTK-m to OpenGL. The one function,
TransferToOpenGL now takes a V...It has been a while since anyone has really touched the interop library.
These changes add a vtkm-interop library that encapsulates all of the
code to transfer arrays from VTK-m to OpenGL. The one function,
TransferToOpenGL now takes a VariantArrayHandle that passes the array
through a library boundary.
The interop library also no longer relies on the VTK-m render library.
Chances are if someone is using OpenGL interop they are using their own
rendering code.https://gitlab.kitware.com/vtk/vtk-m/-/merge_requests/1119WIP: Vectorization2019-08-15T11:53:59-04:00Ben NewtonWIP: VectorizationChanges in support of allowing vtk-m to vectorize (on appropriate hardward avx2, avx512, etc) the execution of the worklets. Currently a work in progress.Changes in support of allowing vtk-m to vectorize (on appropriate hardward avx2, avx512, etc) the execution of the worklets. Currently a work in progress.Kenneth MorelandKenneth Morelandhttps://gitlab.kitware.com/vtk/vtk-m/-/merge_requests/1534WIP Add build time check for ninja builds.2019-08-15T11:46:21-04:00Allison Vacantialliepiper16@gmail.comWIP Add build time check for ninja builds.https://gitlab.kitware.com/vtk/vtk-m/-/merge_requests/1438WIP: Update color table presets2019-08-15T11:46:07-04:00Kenneth MorelandWIP: Update color table presetsAllows the importing and exporting of color tables through
JSON files. Also converts the presets to use this
infrastructure and updates the presets.Allows the importing and exporting of color tables through
JSON files. Also converts the presets to use this
infrastructure and updates the presets.https://gitlab.kitware.com/vtk/vtk-m/-/merge_requests/968Support copying subsets of permutation arrays to devices2019-08-15T11:46:02-04:00Kenneth MorelandSupport copying subsets of permutation arrays to devicesPreviously, ArrayHandlePermutation moved data to devices (for the
execution environment) by copying the entire source arrays and using a
special array portal in the execution environment to extract from the
appropriate location on the fl...Previously, ArrayHandlePermutation moved data to devices (for the
execution environment) by copying the entire source arrays and using a
special array portal in the execution environment to extract from the
appropriate location on the fly.
That is still the default behavior, but now there is an alternate mode
where instead of preparing the source array for the execution
environment, it uses the ArrayManagerExecution to copy the subset of
data exposed in the permutation to the execution environment. It
implements this by disabling the specialized ArrayTransfer and using the
default one.https://gitlab.kitware.com/vtk/vtk-m/-/merge_requests/1289WIP: Pointlocator22019-08-15T11:45:57-04:00Li-Ta LoWIP: Pointlocator2This revision of PointLocatorUniforGrid cause ptas to run into infinite loop. This MR is an attempt for the CI to try compile for all the supported platform.This revision of PointLocatorUniforGrid cause ptas to run into infinite loop. This MR is an attempt for the CI to try compile for all the supported platform.https://gitlab.kitware.com/vtk/vtk-m/-/merge_requests/1385WIP: Pointlocator32019-08-15T11:45:49-04:00Li-Ta LoWIP: Pointlocator3A test to reproduce infinite loop while compiling execution side of PointLocator.A test to reproduce infinite loop while compiling execution side of PointLocator.https://gitlab.kitware.com/vtk/vtk-m/-/merge_requests/918WIP: Slic reduction2019-08-15T11:45:45-04:00Sebastien JourdainWIP: Slic reductionTrying to work out the compilation issue... ;-)Trying to work out the compilation issue... ;-)David ThompsonDavid Thompsonhttps://gitlab.kitware.com/vtk/vtk-m/-/merge_requests/1746WIP: Changing Uniform and Rectilinear Grid Locators to be able to work with 2...2019-08-06T13:13:33-04:00Abhishek Yenpureabhi.yenpure@kitware.comWIP: Changing Uniform and Rectilinear Grid Locators to be able to work with 2D datasets, and particle advection fixes- Changing structured locators to work with 2D grids
- Changing CellInterpolationHelpers in particle advection for locator changes
- Adding fix for particle advection bug of shooting particles which are closer to the boundary- Changing structured locators to work with 2D grids
- Changing CellInterpolationHelpers in particle advection for locator changes
- Adding fix for particle advection bug of shooting particles which are closer to the boundaryhttps://gitlab.kitware.com/vtk/vtk-m/-/merge_requests/1678Update diy2019-07-31T10:34:48-04:00Robert MaynardUpdate diy