1. 30 Apr, 2016 2 commits
  2. 29 Apr, 2016 3 commits
  3. 28 Apr, 2016 4 commits
  4. 27 Apr, 2016 4 commits
  5. 26 Apr, 2016 7 commits
  6. 25 Apr, 2016 4 commits
    • Henry Weller's avatar
      wmake/rules/linux.*Icc: Remove -xHost option which causes... · 5510c7e6
      Henry Weller authored
      wmake/rules/linux.*Icc: Remove -xHost option which causes surfaceFeatureExtract to fail for some cases
    • Henry Weller's avatar
      Completed boundaryField() -> boundaryFieldRef() · a4e2afa4
      Henry Weller authored
      Resolves bug-report http://www.openfoam.org/mantisbt/view.php?id=1938
      Because C++ does not support overloading based on the return-type there
      is a problem defining both const and non-const member functions which
      are resolved based on the const-ness of the object for which they are
      called rather than the intent of the programmer declared via the
      const-ness of the returned type.  The issue for the "boundaryField()"
      member function is that the non-const version increments the
      event-counter and checks the state of the stored old-time fields in case
      the returned value is altered whereas the const version has no
      side-effects and simply returns the reference.  If the the non-const
      function is called within the patch-loop the event-counter may overflow.
      To resolve this it in necessary to avoid calling the non-const form of
      "boundaryField()" if the results is not altered and cache the reference
      outside the patch-loop when mutation of the patch fields is needed.
      The most straight forward way of resolving this problem is to name the
      const and non-const forms of the member functions differently e.g. the
      non-const form could be named:
      Given that in C++ a reference is non-const unless specified as const:
      "T&" vs "const T&" the logical convention would be
      and given that the const form which is more commonly used is it could
      simply be named "boundaryField()" then the logical convention is
          GeometricBoundaryField& boundaryFieldRef();
          inline const GeometricBoundaryField& boundaryField() const;
      This is also consistent with the new "tmp" class for which non-const
      access to the stored object is obtained using the ".ref()" member function.
      This new convention for non-const access to the components of
      GeometricField will be applied to "dimensionedInternalField()" and "internalField()" in the
      future, i.e. "dimensionedInternalFieldRef()" and "internalFieldRef()".
    • Henry Weller's avatar
    • Henry Weller's avatar
  7. 24 Apr, 2016 2 commits
  8. 23 Apr, 2016 7 commits
    • Henry Weller's avatar
      Updated header · 40ec00b5
      Henry Weller authored
    • Henry Weller's avatar
      boundaryField() -> boundaryFieldRef() · 77cad08d
      Henry Weller authored
    • Henry Weller's avatar
      boundaryField() -> boundaryFieldRef() · 89397e80
      Henry Weller authored
    • Henry Weller's avatar
      GeometricField: New non-const access function boundaryFieldRef() · c25b48a7
      Henry Weller authored
      There is a need to specify const or non-const access to a non-const
      object which is not currently possible with the "boundaryField()" access
      function the const-ness of the return of which is defined by the
      const-ness of the object for which it is called.  For consistency with
      the latest "tmp" storage class in which non-const access is obtained
      with the "ref()" function it is proposed to replace the non-const form
      of "boundaryField()" with "boundaryFieldRef()".
      Thanks to Mattijs Janssens for starting the process of migration to
      "boundaryFieldRef()" and providing a patch for the OpenFOAM and
      finiteVolume libraries.
    • Henry Weller's avatar
      plenumPressureFvPatchScalarField: New plenum pressure boundary condition · b63a532a
      Henry Weller authored
      This condition creates a zero-dimensional model of an enclosed volume of
      gas upstream of the inlet. The pressure that the boundary condition
      exerts on the inlet boundary is dependent on the thermodynamic state of
      the upstream volume.  The upstream plenum density and temperature are
      time-stepped along with the rest of the simulation, and momentum is
      neglected. The plenum is supplied with a user specified mass flow and
      The result is a boundary condition which blends between a pressure inlet
      condition condition and a fixed mass flow. The smaller the plenum
      volume, the quicker the pressure responds to a deviation from the supply
      mass flow, and the closer the model approximates a fixed mass flow. As
      the plenum size increases, the model becomes more similar to a specified
      The expansion from the plenum to the inlet boundary is controlled by an
      area ratio and a discharge coefficient. The area ratio can be used to
      represent further acceleration between a sub-grid blockage such as fins.
      The discharge coefficient represents a fractional deviation from an
      ideal expansion process.
      This condition is useful for simulating unsteady internal flow problems
      for which both a mass flow boundary is unrealistic, and a pressure
      boundary is susceptible to flow reversal. It was developed for use in
      simulating confined combustion.
          helmholtz resonance tutorial case for plenum pressure boundary
      This development was contributed by Will Bainbridge
    • Henry Weller's avatar
      fireFoam: Added optional hydrostatic initialization of the pressure and density · 2c6b4050
      Henry Weller authored
      Also added the new prghTotalHydrostaticPressure p_rgh BC which uses the
      hydrostatic pressure field as the reference state for the far-field
      which provides much more accurate entrainment is large open domains
      typical of many fire simulations.
      The hydrostatic field solution is controlled by the optional entries in
      the fvSolution.PIMPLE dictionary, e.g.
          hydrostaticInitialization yes;
          nHydrostaticCorrectors 5;
      and the solver must also be specified for the hydrostatic p_rgh field
      ph_rgh e.g.
      Suitable boundary conditions for ph_rgh cannot always be derived from
      those for p_rgh and so the ph_rgh is read to provide them.
      To avoid accuracy issues with IO, restart and post-processing the p_rgh
      and ph_rgh the option to specify a suitable reference pressure is
      provided via the optional pRef file in the constant directory, e.g.
          dimensions      [1 -1 -2 0 0 0 0];
          value           101325;
      which is used in the relationship between p_rgh and p:
          p = p_rgh + rho*gh + pRef;
      Note that if pRef is specified all pressure BC specifications in the
      p_rgh and ph_rgh files are relative to the reference to avoid round-off
      For examples of suitable BCs for p_rgh and ph_rgh for a range of
      fireFoam cases please study the tutorials in
      tutorials/combustion/fireFoam/les which have all been updated.
      Henry G. Weller
      CFD Direct Ltd.
    • Henry Weller's avatar
  9. 22 Apr, 2016 3 commits
  10. 21 Apr, 2016 4 commits