- Mar 04, 2025
-
-
Vicente Bolea authored
-
- Feb 28, 2025
-
-
dd88415c ci: remove duplicated MAVEN_NATIVE_ARTIFACTS Acked-by:
Kitware Robot <kwrobot@kitware.com> Acked-by:
buildbot <buildbot@kitware.com> Reviewed-by:
Sebastien Jourdain <sebastien.jourdain@kitware.com> Merge-request: !11950
-
- Feb 27, 2025
-
-
Vicente Bolea authored
The reason of this change being done in a different commit since this change cannot be merged to master due to a conflict in an unrelated but adjacent line at configure_options.cmake. (cherry picked from commit 7a350f5b)
-
- Feb 25, 2025
-
-
-
b043d4a5 Use VTK_ALWAYS_INLINE even on Windows 6018941f Add more special keywords to parser f46593b8 vtkFFT.txx: add needed but missing typename keyword Acked-by:
Spiros Tsalikis <spiros.tsalikis@kitware.com> Merge-request: !11937
-
c24fa8eb ci,java: allow different build types Acked-by:
-
- Feb 21, 2025
-
-
The __forceinline keyword is now recognized as a form of 'inline' by the wrappers, so it no longer causes a build failure. (cherry picked from commit 452a9324)
-
Adds __attribute() for icc, __inline and __forceinline for MSVC. Since these are used in vtkSetGet.h, it's necessary for the wrappers to be able to handle them. (cherry picked from commit 71a07324)
-
Cory Quammen authored
This fixes a compilation error on Intel Classic compilers. (cherry picked from commit 5ff030e5)
-
- Feb 19, 2025
-
-
Vicente Bolea authored
It also now includes the CMAKE_BUILD_TYPE in the filename of the native jars.
-
- Feb 11, 2025
-
-
f0d46cdd doc: fix typo in filename data_assembly.md Acked-by:
Christos Tsolakis <christos.tsolakis@kitware.com> Acked-by:
Sean Ahern <sean.ahern@ansys.com>
Merge-request: !11913 -
Cory Quammen authored
-
-
18a38103 XdmfValuesHDF: Print error when there is a ranks mismatch f6c748e2 vtkPiecewiseFunction: actually assign a fallback SearchMethod 382c038e vtkImageToStructuredPoints: fix improper bounds alignment 6d8305b9 vtkPostgreSQLDatabase: factor out clamping 7204b5be vtkAxis: fix clamping assignment 788628b4 vtkImplicitModeller: factor out clamping 523e1f61 vtkSelectionSource: factor out clamping 2bb8a912 vtkCamera: clamp ViewAngle before updating ... Acked-by:
Mathieu Westphal (Kitware) <mathieu.westphal@kitware.com> Reviewed-by:
Nicolas Vuaille <nicolas.vuaille@kitware.com> Merge-request: !11909
-
18a38103 XdmfValuesHDF: Print error when there is a ranks mismatch f6c748e2 vtkPiecewiseFunction: actually assign a fallback SearchMethod 382c038e vtkImageToStructuredPoints: fix improper bounds alignment 6d8305b9 vtkPostgreSQLDatabase: factor out clamping 7204b5be vtkAxis: fix clamping assignment 788628b4 vtkImplicitModeller: factor out clamping 523e1f61 vtkSelectionSource: factor out clamping 2bb8a912 vtkCamera: clamp ViewAngle before updating ... Acked-by:
-
- Feb 10, 2025
-
-
(cherry picked from commit 780a8baa)
-
The `type` value that was just verified as out-of-range is still set after the block, so instead update it so the single assignment at the end is shared. (cherry picked from commit 9c6c952e)
-
(cherry picked from commit 2e9d08b6)
-
(cherry picked from commit 8f114753)
-
(cherry picked from commit e14e3a4a)
-
(cherry picked from commit e641ea55)
-
Clamping in the condition and again in the assignment is just error-prone. Clamp once and store the result. (cherry picked from commit ac81ee5c)
-
If the angle is different, but ends up being clamped to the current value, an unnecessary `Modified` event is generated. (cherry picked from commit 80c48cd5)
-
(cherry picked from commit acd3a1d8)
-
(cherry picked from commit 9b89398b)
-
on line 85 there is an error when tests are run with libc++ hardness mode with the debug setting on line 82 we reserve space for the vector this does not change n though so when we access it on line 85 there is an error n=0, to fix this we reserve and initalize the vector (cherry picked from commit e1d59512)
-
This change ensures that the camera orientation widget handles are updated at build time. This allows arbitary calls to BuildRepresentation to yield updated handles. (cherry picked from commit 8bad31f2)
-
(cherry picked from commit 147500ad)
-
(cherry picked from commit 2ac151e6)
-
Fixes overflows for large number of cells which can cause integer math to overflow. (cherry picked from commit 814eba3a)
-
(cherry picked from commit 4d7281e6)
-
- Feb 03, 2025
-
-
37cac86a Add doxygen macro override for Set/GetSmartPointerMacro Acked-by:
-
Sankhesh Jhaveri authored
This is necessary so that the classes that use the `Set/GetSmartPointerMacro` get documented properly with doxygen.
-
- Jan 16, 2025
-
-
406cceb9 AMReXParticlesReader: handle inexact division of grids among MPI ranks 1d4baf0d AMReXGridReader: Use std::size_t or vtkIdType instead of long where necessary 2715c463 AMReX - continue reading particle file when top level header does not exist 905c2586 Fix vtkPlotBar::GetBounds logic when log scale is enabled 72fb8a68 doc: Fix typo LogScaling -> LogScale in vtkAxis header fefb1764 Fix cell coloring for thick lines on apple silicon Acked-by:
Cory Quammen <cory.quammen@kitware.com>
Merge-request: !11834 -
-
- Jan 13, 2025
-
-
Jaswant Panchumarti (Kitware) authored
- this commit fixes the grid-process assignment logic robust when the number of grids cannot be exactly divided among the number of MPI ranks (pieces in this code) - this commit also adds MPI awareness to an existing unit test. - the unit test TestAMReXParticlesReader is run with MPI, when enabled, on 3 nodes. It passes only when the sum of the number of points across all nodes is equal to a known value. - without the change in vtkAMReXParticlesReader, the unit test will faill with MPI (cherry picked from commit de94dced)
-
Jaswant Panchumarti (Kitware) authored
- this commit should allow opening files larger than 2GB on windows. - it uses `size_t`/`vtkIdType` instead of `long` when doing stream operations like `seekg`, `tellg`. earlier, it passed `long` (32-bit in windows) to `seekg`. As a result, arrays beyond the 2GB offset could not be read into the buffer. - see user report https://github.com/AMReX-Codes/amrex/issues/4167 and https://discourse.paraview.org/t/potential-length-overflow-for-large-data/15516 (cherry picked from commit d9d40248)
-
Jaswant Panchumarti (Kitware) authored
- address paraview/paraview#22835 (cherry picked from commit 2f2329d0)
-
Jaswant Panchumarti (Kitware) authored
- address paraview/paraview#22733 - This commit fixes the logic in the `vtkPlotBar::GetBounds(double*, bool unscaled)` method to scale the bounds only if `unscaled` is false. Previously, it returned unscaled bounds even when `unscaled` was false and returned scaled bounds when `unscaled` was true. (cherry picked from commit 6d90695f)
-
Jaswant Panchumarti (Kitware) authored
(cherry picked from commit c6c3a83d)
-
