1. 03 Dec, 2018 3 commits
    • Andrew Heather's avatar
      ENH: freestream BC: allow inlet value to be specified by another patch · 31a439dc
      Andrew Heather authored
      The freestreamFvPatchField previously employed a fixed value when supplying
      the inlet values.  This commit extends the BC so that users can use another
      patch to supply the values via the new freestreamBC entry, e.g. to set the
      velocity to an atmospheric boundary layer profile:
              type            freestream;
                  type            atmBoundaryLayerInletVelocity;
                  flowDir         (1 0 0);
                  zDir            (0 0 1);
                  Uref            20;
                  Zref            20;
                  z0              uniform 0.1;
                  zGround         uniform 935;
      The earlier specification is also maintained for backwards compatibility, e.g.
              type            freestream;
              freestreamValue uniform (300 0 0);
    • Mark Olesen's avatar
      CONFIG: adjustments to environment · b8c257d6
      Mark Olesen authored
      - provide default WM_DIR if not already set, to improve robustness if a
        reduced environment is used
      - add etc/ to WM_PROJECT_SITE search. This makes the site directory
        structure consistent with the OpenFOAM structure.
      - Don't set/export WM_OSTYPE.  The default is POSIX and is properly
        defaulted throughout, including in CMakeLists-OpenFOAM.txt (also for
    • mattijs's avatar
      ENH: triSurfaceMesh: improved error message. · e9175865
      mattijs authored
  2. 29 Nov, 2018 1 commit
  3. 02 Dec, 2018 2 commits
    • Mark Olesen's avatar
      ENH: configurable output temperature for externalCoupled mixed T BC (#1072) · 550e4762
      Mark Olesen authored
      - Uses the user-specified value for outputTemperature:
            type  externalCoupledTemperature;
            outputTemperture  fluid;  // or wall;
        Otherwises uses 'wall' as a default (for compatibility) and emits a
        The T.out header now reflects the type of output. Eg,
           # Values: area Tfluid qDot htc
    • Mark Olesen's avatar
      TUT: use defaultPatch for naming instead of explicit Default_Boundary_Region · 1116ba80
      Mark Olesen authored
      - tutorials based on squareBend used Default_Boundary_Region explicitly
        defined since they predated the defaultPatch renaming (2008).
        The name 'Default_Boundary_Region' was for convenience as the default
        name when converting to PROSTAR or CCM formation, but can now be
        changed to something more generic.
      - define wall boundary conditions for squareBend using a general regex
        to allow future splitting of wall types by name.
  4. 30 Nov, 2018 1 commit
    • Mark Olesen's avatar
      ENH: add isTrue function to RunFunctions · c5beee63
      Mark Olesen authored
      - check if the first argument corresponds to an OpenFOAM value for
        'true' (as per Switch).
        True == 't', 'y', 'true', 'yes', 'on'. Everything else is not true.
      - when the first argument is '-dict', it initializes the value
        with a query via foamDictionary.
             isTrue -dict mydict -entry parallel
         ==> value=$(foamDictionary mydict -entry parallel -value)
             isTrue $value
         a missing entry is silently treated as false.
      ENH: add getNumberOfPatchFaces function in RunFunctions
      - simple extraction of nFaces from boundary file for given patch/region
  5. 02 Dec, 2018 1 commit
  6. 29 Nov, 2018 8 commits
    • Mark Olesen's avatar
    • Mark Olesen's avatar
      ENH: append date to build info · d587e2f0
      Mark Olesen authored
      - append the commit hash value with the commit date when creating
        the build string information and drop the version prefix.
        This provides an immediate overview of when the code was last
        changed. The prefixed version information can be dropped from
        the build string, since it is readily available in other forms.
    • Mark Olesen's avatar
      COMP: adjust headers for more detailed build info in the future (issue #1010) · 4b7e11fc
      Mark Olesen authored
      - this splits a larger changeset for a gradual implementation
    • Mark Olesen's avatar
      ENH: relocate WM_PROJECT_SITE default (issue #1050) · 9e094f1f
      Mark Olesen authored
      - was PREFIX/site, now PROJECT/site
        This avoids several issues when installing OpenFOAM in clusters
        without an intermediate OpenFOAM-specific installation prefix.
        The 'site' directory may have a reserved meaning in these situations
        and it is undesirable to 'leak' upwards into the parent directory to
        look for configuration files.
        Placing the default within the project directory avoids this.
        Alternative locations can be given via the WM_PROJECT_SITE variable.
    • Mark Olesen's avatar
      STYLE: adjust wording, file-layout · be46f968
      Mark Olesen authored
      - comments in bashrc, cshrc.
      - about controlDict names for allowSystemOperations
    • Mark Olesen's avatar
      SUBMODULE: catalyst with so versioning · 3f7ea92e
      Mark Olesen authored
    • Mark Olesen's avatar
    • Mark Olesen's avatar
      ENH: improve setup for paraview · 628b2445
      Mark Olesen authored
      - removed reliance on ParaView_INCLUDE_DIR variable for conveying the
        major.minor version information when compiling. This can be somewhat
        fragile and also adds variable that is an unnecessary when running
        (only used when compiling).
        Instead use `have_pvplugin_support` function in paraviewFunctions
        wmake script to determine the maj.min from the PV_PLUGIN_PATH
        since we have already defined the output path there with paraview
        maj.min numbering.
        Can now build with paraview from the operating system,
        provided that it has develop headers available.
        In the etc/config.sh/paraview setup, the maj.min is taken from
        the corresponding `paraview --version` output and used when
        defining the PV_PLUGIN_PATH.
        During the build, the include path taken from `paraview-config`
        for a system installation, from the guess installation root
        of the paraview binary, or ParaView_DIR otherwise.
      NB: using a system ParaView for building runTimePostProcessing is unsupported.
      - these types of builds appear to have various library resolution issues
        (eg, libexpat not being loaded). Additionally, the build logic does
        not yet cover this type of use case.
  7. 28 Nov, 2018 6 commits
  8. 27 Nov, 2018 12 commits
  9. 26 Nov, 2018 3 commits
  10. 25 Nov, 2018 3 commits