1. 26 Jan, 2018 1 commit
  2. 25 Jan, 2018 1 commit
    • Mark Olesen's avatar
      ENH: remove Foam::Swap specializations for HashSet, HashTable · 915e8c9f
      Mark Olesen authored
      - without these will use the normal move construct + move assign.
        This is similarly efficient, but avoids the inadvertently having the
        incorrect Swap being used for derived classes.
      
      STYLE: remove unused xfer methods for HashTable, HashSet
      
      - unneeded since move construct and move assignment are possible
      915e8c9f
  3. 22 Feb, 2018 3 commits
  4. 20 Feb, 2018 1 commit
  5. 08 Feb, 2018 1 commit
  6. 08 Dec, 2017 1 commit
  7. 05 Nov, 2017 1 commit
  8. 19 Nov, 2017 1 commit
  9. 10 Nov, 2017 1 commit
    • Mark Olesen's avatar
      ENH: improved zone constructors · a59c87d5
      Mark Olesen authored
      - constructor for empty cell/face/point Zones, with contents to be
        transferred in later.
      
      - ZoneMesh::operator(const word&) to return existing zone or a new empty one.
      a59c87d5
  10. 06 Nov, 2017 1 commit
  11. 22 Sep, 2017 1 commit
  12. 24 Oct, 2017 1 commit
  13. 04 Oct, 2017 2 commits
  14. 20 Sep, 2017 1 commit
    • Mark Olesen's avatar
      ENH: update List and DynamicList methods (issue #595) · 049617d0
      Mark Olesen authored
      - improve functional compatibility with DynList (remove methods)
        * eg, remove an element from any position in a DynamicList
        * reduce the number of template parameters
        * remove/subset regions of DynamicList
      
      - propagate Swap template specializations for lists, hashtables
      
      - move construct/assignment to various containers.
      
      - add find/found methods for FixedList and UList for a more succinct
        (and clearer?) usage than the equivalent global findIndex() function.
      
      - simplify List_FOR_ALL loops
      049617d0
  15. 17 Jul, 2017 1 commit
  16. 14 Sep, 2017 1 commit
  17. 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;
      2defba00
  18. 03 Jul, 2017 1 commit
  19. 05 Jul, 2017 1 commit
  20. 03 Jul, 2017 1 commit
  21. 14 Jun, 2017 1 commit
    • mattijs's avatar
      ENH: overset: Initial release of overset capability. · fd665b4a
      mattijs authored
      Adds overset discretisation to selected physics:
      - diffusion : overLaplacianDyMFoam
      - incompressible steady : overSimpleFoam
      - incompressible transient : overPimpleDyMFoam
      - compressible transient: overRhoPimpleDyMFoam
      - two-phase VOF: overInterDyMFoam
      
      The overset method chosen is a parallel, fully implicit implementation
      whereby the interpolation (from donor to acceptor) is inserted as an
      adapted discretisation on the donor cells, such that the resulting matrix
      can be solved using the standard linear solvers.
      
      Above solvers come with a set of tutorials, showing how to create and set-up
      simple simulations from scratch.
      fd665b4a
  22. 26 May, 2017 1 commit
  23. 19 May, 2017 1 commit
  24. 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
      "masterUncollated".
      
      The controls for the file handling are in the OptimisationSwitches of
      etc/controlDict:
      
      OptimisationSwitches
      {
          ...
      
          //- 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:
      $FOAM_TUTORIALS/IO/fileHandling
      
      The work was undertaken by Mattijs Janssens, in collaboration with Henry Weller.
      d8d6030a
  25. 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
            {
                volScalarField::typeName,
                volVectorField::typeName
            };
      
            IOobjectList objects(runTime, runTime.timeName());
            HashTable<wordHashSet> classes = objects.classes();
      
            classes.retain(interestingTypes);
      
            // Or do just the opposite:
            classes.erase(unsupportedTypes);
      
        Can also use the underlying HashTable filter methods
      
      STYLE: use templated internals to avoid findString() when matching subsets
      9761e9d8
  26. 10 May, 2017 1 commit
  27. 05 Sep, 2017 1 commit
  28. 01 Jun, 2017 1 commit
  29. 22 May, 2017 1 commit
  30. 28 Apr, 2017 1 commit
    • Will Bainbridge's avatar
      Lagrangian: Rewrite of the particle tracking algorithm to function in · 743dea87
      Will Bainbridge authored and Andrew Heather's avatar Andrew Heather committed
      terms of the local barycentric coordinates of the current tetrahedron,
      rather than the global coordinate system.
      
      Barycentric tracking works on any mesh, irrespective of mesh quality.
      Particles do not get "lost", and tracking does not require ad-hoc
      "corrections" or "rescues" to function robustly, because the calculation
      of particle-face intersections is unambiguous and reproducible, even at
      small angles of incidence.
      
      Each particle position is defined by topology (i.e. the decomposed tet
      cell it is in) and geometry (i.e. where it is in the cell). No search
      operations are needed on restart or reconstruct, unlike when particle
      positions are stored in the global coordinate system.
      
      The particle positions file now contains particles' local coordinates
      and topology, rather than the global coordinates and cell. This change
      to the output format is not backwards compatible. Existing cases with
      Lagrangian data will not restart, but they will still run from time
      zero without any modification. This change was necessary in order to
      guarantee that the loaded particle is valid, and therefore
      fundamentally prevent "loss" and "search-failure" type bugs (e.g.,
      2517, 2442, 2286, 1836, 1461, 1341, 1097).
      
      The tracking functions have also been converted to function in terms
      of displacement, rather than end position. This helps remove floating
      point error issues, particularly towards the end of a tracking step.
      
      Wall bounded streamlines have been removed. The implementation proved
      incompatible with the new tracking algorithm. ParaView has a surface
      LIC plugin which provides equivalent, or better, functionality.
      
      Additionally, bug report <https://bugs.openfoam.org/view.php?id=2517>
      is resolved by this change.
      743dea87
  31. 27 Apr, 2017 1 commit
  32. 10 Mar, 2017 1 commit
  33. 15 Dec, 2016 1 commit
    • Mark Olesen's avatar
      BUG: polyMesh removeFiles side-effect for blockMesh viewer (issue #346) · a32a915d
      Mark Olesen authored
      - polyMesh constructor from cell shapes invoked 'removeFiles'.
        This may or may not be what the caller wants or expects.
        With the ParaView blockMesh viewer, this behaviour causes deletion of
        all mesh data (points, faces, etc) when the viewer is refreshed.
      
        Triggered even when just building the blockMesh topology.
      
      - only a few places that construct a polyMesh from cell shapes
        (mostly mesh conversion utilities).
        Ensure that the file removal (if any) occurs in the application
        and *not* as a side-effect of calling the polyMesh constructor.
      
      --
      
        blockMesh (application)
          - The placement of the removeFiles seems to also remove freshly
            generated sets (Bug or feature to remove sets?)
      
        +-----------------------+---------------+------------------+
        | Application           | Constructor   | removeFiles      |
        |                       | (patch info)  | new / existing   |
        +-----------------------+---------------+------------------+
        | blockMesh             | dictionary    | existing         |
        | ansysToFoam           | names         | new              |
        | cfx4ToFoam            | dictionary    | new              |
        | fluentMeshToFoam      | names         | new              |
        | gambitToFoam          | dictionary    | new              |
        | gmshToFoam            | names         | new              |
        | ideasUnvToFoam        | names         | new              |
        | kivaToFoam            | dictionary    | new              |
        | mshToFoam             | names         | new              |
        | netgenNeutralToFoam   | names         | new              |
        | plot3dToFoam          | names         | new              |
        | tetgenToFoam          | names         | new              |
        | vtkUnstructuredToFoam | names         | new              |
        +-----------------------+---------------+------------------+
      a32a915d
  34. 14 Dec, 2016 1 commit
  35. 29 Nov, 2016 1 commit
  36. 28 Nov, 2016 1 commit
  37. 25 Nov, 2016 1 commit
    • Henry Weller's avatar
      zoneCombustion: New cellZone based combustion model · 8462be6a
      Henry Weller authored
      in which the reactions are enabled only in the specified list of
      cellZones.  e.g. in constant/combustionProperties
      
      combustionModel zoneCombustion<psiChemistryCombustion>;
      
      active  true;
      
      zoneCombustionCoeffs
      {
          zones (catalyst);
      }
      
      and in constant/zoneCombustionProperties
      
      combustionModel laminar<psiChemistryCombustion>;
      
      active  true;
      
      laminarCoeffs
      {}
      8462be6a