1. 20 Dec, 2017 1 commit
  2. 13 Dec, 2017 2 commits
  3. 06 Dec, 2017 1 commit
  4. 01 Dec, 2017 1 commit
  5. 22 Nov, 2017 1 commit
    • Philippe P. Pébaÿ's avatar
      Fixed issues with the computation of material interfaces in HTG · a4cc7836
      Philippe P. Pébaÿ authored
      This commit addresses to main issues:
      1. The AxisReflection was /adding/ modified arrays, as opposed to
         modifying in situ the interface arrays (vectors and intercepts).
         This had initially made on purpose with the intent of temporary
         retaining the original arrays for debugging purposes. However,
         this had been forgotten and left in place. As a result, interface
         computations after a reflection where incorrect. This bug was
         not revealing itself in the test harness so far as this combination
         (reflection + interface computations) was not exercised.
         As a result, this commit addresses the issue but also verifies
         this combination. Furthermore, the HTG source was modified in
         order to allow for the specification of intercepts arrays in
         the form that exercise this configuration.
      2. The Geometry extraction was not building material interfaces, as
         a result of some code having been leftover during the HTG-v2
         merger in VTK 8. This commit fixes this issue, and also adds
         a unit test to verify material extraction together with its
         corresponding non-regression image.
      a4cc7836
  6. 29 Oct, 2017 1 commit
    • Philippe P. Pébaÿ's avatar
      Fixed a bug in the Moore supercursor · baef249b
      Philippe P. Pébaÿ authored
      The goal of this commit was to fix a bug that occurred only in
      the (f=2;d=3) case ("binary 3D"), and that had been caused
      by a typo in the MooreChildCursorToChildTable and
       MooreChildCursorToParentCursorTable tables: specifically,
      a "23" had been written instread of "32".
      
      In addition, two non-regression tests, as well as their baseline
      images, were added in order to validate this fix:
      (i) a geometry case which does not exercise the offending part of
      the code but that illustrates the case built to do it; and
      (ii) a contouring case that does exercise that part of the code,
      for it relies on the "32" section of the Moore supercursor tables.
      baef249b
  7. 21 Sep, 2017 1 commit
  8. 12 Sep, 2017 2 commits
  9. 18 Aug, 2017 2 commits
  10. 17 Aug, 2017 1 commit
    • David E. DeMarle's avatar
      miscellaneous cleanup for merge readiness · 06e08644
      David E. DeMarle authored
      * pedantic spacing, doxygen and other style changes
      * fix unused variable warnings
      * fix sign comparison warnings
      * fix overridden variable warnings.
      * use nullptr instead of NULL or 0
      * use VTK_DELETE_FUNCTION instead of //Not implemented.
      * update a stray __WRAP__ to __VTK_WRAP__ (can likely remove too)
      * fixup override, should now be virtual only on base class, override
      on intermediate children. I'm not familar enough to know if any of the
      override should be final so I didn't add any.
      * revert the change to vtkCellTypeSource as it should not be required
      * fix a faulty test and commit the baseline image
      * can not stack allocate parentCursors dynamic array
      * fix potential use of uninitialized variable warnings with good defaults
      * remove declarations without implementations
      * fix type converion warnings
      * mtime declation and implementation return types must agree
      * M_SQRT2 is not cross platform
      * remove non-cross platform rusage from test
      * fix address unsigned<0 warnings
      * fix virtual function hidden warning
      * VTK_NEWINSTANCE hint so wrappers avoid comp warning
      * fix missing braces warning
      * fix bool vs number comparison warnings
      * fix invalid character literal escape sequence
      * streamline types in GetShiftedLevelZeroIndex to avoid warnings and
      make -1's meaningfule
      * revert planecutter changes as they are harmful and not needed
      * increase test tolerance and add alternate baseline images
          A couple of the dashboard machines draw lines slightly differently.
       Increase test tolerance to just above current failed level and in a
       few cases do that and add alternate images to settle down the noise.
      * disable two tests that do not work on every machine
         Authors are not yet able to reproduce and fix whatever the
       root cause is. disabling the tests until they can.
      06e08644
  11. 08 Aug, 2017 1 commit
    • Philippe P. Pébaÿ's avatar
      Full revision and extension of support for hypertreegrid objects and filters · 61908bd7
      Philippe P. Pébaÿ authored
      In this commit, we provide a complete revision and extension of support for
      hypertreegrid objects and filters, hereby entirely superseding the first
      versions thereof which we developed in 2011-2012.
      When compared to those obtained by constructing an intermediate
      unstructured mesh with fully described connectivity, this new structure
      demonstrates a gain of at least 80% in terms of memory footprint,
      with a better rendering while retaining similar execution speed.
      
      All ancillary structures such as cursors and supercursors have also
      been entirely refactored, for the sake of performance as well as of
      ease of maintenance. Existing native filters, i.e., that operate
      directly on hypertreegrid objects, have been revised accordingly.
      In addition, several new native filters have been added, together with
      a large set of non-regression tests and baseline images.
      
      This commit also implements an adaptive approach in order to accelerate the
      rendering of 2-dimensional hypertreegrids, hereby solving the problem posed
      by the loss of interactivity that occurs when dealing with large and/or
      deeply refined meshes. Specifically, view parameters are taken into account,
      in order to: on one hand, avoid creating surface elements that are
      outside of  the view area; on the other hand, utilize level-of-detail
      properties to cull those cells that are deemed too small to be visible
      with respect to the given view parameters. This adaptive approach typically
      results in a massive increase in rendering performance.
      
      Please refer to the following articles for a comprehensive description:
      https://arxiv.org/abs/1702.04852
      https://arxiv.org/abs/1703.00212
      61908bd7
  12. 08 Mar, 2016 1 commit
  13. 16 Apr, 2014 1 commit
  14. 17 May, 2013 1 commit
  15. 14 May, 2013 1 commit
    • Brad King's avatar
      Use vtk_add_test_cxx function · 5b018861
      Brad King authored
      Refactor */*/Testing/Cxx/CMakeLists.txt to use the vtk_add_test_cxx
      function instead of direct add_test calls.
      
      Change-Id: I73dee627fa87a399c48b409af046b116fc75a0fd
      5b018861
  16. 12 Apr, 2013 1 commit
    • Joachim Pouderoux's avatar
      Optimize HTG for large & sparse level 0 grids. · 34d55b7f
      Joachim Pouderoux authored
      - Replace the vtkCollection which has a find access in O(N) by a std::map.
      
      - Add vtkHyperTreeIterator to avoid browsing every potential tree of
      level 0 grid. Only available trees are now browsed.
      
      - Add a TimeStamp to avoid unnecessary calls to the costly
      UpdateHyperTreesLeafIdOffsets.
      
      Those 3 changes really improve the computation time for building the HTG
      but also for computing the dual and all the filters
      (AxisCut, Geometry & ToUnstructuredGrid).
      
      Also add points for each cell in the tree, not only for leaf, even if
      only leaf points are used to construct the dual and thus referenced by
      some cells.
      
      Change-Id: Ie954fdc8860a55d0de9c23097b0662a2d2123550
      34d55b7f
  17. 10 Apr, 2013 1 commit
    • Joachim Pouderoux's avatar
      HTG modification to support only defined (has mat) level 0 cells. · 3218f2cc
      Joachim Pouderoux authored
      Change the HyperTreeGrid mechanisms to provide efficient storage of very
      large level 0 grids with only few cells defined. Instead of creating a
      full grid array, only defined cells (through MaterialMaskIndex array)
      are stored and processed.
      The source has been updated to take advantage of this new feature.
      
      Some optimizations and code simplification are also provided.
      
      Provide a new test TestHyperTreeGridTernary3DGeometryLargeMaterialBits
      to test the large grids management.
      
      Set 3: Fix tests, mainly fix CopyStructure.
      
      Change-Id: Iaab0afd7d13e66d9ab105c554a4d873ab59f1d35
      3218f2cc
  18. 05 Apr, 2013 1 commit
  19. 23 Mar, 2013 1 commit
  20. 22 Mar, 2013 1 commit
  21. 25 Jan, 2013 1 commit
    • Philippe Pébay's avatar
      Implemented reverse boundary connection for material in 3D case · 88857b3c
      Philippe Pébay authored
      This is an additional fix to be used in relatively infrequent
      topological configurations (at edges & corners between cells of different
      material and different depth levels, when "viewed" from the
      non-material size). Albeit unfrequent, it is necessary to treat
      this case for completeness.
      
      Change-Id: Id66b14db1251210a26844aeab788883a3c0d9233
      88857b3c
  22. 24 Jan, 2013 3 commits
  23. 18 Jan, 2013 1 commit
  24. 17 Jan, 2013 1 commit
  25. 27 Dec, 2012 1 commit
  26. 19 Dec, 2012 4 commits
  27. 18 Dec, 2012 2 commits
  28. 17 Dec, 2012 1 commit
  29. 13 Dec, 2012 1 commit
  30. 01 Dec, 2012 2 commits