1. 21 Feb, 2019 1 commit
  2. 17 Feb, 2019 2 commits
    • Mark Olesen's avatar
      ENH: minor blockMesh improvements · 48e3590b
      Mark Olesen authored
      - avoid potential ambiguities in naming of mesh faces/edges
        vs. block faces/edges
      
      - additional methods characterizing the number of faces
        (internal, boundary, total) associated with a blockDescriptor
      
      - cellLabel() accessor and checkIndex() methods
      
      - restore demand-driven behaviour of block, cache the calculated cells
        and refactor generation of block boundary faces to improve potential
        reuse.
      48e3590b
    • Mark Olesen's avatar
      ENH: support VTK output of point ids · fe445ac5
      Mark Olesen authored
      - can be useful for diagnosing mesh internals and the locations of
        decomposed cells.
      fe445ac5
  3. 16 Feb, 2019 2 commits
    • Mark Olesen's avatar
      STYLE: declare edge::operator[] · 9cb6338c
      Mark Olesen authored
      - already available from the FixedList inheritance, but provide
        explicitly in edge to allow future adjustment of the inheritance
        (#1205)
      9cb6338c
    • Mark Olesen's avatar
      ENH: improvements to label/scalar ranges · 041be829
      Mark Olesen authored
      - construct from MinMax, optional start index for identity factory
        method to match Foam::identity()
      
      - use GREAT instead of VGREAT in inverted scalarRange.
        Consistent with boundBox - to reduce the potential of overflow
        if calculating the span.
      
      - add min()/max() methods to labelRange
      041be829
  4. 18 Feb, 2019 5 commits
  5. 13 Feb, 2019 1 commit
    • Mark Olesen's avatar
      ENH: extended runTimePostProcessing (#1206) · 42fbf6d3
      Mark Olesen authored
      - Extended runTimePostProcessing to include access to "live"
        simulation objects such a geometry patches and sampled surfaces
        stored on the "functionObjectObjects" registry.
      
      - Add 'live' runTimePostProcessing of cloud data.
        Extracts position and fields from the cloud via its objectRegistry writer
      
      - For the "live" simulation objects, there are two new volume filters
        that work directly with the OpenFOAM volume fields:
            * iso-surface
            * cutting planes
        Both use the VTK algorithms directly and support multiple values.
        Eg, can make multiple iso-levels or multiple planes parallel to each
        other.
      
      - When VTK has been compiled with MPI-support, parallel rendering will
        be used.
      
      - Additional title text properties (shadow, italic etc)
      
      - Simplified handling of scalar-bar and visibility switches
      
      - Support multiple text positions. Eg, for adding watermark text.
      42fbf6d3
  6. 12 Feb, 2019 1 commit
  7. 07 Feb, 2019 1 commit
    • Mark Olesen's avatar
      ENH: improved sample surfaces and surface writers (#1206) · 181c974b
      Mark Olesen authored
      - The writers have changed from being a generic state-less set of
        routines to more properly conforming to the normal notion of a writer.
        These changes allow us to combine output fields (eg, in a single
        VTK/vtp file for each timestep).
      
        Parallel data reduction and any associated bookkeeping is now part
        of the surface writers.
        This improves their re-usability and avoids unnecessary
        and premature data reduction at the sampling stage.
      
        It is now possible to have different output formats on a per-surface
        basis.
      
      - A new feature of the surface sampling is the ability to "store" the
        sampled surfaces and fields onto a registry for reuse by other
        function objects.
      
        Additionally, the "store" can be triggered at the execution phase
        as well
      181c974b
  8. 23 Jan, 2019 1 commit
    • Mark Olesen's avatar
      ENH: added polySurface storage with fields (#1206) · 16bc6386
      Mark Olesen authored
      - This simple container provides a means of storing faces/points
        (ie, surfaces) with registered dimensioned fields.
      
        The main registry is used to hold face-based data, a secondary
        sub-registry is used to hold point-based data. This allows the same
        name for CellData and PointData fields without name collisions.
      16bc6386
  9. 07 Jan, 2019 9 commits
  10. 14 Feb, 2019 6 commits
  11. 07 Jan, 2019 2 commits
  12. 13 Feb, 2019 1 commit
  13. 12 Feb, 2019 4 commits
  14. 03 Feb, 2019 1 commit
  15. 07 Jan, 2019 3 commits