1. 01 Oct, 2018 2 commits
  2. 28 Sep, 2018 1 commit
    • Berk Geveci's avatar
      Ported all legacy readers to the new reader architecture. · e9bc920d
      Berk Geveci authored
      The new new reader architecture allows for things such as
      time series without changes to the subclasses.  To benefit
      from this, ported all legacy VTK readers to this architecture.
      
      Also developed a simple reader superclass. This superclass
      can be used to implement algorithms that are neither time
      aware nor parallel.
      
      Also rearchitected the Xdmf readers so that they don't
      unnecessarily subclass from VTK legacy readers.
      e9bc920d
  3. 25 Sep, 2018 1 commit
    • Sankhesh Jhaveri's avatar
      Issue error if vtkAlgorithm::GetInputConnection called on wrong port · 248bf676
      Sankhesh Jhaveri authored
      The original logic was issuing a warning if querying a connection that
      was outside the range of input connections to the port. This led to
      warnings in application code that was querying if a particular algorithm
      had input connections yet.
      
      The new logic issues an error if the port in reference, is outside the
      normal range of input ports for the algorithm but silently returns a
      nullptr when the connection index is outside the range of connection
      indices for the port i.e. no more warning when no input is provided.
      248bf676
  4. 20 Sep, 2018 1 commit
  5. 19 Sep, 2018 4 commits
  6. 18 Sep, 2018 1 commit
  7. 17 Sep, 2018 10 commits
  8. 16 Sep, 2018 1 commit
  9. 14 Sep, 2018 6 commits
  10. 12 Sep, 2018 2 commits
  11. 07 Sep, 2018 1 commit
    • Ben Boeckel's avatar
      warnings: fix strncpy warnings · e1aa3933
      Ben Boeckel authored
      GCC is getting smarter and detects that we're not copying the NUL
      terminator over.
      
      There are two approaches to fixing the warning:
      
        - where code is already a bit more complicated, just use `std::string`
          instead of C-style string manipulations; and
        - where we were doing `strncpy(dest, src, strlen(src))`, just use
          `strcpy` instead since the destination sizes are made based on the
          size of `src` anyways.
      e1aa3933
  12. 04 Sep, 2018 1 commit
    • David Gobbi's avatar
      Implement clamp with ternary for better optimization · 78a2e8ab
      David Gobbi authored
      Both clang and MSVC are very good at optimizing this ternary into
      minsd, maxsd compiler instructions.  For gcc, this optimizes best
      if -ffast-math is used (since gcc might otherwise be pedantic about
      the handling of inf, nan, and negative zero).
      78a2e8ab
  13. 03 Sep, 2018 1 commit
  14. 30 Aug, 2018 1 commit
    • Andreas Buykx's avatar
      Avoid unnecessary allocation of vtkInformation · 48861127
      Andreas Buykx authored
      Calling Modified on any vtkDataArray caused an vtkInformation instance
      to be created if none existed yet. This leads to unnecessary dynamic
      memory allocation and deallocation.
      
      Solved by testing whether the array has a vtkInformation instance before
      getting it and resetting its keys.
      48861127
  15. 29 Aug, 2018 3 commits
  16. 27 Aug, 2018 1 commit
  17. 15 Aug, 2018 2 commits
    • Shreeraj Jadhav's avatar
      Clip Polyhedra Crashes for N-faced Elements · 47872a3e
      Shreeraj Jadhav authored
      When clipping a dataset that contains n-faced elements (polyhedra),
      the program crashes. This is due to use of point locator that merges
      similar points and causes mismatch in number of points and point-Ids
      stored in the clipped cells.
      The issue was fixed by updating the cells with new ids where the
      point locator is used in vtkPolyhedron::Clip function.
      Also, added a test case for clipping a polyhedra dataset.
      47872a3e
    • Menno Deij - van Rijswijk's avatar
      Fixed an indexing issue for polyhedron clipping. · 308c6074
      Menno Deij - van Rijswijk authored
      o When a cell is not intersected by the clip and needs to go forward
        without any changes, an indexing issue gave very distorted cells.
      308c6074
  18. 10 Aug, 2018 1 commit