Skip to content
Snippets Groups Projects
  1. May 21, 2016
    • Henry Weller's avatar
      Standardized the selection of required and optional fields in BCs, fvOptions, functionObjects etc. · e22c65dd
      Henry Weller authored
      In most boundary conditions, fvOptions etc. required and optional fields
      to be looked-up from the objectRegistry are selected by setting the
      keyword corresponding to the standard field name in the BC etc. to the
      appropriate name in the objectRegistry.  Usually a default is provided
      with sets the field name to the keyword name, e.g. in the
      totalPressureFvPatchScalarField the velocity is selected by setting the
      keyword 'U' to the appropriate name which defaults to 'U':
      
              Property     | Description             | Required    | Default value
              U            | velocity field name     | no          | U
              phi          | flux field name         | no          | phi
              .
              .
              .
      
      However, in some BCs and functionObjects and many fvOptions another
      convention is used in which the field name keyword is appended by 'Name'
      e.g.
      
              Property     | Description             | Required    | Default value
              pName        | pressure field name     | no          | p
              UName        | velocity field name     | no          | U
      
      This difference in convention is unnecessary and confusing, hinders code
      and dictionary reuse and complicates code maintenance.  In this commit
      the appended 'Name' is removed from the field selection keywords
      standardizing OpenFOAM on the first convention above.
      e22c65dd
    • Henry Weller's avatar
      functionObjects, foamCalcFunctions, fvOptions: Standardized keywords for... · 2037fc02
      Henry Weller authored
      functionObjects, foamCalcFunctions, fvOptions: Standardized keywords for selecting fields and objects
      
      Generally fields and objects are selected using the 'field[s]' and
      'object[s]' keywords but this was not consistent between all
      functionObject, fvOptions etc. and now fixed by applying the following
      renaming:
      
      fieldName -> field
      fieldNames -> fields
      objectName -> object
      objectNames -> objects
      2037fc02
  2. May 18, 2016
  3. May 17, 2016
  4. May 16, 2016
  5. May 15, 2016
    • Henry Weller's avatar
      functionObjects: rewritten to all be derived from 'functionObject' · 91aba2db
      Henry Weller authored
        - Avoids the need for the 'OutputFilterFunctionObject' wrapper
        - Time-control for execution and writing is now provided by the
          'timeControlFunctionObject' which instantiates the processing
          'functionObject' and controls its operation.
        - Alternative time-control functionObjects can now be written and
          selected at run-time without the need to compile wrapped version of
          EVERY existing functionObject which would have been required in the
          old structure.
        - The separation of 'execute' and 'write' functions is now formalized in the
          'functionObject' base-class and all derived classes implement the
          two functions.
        - Unnecessary implementations of functions with appropriate defaults
          in the 'functionObject' base-class have been removed reducing
          clutter and simplifying implementation of new functionObjects.
        - The 'coded' 'functionObject' has also been updated, simplified and tested.
        - Further simplification is now possible by creating some general
          intermediate classes derived from 'functionObject'.
      91aba2db
    • Henry Weller's avatar
      Patches contributed by Mattijs Janssens: · 1441f8ca
      Henry Weller authored
      splitMeshRegions: handle flipping of faces for surface fields
      
      subsetMesh: subset dimensionedFields
      
      decomposePar: use run-time selection of decomposition constraints. Used to
          keep cells on particular processors. See the decomposeParDict in
      
      $FOAM_UTILITIES/parallel/decomposePar:
        - preserveBaffles: keep baffle faces on same processor
        - preserveFaceZones: keep faceZones owner and neighbour on same processor
        - preservePatches: keep owner and neighbour on same processor. Note: not
          suitable for cyclicAMI since these are not coupled on the patch level
        - singleProcessorFaceSets: keep complete faceSet on a single processor
        - refinementHistory: keep cells originating from a single cell on the
          same processor.
      
      decomposePar: clean up decomposition of refinement data from snappyHexMesh
      
      reconstructPar: reconstruct refinement data (refineHexMesh, snappyHexMesh)
      
      reconstructParMesh: reconstruct refinement data (refineHexMesh, snappyHexMesh)
      
      redistributePa...
      1441f8ca
  6. May 13, 2016
  7. May 12, 2016
    • Henry Weller's avatar
      Standardized the naming of functions which control the writing of fields etc. · 758dfc2c
      Henry Weller authored
      to have the prefix 'write' rather than 'output'
      
      So outputTime() -> writeTime()
      
      but 'outputTime()' is still supported for backward-compatibility.
      
      Also removed the redundant secondary-writing functionality from Time
      which has been superseded by the 'writeRegisteredObject' functionObject.
      758dfc2c
    • Henry Weller's avatar
      functionObjects: Changed options 'outputControl' -> 'writeControl' and... · 71290b4d
      Henry Weller authored
      functionObjects: Changed options 'outputControl' -> 'writeControl' and 'outputInterval' -> 'writeInterval'
      
      for consistency with the time controls in controlDict and to avoid
      unnecessary confusion.  All code and tutorials have been updated.
      
      The old names 'outputControl' and 'outputInterval' are but supported for
      backward compatibility but deprecated.
      71290b4d
  8. May 11, 2016
  9. May 10, 2016
    • Henry Weller's avatar
    • Henry Weller's avatar
      writeVTK: New functionObject to write fields is VTK format · ad3c8f6d
      Henry Weller authored
      Description
          This functionObject writes objects registered to the database in VTK format
          using the foamToVTK library.
      
          Currently only the writing of the cell-values of volFields is supported but
          support for other field types, patch fields, Lagrangian data etc. will be
          added.
      
          Example of function object specification:
          \verbatim
              writeVTK1
              {
                  type        writeVTK;
                  functionObjectLibs ("libIOFunctionObjects.so");
                  ...
                  objectNames (obj1 obj2);
              }
          \endverbatim
      
          \heading Function object usage
          \table
              Property     | Description             | Required    | Default value
              type         | type name: writeVTK     | yes         |
              objectNames  | objects to write        | yes         |
          \endtable
      ad3c8f6d
  10. May 09, 2016
  11. May 08, 2016
    • Henry Weller's avatar
      4c4f68c2
    • Henry Weller's avatar
      applications/solvers/multiphase: Added -postProcess option · 4cadaeb3
      Henry Weller authored
      See also commit 30e2f912
      4cadaeb3
    • Henry Weller's avatar
    • Henry Weller's avatar
      interFoam: Added -postProcess option · 51281bdf
      Henry Weller authored
      See also commit 30e2f912
      Resolves bug-report http://www.openfoam.org/mantisbt/view.php?id=1301
      51281bdf
    • Henry Weller's avatar
      simpleFoam: Added experimental "-postProcess" option · 30e2f912
      Henry Weller authored
          Executes application functionObjects to post-process existing results.
      
          If the "dict" argument is specified the functionObjectList is constructed
          from that dictionary otherwise the functionObjectList is constructed from
          the "functions" sub-dictionary of "system/controlDict"
      
          Multiple time-steps may be processed and the standard utility time
          controls are provided.
      
      This functionality is equivalent to execFlowFunctionObjects but in a
      more efficient and general manner and will be included in all the
      OpenFOAM solvers if it proves effective and maintainable.
      
      The command-line options available with the "-postProcess" option may be
      obtained by
      
      simpleFoam -help -postProcess
      
      Usage: simpleFoam [OPTIONS]
      options:
        -case <dir>       specify alternate case directory, default is the cwd
        -constant         include the 'constant/' dir in the times list
        -dict <file>      read control dictionary from specified location
        -latestTime       select the latest time
        -newTimes         select the new times
        -noFunctionObjects
                          do not execute functionObjects
        -noZero           exclude the '0/' dir from the times list, has precedence
                          over the -withZero option
        -parallel         run in parallel
        -postProcess      Execute functionObjects only
        -region <name>    specify alternative mesh region
        -roots <(dir1 .. dirN)>
                          slave root directories for distributed running
        -time <ranges>    comma-separated time ranges - eg, ':10,20,40:70,1000:'
        -srcDoc           display source code in browser
        -doc              display application documentation in browser
        -help             print the usage
      
      Henry G. Weller
      CFD Direct Ltd.
      30e2f912
  12. May 06, 2016
  13. May 04, 2016
  14. May 03, 2016
  15. May 02, 2016