1. 20 Oct, 2017 2 commits
  2. 13 Oct, 2017 1 commit
  3. 05 Oct, 2017 2 commits
  4. 27 Sep, 2017 1 commit
  5. 26 Sep, 2017 2 commits
  6. 22 Sep, 2017 10 commits
    • Henry Weller's avatar
      sixDoFRigidBodyState: New functionObject which writes the rigid-body state · 94b62c28
      Henry Weller authored and Andrew Heather's avatar Andrew Heather committed
      Based on code contributed by SeongMo Yeon
      Resolves feature request https://bugs.openfoam.org/view.php?id=2656
    • Andrew Heather's avatar
      ENH: Reinstated the wallBoundedStreamline function object · c7edc26d
      Andrew Heather authored
      Note: performs its own tracking and does not rely on the base
      particle::trackXXX functions, and uses a local particle position.
      Look to update to barycentric tracking in the future.
    • Henry Weller's avatar
      Merged reactingParcelFilmFoam into reactingParcelFoam · bc82aff0
      Henry Weller authored and Andrew Heather's avatar Andrew Heather committed
      The combined solver includes the most advanced and general functionality from
      each solver including:
          Continuous phase
          Lagrangian multiphase parcels
          Optional film
          Continuous and Lagrangian phase reactions
          Strong buoyancy force support by solving for p_rgh
      The reactingParcelFoam and reactingParcelFilmFoam tutorials have been combined
      and updated.
    • Henry Weller's avatar
      compressibleInterFoam: Improved mass conservation · 6ad88f15
      Henry Weller authored and Andrew Heather's avatar Andrew Heather committed
      using the continuity error correction formulation developed for
      twoPhaseEulerFoam and reactingEulerFoam.
    • Andrew Heather's avatar
      INT: Integration of Mattijs' collocated parallel IO additions · 85f12ff5
      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.
    • Henry Weller's avatar
      tutorials/multiphase/interDyMFoam/RAS/DTCHull: Resolve stability issue caused... · 7a41ed10
      Henry Weller authored and Andrew Heather's avatar Andrew Heather committed
      tutorials/multiphase/interDyMFoam/RAS/DTCHull: Resolve stability issue caused by improvements to MULES
    • Henry Weller's avatar
    • Will Bainbridge's avatar
      tutorials/lagrangian: Added mixedVesselAMI2D · 28024e5f
      Will Bainbridge authored and Andrew Heather's avatar Andrew Heather committed
      This tutorial demonstrates moving mesh and AMI with a Lagrangian cloud.
      It is very slow, as interaction lists (required to compute collisions)
      are not optimised for moving meshes. The simulation time has therefore
      been made very short, so that it finishes in a reasonable time. The
      mixer only completes a small fraction of a rotation in this time. This
      is still sufficient to test tracking and collisions in the presence of
      AMI and mesh motion.
      In order to generate a convincing animation, however, the end time must
      be increased and the simulation run for a number of days.
    • Henry Weller's avatar
      cloudSolution: Check consistency between the transient option · e811fd25
      Henry Weller authored and Andrew Heather's avatar Andrew Heather committed
      and the continuous-phase simulation type
      For LTS and steady-state simulations the transient option does not need to be
      provided as only steady-state tracking is appropriate.  For transient running
      the Lagrangian tracking may be steady or transient.
    • Will Bainbridge's avatar
      Lagrangian: Rewrite of the particle tracking algorithm to function in · b7d08241
      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.
  7. 08 Sep, 2017 2 commits
  8. 09 Aug, 2017 1 commit
  9. 03 Aug, 2017 1 commit
    • Mark OLESEN's avatar
      TUT: use general 'scale' instead of 'convertToMeters' in blockMeshDict · ab84869c
      Mark OLESEN authored
      - although this has been supported for many years, the tutorials
        continued to use "convertToMeters" entry, which is specific to blockMesh.
        The "scale" is more consistent with other dictionaries.
      - ignore "scale 0;" (treat as no scaling) for blockMeshDict,
        consistent with use elsewhere.
  10. 29 Jul, 2017 1 commit
  11. 27 Jul, 2017 1 commit
  12. 19 Jul, 2017 1 commit
  13. 17 Jul, 2017 2 commits
  14. 07 Jul, 2017 2 commits
  15. 06 Jul, 2017 2 commits
  16. 29 Jun, 2017 2 commits
  17. 28 Jun, 2017 4 commits
  18. 27 Jun, 2017 3 commits