1. 02 May, 2018 1 commit
  2. 16 Apr, 2018 1 commit
  3. 10 Apr, 2018 1 commit
    • Mark OLESEN's avatar
      ENH: provide extra log feedback when catalyst function objects end. · eb5a9821
      Mark OLESEN authored
      - Note that stopping the catalyst function object via a `timeEnd` value
        does not actually call the corresponding end() method.
        See: Development/OpenFOAM-plus#791
      ENH: support mkdir as dictionary keyword
      - this is a convenient means of creating an output directory from within
        the function object without corresponding python or shell script.
        Some pipelines (image generation) balk if the output directory does
        not exist. Others (vtm writer etc) will create their own.
  4. 03 Apr, 2018 1 commit
  5. 07 Jan, 2020 1 commit
  6. 23 Jun, 2018 1 commit
  7. 15 Jun, 2018 1 commit
    • Mark OLESEN's avatar
      ENH: adjustments to runTimePostProcessing · 3c96e8db
      Mark OLESEN authored
      - support VTP input in functionObjectCloud scene element
      - additional fallback lookup of cloud information from state properties
        instead of cloud OutputProperties
  8. 30 May, 2018 1 commit
  9. 17 May, 2018 1 commit
    • Mark OLESEN's avatar
      ENH: avoid memory leaks for HashPtrTable, PtrMap insertion (issue #749) · 2c5cdebe
      Mark OLESEN authored
      - disallow insert() of raw pointers, since a failed insertion
        (ie, entry already existed) results in an unmanaged pointer.
        Either insert using an autoPtr, or set() with raw pointers or autoPtr.
      - IOobjectList::add() now takes an autoPtr instead of an object reference
      - IOobjectList::remove() now returns an autoPtr instead of a raw pointer
  10. 24 Apr, 2018 1 commit
    • Mark OLESEN's avatar
      ENH: improve handling of ThirdParty packages · c794fa0d
      Mark OLESEN authored
      - generalize some of the library extensions (.so vs .dylib).
        Provide as wmake 'sysFunctions'
      - added note about unsupported/incomplete system support
      - centralize detection of ThirdParty packages into wmake/ subdirectory
        by providing a series of scripts in the spirit of GNU autoconfig.
        For example,
            have_boost, have_readline, have_scotch, ...
        Each of the `have_<package>` scripts will generally provide the
        following type of functions:
            have_<package>          # detection
            no_<package>            # reset
            echo_<package>          # echoing
        and the following type of variables:
            HAVE_<package>          # unset or 'true'
            <package>_ARCH_PATH     # root for <package>
            <package>_INC_DIR       # include directory for <package>
            <package>_LIB_DIR       # library directory for <package>
        This simplifies the calling scripts:
            if have_metis
                wmake metisDecomp
        As well as reducing clutter in the corresponding Make/options:
            EXE_INC = \
                -I$(METIS_INC_DIR) \
            LIB_LIBS = \
                -L$(METIS_LIB_DIR) -lmetis
        Any additional modifications (platform-specific or for an external build
        system) can now be made centrally.
  11. 18 Apr, 2018 1 commit
  12. 12 Apr, 2018 2 commits
  13. 11 Apr, 2018 1 commit
  14. 03 Apr, 2018 1 commit
  15. 26 Mar, 2018 1 commit
    • Mark OLESEN's avatar
      STYLE: consistent lookupOrDefault template parameters · f2a7200c
      Mark OLESEN authored
      - in many cases can just use lookupOrDefault("key", bool) instead of
        lookupOrDefault<bool> or lookupOrDefault<Switch> since reading a
        bool from an Istream uses the Switch(Istream&) anyhow
      STYLE: relocated Switch string names into file-local scope
  16. 21 Mar, 2018 1 commit
  17. 27 Feb, 2018 1 commit
  18. 31 Jan, 2018 1 commit
  19. 06 Dec, 2017 1 commit
  20. 13 Sep, 2017 1 commit
    • Andrew Heather's avatar
      ENH: Lagrangian - provided backwards compatibility for cases using the · 984f8f00
      Andrew Heather authored
      old "positions" file form
      The change to barycentric-based tracking changed the contents of the
      cloud "positions" file to a new format comprising the barycentric
      co-ordinates and other cell position-based info.  This broke
      backwards compatibility, providing no option to restart old cases
      (v1706 and earlier), and caused difficulties for dependent code, e.g.
      for post-processing utilities that could only infer the contents only
      after reading.
      The barycentric position info is now written to a file called
      "coordinates" with provision to restart old cases for which only the
      "positions" file is available. Related utilities, e.g. for parallel
      running and data conversion have been updated to be able to support both
      file types.
      To write the "positions" file by default, use set the following option
      in the InfoSwitches section of the controlDict:
          writeLagrangianPositions 1;
  21. 06 Sep, 2017 1 commit
  22. 12 Sep, 2017 2 commits
  23. 02 Aug, 2017 1 commit
  24. 20 Jul, 2017 1 commit
  25. 17 Jul, 2017 2 commits
    • Mark OLESEN's avatar
      ENH: make treatment of stream allocators more uniform (issue #532) · 41cfd4d0
      Mark OLESEN authored
      - use allocator class to wrap the stream pointers instead of passing
        them into ISstream, OSstream and using a dynamic cast to delete
        then. This is especially important if we will have a bidirectional
        stream (can't delete twice!).
      - file stream constructors with std::string (C++11)
      - for rewind, explicit about in|out direction. This is not currently
        important, but avoids surprises with any future bidirectional access.
      - combined string streams in StringStream.H header.
        Similar to <sstream> include that has both input and output string
    • Mark OLESEN's avatar
  26. 03 Jul, 2017 3 commits
  27. 13 Jun, 2017 1 commit
  28. 24 May, 2017 1 commit
    • Mark OLESEN's avatar
      ENH: paraview reader module with internal caching of the vtk geometries · 8d900264
      Mark OLESEN authored
      - The reader module allows two levels of caching.
        The OpenFOAM fvMesh can be cached in memory, for faster loading of
        fields. Additionally, the translated VTK geometries are held in a
        local cache. The cached VTK geometries should incur no additional
        overhead since they use the VTK reference counting for their storage
  29. 23 May, 2017 1 commit
  30. 15 May, 2017 3 commits
  31. 14 May, 2017 3 commits