1. 17 Apr, 2019 1 commit
  2. 10 Apr, 2019 1 commit
  3. 06 Apr, 2019 1 commit
  4. 11 Feb, 2019 1 commit
  5. 06 Feb, 2019 4 commits
  6. 23 Jan, 2019 1 commit
    • Mark OLESEN's avatar
      BUG: clearing objectRegistry can leak memory (#1180) · 5878b6ed
      Mark OLESEN authored
      - now free anything owned by the registry when doing a clear.
      - the myriad of other ways to remove items (and potentially leaking)
        have not yet been addressed:
        * set, erase, retain, filterKeys, filterValues, filterEntries
  7. 18 Jan, 2019 1 commit
  8. 11 Nov, 2018 1 commit
  9. 10 Nov, 2018 1 commit
  10. 09 Nov, 2018 1 commit
    • Mark OLESEN's avatar
      ENH: add IOobjectList::findObject() method · faaa93fd
      Mark OLESEN authored
      - naming similar to objectRegistry, with unambiguous resolution.
        The lookup() methods have different return types depending on the
        calling parameter.
      STYLE: use IOobjectListTemplates.C for implementations
      - previously included as local definition within IOobjectList.C,
        but will be adding more templated methods soon.
      - adjust parameters (eg, matchName instead of matcher) to show their
      ENH: handle objectRegistry::names<void>(...)
      - this is equivalent to no Type restriction, and can be used when
        filtering names. Eg,
  11. 26 Jul, 2018 1 commit
  12. 02 Aug, 2017 1 commit
    • Mark OLESEN's avatar
      ENH: consolidate, cleanup some string methods · e70fc616
      Mark OLESEN authored
      - consolidate word::validated() into word::validate() and also allow
        as short form for string::validate<word>(). Also less confusing than
        having similarly named methods that essentially do the same thing.
      - more consistent const access when iterating over strings
      - add valid(char) for keyType and wordRe
  13. 07 Jul, 2017 1 commit
    • Andrew Heather's avatar
      INT: Integration of Mattijs' collocated parallel IO additions · d8d6030a
      Andrew Heather authored
      Original commit message:
      Parallel IO: New collated file format
      When an OpenFOAM simulation runs in parallel, the data for decomposed fields and
      mesh(es) has historically been stored in multiple files within separate
      directories for each processor.  Processor directories are named 'processorN',
      where N is the processor number.
      This commit introduces an alternative "collated" file format where the data for
      each decomposed field (and mesh) is collated into a single file, which is
      written and read on the master processor.  The files are stored in a single
      directory named 'processors'.
      The new format produces significantly fewer files - one per field, instead of N
      per field.  For large parallel cases, this avoids the restriction on the number
      of open files imposed by the operating system limits.
      The file writing can be threaded allowing the simulation to continue running
      while the data is being written to file.  NFS (Network File System) is not
      needed when using the the collated format and additionally, there is an option
      to run without NFS with the original uncollated approach, known as
      The controls for the file handling are in the OptimisationSwitches of
          //- Parallel IO file handler
          //  uncollated (default), collated or masterUncollated
          fileHandler uncollated;
          //- collated: thread buffer size for queued file writes.
          //  If set to 0 or not sufficient for the file size threading is not used.
          //  Default: 2e9
          maxThreadFileBufferSize 2e9;
          //- masterUncollated: non-blocking buffer size.
          //  If the file exceeds this buffer size scheduled transfer is used.
          //  Default: 2e9
          maxMasterFileBufferSize 2e9;
      When using the collated file handling, memory is allocated for the data in the
      thread.  maxThreadFileBufferSize sets the maximum size of memory in bytes that
      is allocated.  If the data exceeds this size, the write does not use threading.
      When using the masterUncollated file handling, non-blocking MPI communication
      requires a sufficiently large memory buffer on the master node.
      maxMasterFileBufferSize sets the maximum size in bytes of the buffer.  If the
      data exceeds this size, the system uses scheduled communication.
      The installation defaults for the fileHandler choice, maxThreadFileBufferSize
      and maxMasterFileBufferSize (set in etc/controlDict) can be over-ridden within
      the case controlDict file, like other parameters.  Additionally the fileHandler
      can be set by:
      - the "-fileHandler" command line argument;
      - a FOAM_FILEHANDLER environment variable.
      A foamFormatConvert utility allows users to convert files between the collated
      and uncollated formats, e.g.
          mpirun -np 2 foamFormatConvert -parallel -fileHandler uncollated
      An example case demonstrating the file handling methods is provided in:
      The work was undertaken by Mattijs Janssens, in collaboration with Henry Weller.
  14. 17 May, 2017 1 commit
    • Mark OLESEN's avatar
      ENH: added classes() method to objectRegistry/IOobjectList · 9761e9d8
      Mark OLESEN authored
      - provides a summary hash of classes used and their associated object names.
        The HashTable representation allows us to leverage various HashTable
        methods. This hashed summary view can be useful when querying
        particular aspects, but is most useful when reducing the objects in
        consideration to a particular subset. For example,
            const wordHashSet interestingTypes
            IOobjectList objects(runTime, runTime.timeName());
            HashTable<wordHashSet> classes = objects.classes();
            // Or do just the opposite:
        Can also use the underlying HashTable filter methods
      STYLE: use templated internals to avoid findString() when matching subsets
  15. 01 Dec, 2016 1 commit
    • Mark Olesen's avatar
      ENH: improve objectRegistry functionality (issue #322) · 92fa5a19
      Mark Olesen authored
      - Recursive searching for objects within a registry is now optional
        (previous it was always done).
        A recursive search effectively blocks the construction of sub-sub-registries
        if their names are 'masked' by some parent level sub-registry with
        the same name! (BUG)
      - Recursive search is now turned OFF by default, which makes it consistent
        with dictionary and probably causes the least number of surprises.
      Various new convenience methods added:
      - returns a non-const reference.
        For example,
            volScalarField& U = mesh().lookupObjectRef<volScalarField>("U");
        Instead of
            volScalarField& U = const_cast<volScalarField&>
      - returns a const pointer, and nullptr on failure.
        For example,
            const volScalarField* Uptr = mesh().lookupObjectPtr<volScalarField>("U");
            if (Uptr)
                const volScalarField& U = *Uptr;
        Instead of
            if (mesh().foundObject<volScalarField>("U"))
                const volScalarField& U = mesh().lookupObject<volScalarField>("U");
      - returns a non-const pointer, and nullptr on failure.
        For example,
            volScalarField* Uptr = mesh().lookupObjectRefPtr<volScalarField>("U");
            if (Uptr)
                volScalarField& U = *Uptr;  // use as reference
                (*Uptr) = ...;              // or use directly
        Instead of
            if (mesh().foundObject<volScalarField>("U"))
                volScalarField& U = const_cast<volScalarField&>
      - now works with template parameters and with regular expression
        matching as well.
        For example,
            wordList names  = mesh().sortedNames();
            wordList fields = mesh().sortedName<volScalarField>();
        Instead of
            wordList names  = mesh().sortedNames();
            wordList fields = mesh().names<volScalarField>();
  16. 15 May, 2016 1 commit
    • Henry Weller's avatar
      Patches contributed by Mattijs Janssens: · ce0cd351
      Henry Weller authored
      splitMeshRegions: handle flipping of faces for surface fields
      subsetMesh: subset dimensionedFields
      decomposePar: use run-time selection of decomposition constraints. Used to
          keep cells on particular processors. See the decomposeParDict in
        - preserveBaffles: keep baffle faces on same processor
        - preserveFaceZones: keep faceZones owner and neighbour on same processor
        - preservePatches: keep owner and neighbour on same processor. Note: not
          suitable for cyclicAMI since these are not coupled on the patch level
        - singleProcessorFaceSets: keep complete faceSet on a single processor
        - refinementHistory: keep cells originating from a single cell on the
          same processor.
      decomposePar: clean up decomposition of refinement data from snappyHexMesh
      reconstructPar: reconstruct refinement data (refineHexMesh, snappyHexMesh)
      reconstructParMesh: reconstruct refinement data (refineHexMesh, snappyHexMesh)
        - corrected mapping surfaceFields
        - adding processor patches in order consistent with decomposePar
      argList: check that slaves are running same version as master
      fvMeshSubset: move to dynamicMesh library
        - support for mapping dimensionedFields
        - corrected mapping of surfaceFields
      parallel routines: allow parallel running on single processor
      Field: support for
        - distributed mapping
        - mapping with flipping
      mapDistribute: support for flipping
      AMIInterpolation: avoid constructing localPoints
  17. 20 Mar, 2016 2 commits
  18. 07 Dec, 2015 1 commit
    • mattijs's avatar
      BUG: objectRegistry: do not clear event number on dependent objects · 9298d68a
      mattijs authored
      This was causing same event number on both U and grad(U) which meant
      that if one of the processors had different event number the trigger
      of gradient caching would not be synchronised. Now instead the overflow
      is detected in the regIOobject::upToDate function and handled consistently
      (by assuming that the events of object will never differ by more than
  19. 11 Nov, 2015 2 commits
  20. 10 Nov, 2015 1 commit
  21. 11 Dec, 2012 1 commit
  22. 17 Apr, 2012 1 commit
  23. 19 Oct, 2011 1 commit
  24. 14 Aug, 2011 1 commit
  25. 19 Jan, 2011 1 commit
  26. 14 Jan, 2011 1 commit
  27. 07 Jan, 2011 1 commit
  28. 05 Jan, 2011 2 commits
  29. 08 Dec, 2010 1 commit
  30. 28 Jul, 2010 1 commit
  31. 02 Jun, 2010 1 commit
  32. 29 Mar, 2010 1 commit
  33. 01 Dec, 2009 1 commit
  34. 14 Jul, 2009 1 commit