1. 08 Oct, 2020 1 commit
  2. 26 Nov, 2019 1 commit
  3. 31 Oct, 2019 1 commit
  4. 28 Apr, 2019 1 commit
  5. 06 Feb, 2019 1 commit
  6. 29 Jan, 2019 1 commit
    • Mark OLESEN's avatar
      ENH: restructuring of ensight output files · b7fb6116
      Mark OLESEN authored
      - changed ensightOutput from a class solely comprising static methods to
        a namespace and added in sub-namespaces Detail and Serial.
        This makes it easier to "mix-in" functions at different levels.
        Refactored and combined some serial/parallel code where possible.
        The general ensightOutput namespace has now shifted to be in the
        fileFormats lib, while leaving volField outputs in the conversion lib
        and cloud outputs in the lagrangian-intermediate lib.
        The ensightCloud namespace is now simply folded into the new
        ensightOutput namespace.
        These changes clean up some code, reduce fragmentation and
        duplication and removes the previous libconversion dependency for
      - use int for ensight nTypes constexpr
      Note: issue #1176 is unaffected except for the change in file name:
         ensightOutputTemplates.C -> ensightOutputVolFieldTemplates.C
  7. 07 Jan, 2019 1 commit
  8. 11 Dec, 2018 1 commit
  9. 13 Dec, 2018 1 commit
  10. 12 Dec, 2018 1 commit
  11. 10 Dec, 2018 1 commit
  12. 28 Nov, 2018 1 commit
  13. 25 Nov, 2018 2 commits
  14. 09 Oct, 2018 1 commit
  15. 10 Oct, 2018 1 commit
  16. 09 Oct, 2018 1 commit
  17. 02 Oct, 2018 1 commit
    • Mark OLESEN's avatar
      ENH: multiple zone selection for fvMeshSubsetProxy (#973) · 2fb382bf
      Mark OLESEN authored
      - handle tmp fields in interpolate methods
      - special method interpolateInternal() for creating a volume field
        with zero-gradient treatment for patches from an internal field.
        This method was previously also called interpolate(), but that
        masked the ability to subset the internal field only.
        Ensight output needs the volume field:
            uses interpolateInternal().
        VTK output has separate handling of internal and patch fields:
            uses interpolate().
      ENH: added fvMeshSubset mesh() method for baseMesh or subMesh.
      - simplies coding when the fvMeshSubset may or may not be in active use.
      ENH: update foamToEnsight to use newer methods in wrapped form
      - static interpolate functions with renaming for manual use with
        fvMeshSubset (when fvMeshSubsetProxy may be too limiting in
  18. 28 Sep, 2018 1 commit
  19. 09 Aug, 2018 1 commit
  20. 31 Jul, 2018 1 commit
  21. 30 Jul, 2018 1 commit
  22. 26 Jul, 2018 1 commit
  23. 25 Jul, 2018 1 commit
  24. 23 Jan, 2018 1 commit
  25. 19 Dec, 2017 1 commit
  26. 27 Apr, 2018 1 commit
  27. 26 Feb, 2018 1 commit
    • Mark OLESEN's avatar
      ENH: cleanup autoPtr class (issue #639) · 660f3e54
      Mark OLESEN authored
      Improve alignment of its behaviour with std::unique_ptr
        - element_type typedef
        - release() method - identical to ptr() method
        - get() method to get the pointer without checking and without releasing it.
        - operator*() for dereferencing
      Method name changes
        - renamed rawPtr() to get()
        - renamed rawRef() to ref(), removed unused const version.
      Removed methods/operators
        - assignment from a raw pointer was deleted (was rarely used).
          Can be convenient, but uncontrolled and potentially unsafe.
          Do allow assignment from a literal nullptr though, since this
          can never leak (and also corresponds to the unique_ptr API).
      Additional methods
        - clone() method: forwards to the clone() method of the underlying
          data object with argument forwarding.
        - reset(autoPtr&&) as an alternative to operator=(autoPtr&&)
      STYLE: avoid implicit conversion from autoPtr to object type in many places
      - existing implementation has the following:
           operator const T&() const { return operator*(); }
        which means that the following code works:
             autoPtr<mapPolyMesh> map = ...;
             updateMesh(*map);    // OK: explicit dereferencing
             updateMesh(map());   // OK: explicit dereferencing
             updateMesh(map);     // OK: implicit dereferencing
        for clarity it may preferable to avoid the implicit dereferencing
      - prefer operator* to operator() when deferenced a return value
        so it is clearer that a pointer is involve and not a function call
        etc    Eg,   return *meshPtr_;  vs.  return meshPtr_();
  28. 06 Mar, 2018 1 commit
    • Mark OLESEN's avatar
      ENH: dedicated HashSetOps, HashTableOps namespaces · bcabe827
      Mark OLESEN authored
      - relocated HashSetPlusEqOp and HashTablePlusEqOp to
        HashSetOps::plusEqOp and HashTableOps::plusEqOp, respectively
      - additional functions for converting between a labelHashSet
        and a PackedBoolList or List<bool>:
        From lists selections to labelHashSet indices:
            HashSetOps::used(const PackedBoolList&);
            HashSetOps::used(const UList<bool>&);
        From labelHashSet to list forms:
            PackedBoolList bitset(const labelHashSet&);
            List<bool> bools(const labelHashSet&);
  29. 21 Feb, 2018 1 commit
  30. 08 Jan, 2018 1 commit
    • Mark OLESEN's avatar
      ENH: simplify method names for reading argList options and arguments · 345a2a42
      Mark OLESEN authored
      - use succincter method names that more closely resemble dictionary
        and HashTable method names. This improves method name consistency
        between classes and also requires less typing effort:
          args.found(optName)        vs.  args.optionFound(optName)
          args.readIfPresent(..)     vs.  args.optionReadIfPresent(..)
          args.opt<scalar>(optName)  vs.  args.optionRead<scalar>(optName)
          args.read<scalar>(index)   vs.  args.argRead<scalar>(index)
      - the older method names forms have been retained for code compatibility,
        but are now deprecated
  31. 21 Nov, 2017 1 commit
  32. 13 Sep, 2017 1 commit
    • Andrew Heather's avatar
      ENH: Lagrangian - provided backwards compatibility for cases using the · 2defba00
      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;
  33. 11 Jul, 2017 1 commit
  34. 14 Jun, 2017 2 commits
  35. 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.
  36. 17 May, 2017 1 commit
  37. 16 May, 2017 1 commit
  38. 18 May, 2017 1 commit