1. 03 Oct, 2018 1 commit
  2. 04 Oct, 2018 4 commits
  3. 03 Oct, 2018 2 commits
  4. 01 Oct, 2018 1 commit
  5. 26 Sep, 2018 1 commit
  6. 28 Sep, 2018 6 commits
  7. 27 Sep, 2018 4 commits
  8. 26 Sep, 2018 1 commit
  9. 25 Sep, 2018 2 commits
  10. 21 Sep, 2018 2 commits
  11. 20 Sep, 2018 1 commit
  12. 25 Sep, 2018 1 commit
    • Mark OLESEN's avatar
      ENH: allow new patch names in subsetMesh (issue #1019) · d0da21fe
      Mark OLESEN authored
      Previously had 3 possibilities for handling exposed internal faces
        1. use default "oldInternalFaces"
        2. specify -patch, to use the specified (existing) patch
        3. specify -patches, to use the geometrically closest patches
      Now relaxed the restriction on -patch to allow specification of a new
      (not yet existing) patch name. This improves flexibility, but won't
      catch typing mistakes.
      Harmonize behaviour of -patches and -patch. When -patches is used to
      specify a single, non-regex patch name, it now behaves identically to
      -patch. Since the getList handling for options already allows special
      treatment for single parameter lists, the following will work
            subsetMesh -patch  patch0
            subsetMesh -patches patch0
            subsetMesh -patches '( patch0 )'
      In the future it might be reasonable to fully combine the behaviour of
      '-patch' and '-patches' and treat them as aliases for each other.
      ENH: support subsetMesh on a cellZone.
      - when the '-zone' option is specified, the command argument is treated
        as the name (or names) of cellZones to be selected instead of as the
        name of the cellSet.
        The command argument can be a single word, regex, or list of
            subsetMesh -zone -patch mypatch  mixer
            subsetMesh -zone -patch mypatch  '(mixer "moving.*" )'
      STYLE: simplify set handling and other code cleanup in subsetMesh
  13. 21 Sep, 2018 1 commit
  14. 19 Sep, 2018 8 commits
  15. 18 Sep, 2018 1 commit
  16. 19 Sep, 2018 1 commit
    • Mark OLESEN's avatar
      ENH: improve distanceSurface handling (issue #1012) · 4aa94bd1
      Mark OLESEN authored
      - 'signed' input parameter only mandatory for distance > 0.
        A distance <= 0 is always signed and the input parameter is ignored.
      - Use normal distance when distance == 0. This has no effect when
        the surface has no open edges, but improves on rounding issues
        around the zero crossing when the surface has open edges.
        This may still need future revisiting.
  17. 14 Sep, 2018 3 commits
    • Mark OLESEN's avatar
      ENH: refactor cutting-plane cell selection · 9973c378
      Mark OLESEN authored
      - avoid duplicate code by relocating cellZone selection and bounding box
        sub-selection into cuttingPlane and cuttingSurfaceBaseSelection.
        Allows reuse by inherited classes (sampledPlane, surfMeshSamplePlane).
    • Mark OLESEN's avatar
      ENH: make cuttingPlane cell walker an algorithm · a8ef9e97
      Mark OLESEN authored
      - takes two general actions:
        1. orient edge in canonical direction (positive gradient) and detect
           any edge intersection.
        2. edge intersection alpha (0-1)
      - refactor into a cuttingSurfaceBase intermediate class with the
        actions as templated parameters rather than function pointers. This
        allows the use of lambda functions with captures from the caller.
    • Mark OLESEN's avatar
      STYLE: split up cuttingPlane source files · 7cf232ce
      Mark OLESEN authored