1. 20 Mar, 2018 2 commits
    • Sean McBride's avatar
      Applied clang-tidy modernize-use-equals-default fixes · 84ec1d57
      Sean McBride authored
      This required some clean up, because the automatic changes borked a couple of files, but mostly resulted in stupid whitespacing. A few find/replace fixed things up.
      There are now some duplicate semis because it did changes like:
        ~AMRIndexIterator() override{};
        ~AMRIndexIterator() override= default;;
      Note there was a pointless semi before, which clang-tidy didn’t expect / account for.
      My next commit will remove them.
    • luz.paz's avatar
      Misc. typos (cont.) · c0e48025
      luz.paz authored
      Found via `codespell` and `grep`
  2. 19 Mar, 2018 1 commit
  3. 16 Mar, 2018 2 commits
    • Allison Vacanti's avatar
      Fix an integer overflow in vtkStaticCellLocator. · 12a62b5f
      Allison Vacanti authored
      The intermediate results of this calculation used 32-bit integers,
      which overflowed before casting to a 64-bit vtkIdType.
    • Allison Vacanti's avatar
      Use a tolerance for detecting zero width lengths. · 73fd119c
      Allison Vacanti authored
      A customer reported a bug in the cell locator crashing from not
      being able to allocate sufficient memory. The dimensions of the dataset
      were (2e-14, 1000, 500), and because of the 2e-14 length
      vtkBoundingBox::ComputeDivisions was creating roughly 11M bins to
      hold 60 cells :)
      Fixed by considering any lengths less than 0.1% of the average dataset
      width to be effectively zero.
  4. 14 Mar, 2018 2 commits
  5. 13 Mar, 2018 1 commit
  6. 12 Mar, 2018 1 commit
  7. 08 Mar, 2018 5 commits
  8. 28 Feb, 2018 1 commit
    • Ken Martin's avatar
      compute bounds was being done too often · c420991a
      Ken Martin authored
      The mtime checks were considering more then
      required. The bniggest culprits being the
      field/cell/point data arrays which have no impact
      on the bounds.
  9. 23 Feb, 2018 1 commit
  10. 22 Feb, 2018 3 commits
  11. 21 Feb, 2018 1 commit
    • Will Schroeder's avatar
      Added threaded random sequence generation · ba064de1
      Will Schroeder authored
      Added a new class vtkRandomPool which creates a sequence of
      random numbers in an array. The processing for large numbers
      is threaded. The pool can be used in multithreaded applications
      where a random sequence can be precalculated, and the then
      deterministically accessed to provide reproducible results. Pools
      can be created using difference subclasses of vtkRandomSequence.
      By default, vtkMersenneTwister is used.
  12. 20 Feb, 2018 2 commits
    • Will Schroeder's avatar
      Added Shepard normalization · 7c995e70
      Will Schroeder authored
      If requested, output data can be normalized via the Shepard sum.
      That is, each component of the output data array is divided by
      the Shepard sum for the associated point.
    • Will Schroeder's avatar
      New filter to extract points inside closed surface · 6f6146d7
      Will Schroeder authored
      Created a new filter vtkExtractEnclosedPoints that extracts all points
      inside of a closed manifold surface. Refactored some code so that the
      sister filter vtkSelectEnclosedPoints share code.
  13. 19 Feb, 2018 2 commits
  14. 15 Feb, 2018 1 commit
    • Utkarsh Ayachit's avatar
      make vtkOutputWindow easier to subclass/use · f156dd4e
      Utkarsh Ayachit authored
      This addresses the following issues with vtkOutputWindow.
      1. `vtkOutputWindow::DisplayText` method gets called for all types of
         messages and fired vtkCommand::MessageEvent. With no ability to
         determine the type of message in DisplayText overrides or
         MessageEvent handlers, this has little utility and one always ended
         up handling/overriding other `Display.*` methods. There was still a
         problem: it was challenging to determine if `DisplayText` was
         directly being called for output messages rather than via any of the
         other `Display.*` methods.
         This is fixed by adding `vtkOutputWindow::GetCurrentMessageType`
         protected method. Subclasses can use that in
         `vtkOutputWindow::DisplayText` overrides to determine message type.
         Additionally, a new `vtkCommand::TextEvent` is fired by
         `vtkOutputWindow::DisplayText` when the method is directly invoked.
      2. vtkOutputWindow presented all messages to `cerr`. It should put
         `vtkOutputWindow::DisplayText` to `cout` as those are not exceptions.
         Added `UseStdErrorForAllMessages` (defaults to same behavior as
         before) to change this.
  15. 12 Feb, 2018 2 commits
  16. 10 Feb, 2018 1 commit
  17. 09 Feb, 2018 1 commit
    • David E. DeMarle's avatar
      Fix Initialize in HyperTreeGrid. · 5244da0f
      David E. DeMarle authored
      Initialize needs to clear out all of the state and return
      the entire object to the default empty state, including arrays.
      Otherwise the vtm reader would fail when arrays from a previous
      parse stuck around. Now that initialize works, don't throw away
      arrays needlessly.
  18. 29 Jan, 2018 1 commit
  19. 26 Jan, 2018 1 commit
  20. 25 Jan, 2018 1 commit
  21. 22 Jan, 2018 2 commits
  22. 20 Jan, 2018 2 commits
  23. 17 Jan, 2018 1 commit
    • Shawn Waldon's avatar
      Handle simple filters with multiple output ports in composite pipeline · ce1ad00e
      Shawn Waldon authored
      This fixes the bug at the root of paraview/paraview#17763.  Previously
      the composite data pipeline would incorrectly handle simple filters with
      multiple output ports.  This would lead to crashes when executing these
      This commit changes the composite data pipeline to consider all output
      ports when evaluating and executing simple filters and adds a test of
      this behavior using both AMR and multiblcok data.
  24. 15 Jan, 2018 1 commit
  25. 13 Jan, 2018 1 commit
    • Will Schroeder's avatar
      New method to quickly pick/select points · 4dfc9291
      Will Schroeder authored
      Analogous to vtkStaticCellLocator, the
      vtkStaticPointLocator::IntersectWithLine method implements a fast method
      to pick points within a tolerance along a line. The point with a
      specified tolerance and closest to the ray start is returned.
      Note that finding the points closest to a line means testing some neighboring
      bins as well as bins that contain the line.
  26. 08 Jan, 2018 1 commit
    • Will Schroeder's avatar
      New extrusion filter extrudes to trim surface · a007b93d
      Will Schroeder authored
      This filter extrudes a generating polydata until it intersects
      a trim surface. Two inputs are required: the input generating
      polydata and the trim surface (also polydata). Options exist
      to control the capping process to produce the end cap at the average
      intersection distance, maximum intersection distance, minimum
      intersection distance, and as intersected.
      Further, vtkStaticCellLocator was not thread safe in its line
      intersection method, and the locator was not intersecting cells
      properly in all cases. The bin - line intersection traversal
      algorithm was confusing and non-optimal. Hence the commit
      also includes a rewrite of the intersection code to be thread
      safe and to use a more efficient bin/voxel traversal method.