Before, the rtImageTest test driver script would set VTK_DATA_ROOT
as a global variable before running the test scripts. But it's
better for the scripts to set it themselves, so that they can be
run without rtImageTest.
`vtkCallbackTokens` are now returned by `Push` and the new
`PushDependent` method. They
embed a `std::shared_future` which allows to synchronize code in the
main thread depending on whether certain functions have been executed or
not.
`PushDependent` takes as input, in addition to the function and parameters,
a container of tokens. The pushed function through this method will only
execute when the functions associated with the tokens have all
terminated.
Currently, the thread taking charge of a function that needs to wait
before being executed just call the `wait()` method of the future. There
could be a smarter way to do that by having multiple queues depending on
the readiness of functions.
9d88c0d119 vtkContour3DLinearGrid: Set selected array as active scalars
d5d492b8a5 vtkContour3DLinearGrid: Don't promote arrays to float
8945162b33 vtkCellDataToPointData: Remove leftover from old MR.
Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: buildbot <buildbot@kitware.com>
Reviewed-by: Cory Quammen <cory.quammen@kitware.com>
Merge-request: !9850
A few Python tests were still using utilities from vtkTclTest2Py,
such as 'catch', 'info', 'file', 'lindex', 'expr', or they were
expecting named colors in the global namespace.
Per PEP 561, the presence of a py.typed file indicates that there
is type information (the .pyi files) for the Python VTK modules.
The pyi files aren't perfect, so YMMV when you use them for static
analysis of your VTK programs.
6e618a1a9c Add dev note for update-python-tests
47360cd8f3 Update utility Python scripts for vtkmodules
519316fe11 Update the Python tests for remaining modules
19a7d11768 Update the Python tests in Interaction
61e9d6730f Update the Python tests in Rendering
9286f1885d Update the Python tests in IO
53c9d0bc96 Update the Python tests in Imaging
2098c26a73 Update the Python tests in Filters
...
Acked-by: Kitware Robot <kwrobot@kitware.com>
Tested-by: buildbot <buildbot@kitware.com>
Reviewed-by: Ben Boeckel <ben.boeckel@kitware.com>
Merge-request: !9830
The internal controller doesn't have to be its own type. By overloading
`vtkThreadedCallbackQueue::New` we are able to instanciate it correctly.
The few lambdas in the `.cxx` file can also capture parameters. It
simplifies the code slightly.
The view rendered in the CAVE was coupled to the desktop camera,
requiring CAVE users to move the desktop camera to the origin,
and then not touch it again, or it would affect the view seen
in the CAVE views. This change decouples the camera transform
from the view transform when in off-axis mode to fix that problem.
The lighting of objects was broken in the CAVE. In the best
case, the light seemed to come from the opposite side it should
have (try turning off the light kit and adding a single directional
light before this change). By placing the eye offset into the
view transform in off-axis mode, objects are now lit on the
correct side.
Clipping was broken in the CAVE so that sometimes rendered objects
would disappear from one CAVE screen before the others. The
problem was worse when viewing CAVE displays from more oblique
angles. This changes fixes that problem by adding (or subtracting)
the size of the screen in world coordinates to the far (or near)
clipping planes.
GPU volume rendering under CAVE head tracking was broken as well,
as the camera position (and not the eye position) was used as
the starting point for tracing rays. This change fixes that by
using the eye point instead, when in off-axis mode.
bddd94efd3 Improve OpenVR/OpenXR module and test and enable OpenXR in CI
Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: buildbot <buildbot@kitware.com>
Merge-request: !9791
07ee8e07c0 add changelog for SizeAverageCellToPoint in OpenFOAMReader
4da4069d55 add test for cell size weighted average in OpenFOAM reader
db6b6158e8 add size weighted cell to point option in OpenFOAMReader
Acked-by: Kitware Robot <kwrobot@kitware.com>
Tested-by: buildbot <buildbot@kitware.com>
Merge-request: !9806
1- Improve the initialization of the interpolator when there is a lot of
data. We can now fill the interpolator with all the data in one time and
then, only compute one sort.
2- Improve the interpolation computation. We can now decide to use the
interpolation search algorithm instead of the binary search.
Co-authored-by: Pierre Guilbert <pierre.guilbert@kitware.com>