1. 28 Sep, 2022 1 commit
  2. 20 Sep, 2022 2 commits
    • Ryan Krattiger's avatar
      Add name mangling module test. · 95ff3e54
      Ryan Krattiger authored
      This is a UNIX only test.
      95ff3e54
    • Ryan Krattiger's avatar
      Put VTK symbols inside ABI namespace macros. · 65fc526a
      Ryan Krattiger authored
      VTK_ABI_NAMESPACE_{BEGIN,END} macro is inserted around all VTK symbols.
      
      Exclusions:
       * C interfaces, such as GetVTKVersion and the python module.
       * third-party libraries and external libraries that are not maintained
         by VTK but are part of the VTK repository.
       * Cxx module tests
       * Utilities
       * Wrapping/Tools
      65fc526a
  3. 06 Sep, 2022 3 commits
  4. 02 Sep, 2022 3 commits
  5. 03 Aug, 2022 1 commit
  6. 19 Jul, 2022 1 commit
  7. 13 Jul, 2022 1 commit
  8. 01 Jul, 2022 3 commits
  9. 30 Jun, 2022 1 commit
  10. 28 Jun, 2022 2 commits
  11. 15 Jun, 2022 3 commits
    • Sean McBride's avatar
      Fixed many warnings on cdash · 18f48ab1
      Sean McBride authored
      Specifically:
      
      Filters/FlowPaths/vtkTemporalInterpolatedVelocityField.cxx:339:19: warning: moving a temporary object prevents copy elision [-Wpessimizing-move]
      
      Filters/Sources/vtkHyperTreeGridPreConfiguredSource.h:151:11: warning: '~vtkHyperTreeGridPreConfiguredSource' overrides a destructor but is not marked 'override' [-Winconsistent-missing-destructor-override]
      
      Filters/Statistics/Testing/Cxx/TestLengthDistribution.cxx:34:24: warning: variable 'ug' set but not used [-Wunused-but-set-variable]
      
      IO/Cesium3DTiles/vtkCesium3DTilesWriter.cxx:219:58: warning: unused parameter 'port' [-Wunused-parameter]
      
      IO/Cesium3DTiles/vtkCesiumPointCloudWriter.cxx:78:27: warning: unused parameter 'array' [-Wunused-parameter]
      
      IO/Cesium3DTiles/TreeInformation.cxx:924:81: warning: unused parameter 'node' [-Wunused-parameter]
      
      Charts/Core/vtkPlotParallelCoordinates.cxx:211:25: warning: comparison of integers of different signs: 'int' and 'size_t' (aka 'unsigned long') [-Wsign-compare]
      
      Charts/Co...
      18f48ab1
    • Spiros Tsalikis's avatar
      f19de954
    • Spiros Tsalikis's avatar
  12. 03 Jun, 2022 1 commit
  13. 01 Jun, 2022 1 commit
  14. 24 May, 2022 4 commits
  15. 17 May, 2022 10 commits
  16. 10 May, 2022 1 commit
  17. 03 May, 2022 2 commits
    • Spiros Tsalikis's avatar
      Cell/Point Locators: UseExistingSearchStructure for all locators · 186626d5
      Spiros Tsalikis authored
      UseExistingSearchStructure, when enabled (default off), it allows the locator to NOT be
      built again. This is useful when you have a dataset that either changes because
      the FieldData (PointData/CellData) changed or the actual dataset object changed
      but it's actually the same geometry (useful when a dataset has timesteps).
      When this flag is on you need to use ForceBuildLocator() to rebuild the locator,
      if your dataset changes.
      
      To accommodate this functionality now all locators implement the following
      functions: BuildLocator/ForceBuildLocator/BuildLocatorInternal.
      
      Also, the LazyEvaluation flag for CellLocators has been deprecated because
      it was not used, except in vtkCachingInterpolatedVelocityField, and also it
      could lead to thread-safety issues when 2 threads would call e.g. FindCell
      and both threads would try to build the locator.
      186626d5
    • Spiros Tsalikis's avatar
      CellLocators: Unify IntersectWithLine/FindCellAlongLine · 5af0b700
      Spiros Tsalikis authored
      vtkCellLocator(CL), vtkStaticCellLocator(SCL), vtkCellTreeLocator(CTL)
      vtkModifiedBSPTree(BSP) now all have a similar implementation with regard
      to their IntersectWithLine and FindCellAlongLine functions. FindCellAlongLine
      is actually a special case of a more general IntersectWithLine that returns
      points/cellIds which now all cell locators implement, and therefore they also
      support FindCellAlongLine (new for CTL, BSP).
      
      Inside those functions the given tolerance is now also used not only for the cell's
      intersectWithLine function but also for checking for intersection with the bounds
      of the cell itself which happens before that. This is needed because if we don't use
      the tolerance in the bounds check, for a line that passes right next to the bounds of
      a quad, the cell's IntersectWithLine using the tolerance can return that there was an
      intersection, but the intersection with the bounds of cell could say return no intersection,
      if the tolerance is not used. This way we could have a false-negative.
      
      In the past SCL had issues with not intersecting with cells in the functions
      IntersectWithLine/FindCellsAlongALine. For that reason Tolerance was introduced to
      ameliorate this issue by padding the bins by the Locator's Tolerance. Tolerance needed
      to be removed because nobody was using it except 1-2 classes that had the
      problem of intersection, and it would lead to really slow performance
      if the dataset was small bounds-wise, because the default Tolerance was 0.001.
      
      The intersection issues have actually been resolved thanks to the double
      tolerance that Will Schroeder introduced in FindCellsAlongALine and I copied
      in IntersectWithLine as well. This way, we get more accurate and faster, results
      with a smaller memory foot-print. Since Tolerance is no longer used,
      vtkStaticCellLocator's UseDiagonalLengthTolerance has also been deprecated.
      
      CTL's and BSP's IntersectWithLine have become thread-safe, while the none thread-safe
      functions can still be called through the functions of the vtkAbstractCellLocator.
      
      BSP has now the option of not caching cell bounds.
      
      Finally, vtkAbstractCellLocator now clearly states which functions are
      thread-safe or not and the documentation has been unified throughout
      all the cell locators.
      5af0b700