Skip to content
Snippets Groups Projects
  1. Nov 24, 2016
  2. Nov 23, 2016
  3. Nov 22, 2016
  4. Nov 21, 2016
  5. Nov 20, 2016
  6. Nov 19, 2016
  7. Nov 17, 2016
  8. Nov 15, 2016
  9. Nov 14, 2016
    • Mark OLESEN's avatar
      Merge branch 'surface-declutter' into 'develop' · fff2ee54
      Mark OLESEN authored
      Surface declutter - issue #294
      
      Removing various clutter from surfMesh and triSurface
      - unused classes/files (backup copies on non-release repo)
      - relocate some triSurface-related classes to where they make more sense, and where they can be reused.
      - improve handling of various face types in MeshedSurface and UnsortedMeshedSurface (to bridge the gap to triSurface)
      - improve transfer methods for reclaiming/reusing surface allocations
      
      See merge request !77
      fff2ee54
  10. Nov 13, 2016
    • Mark Olesen's avatar
      ENH: provide ModifiableMeshedSurface class · e112eb50
      Mark Olesen authored
      - A special purpose MeshedSurface that exposes the stored values
        for direct modification.
      
      - Its usage should be restricted to special cases where the surface
        needs modifications as an atomic operation.
      e112eb50
    • Mark Olesen's avatar
      ENH: simplify check for metis sizes (issue #290) · 704620ae
      Mark Olesen authored
      - Now that the metisDecomp uses the metis definition for float/double,
        do not need to verify the scalar sizes.
      
      Note:
      - could drop precision qualifier for metis, scotch installation
        (include, lib) as being unneeded, but it is simpler to keep them
        and continue to use the FOAM_EXT_LIBBIN path
        (in case other ThirdParty software is compiled with different
        precisions).
      704620ae
  11. Nov 12, 2016
    • Mark Olesen's avatar
      ENH: provide xfer methods for the meshed surface components. · 52b6c49b
      Mark Olesen authored
      - the surfMesh classes where originally designed with limited
        (protected) access to the underlying components. This is to
        avoid unintentional direct changes, since these can quickly
        lead to inconsistencies with the topology addressing etc.
      
        However, if we wish to efficiently adjust surfaces, it is useful
        to modify the components directly.
        The compromise is to provide 'xfer' methods:
          - xferFaces()
          - xferPoints()
          - xferZones()
        These transfer the contents to an Xfer container for reuse, while
        also resetting the topology addressing.  To apply the changes,
        the reset() method is used.
      52b6c49b
  12. Nov 13, 2016
  13. Nov 12, 2016