1. 25 Jan, 2019 1 commit
  2. 18 Oct, 2018 1 commit
    • Mark OLESEN's avatar
      ENH: cleanup of Enum class · 3b745122
      Mark OLESEN authored
      - more dictionary-like methods, enforce keyType::LITERAL for all
        lookups to avoid any spurious keyword matching.
      
      - new readEntry, readIfPresent methods
      
      - The get() method replaces the now deprecate lookup() method.
      
      - Deprecate lookupOrFailsafe()
        Failsafe behaviour is now an optional parameter for lookupOrDefault,
        which makes it easier to tailor behaviour at runtime.
      
      - output of the names is now always flatted without line-breaks.
        Thus,
      
           os << flatOutput(someEnumNames.names()) << nl;
           os << someEnumNames << nl;
      
        both generate the same output.
      
      - Constructor now uses C-string (const char*) directly instead of
        Foam::word in its initializer_list.
      
      - Remove special enum + initializer_list constructor form since
        it can create unbounded lookup indices.
      
      - Removd old hasEnum, hasName forms that were provided during initial
        transition from NamedEnum.
      
      - Added static_assert on Enum contents to restrict to enum or
        integral values.  Should not likely be using this class to enumerate
        other things since it internally uses an 'int' for its values.
      
        Changed volumeType accordingly to enumerate on its type (enum),
        not the class itself.
      3b745122
  3. 03 Aug, 2018 1 commit
  4. 21 Feb, 2018 1 commit
  5. 03 Jul, 2017 1 commit
  6. 29 May, 2017 1 commit
    • Mark OLESEN's avatar
      ENH: cleanup of NamedEnum · fb497164
      Mark OLESEN authored
      - Remove the unused enums() method since it delivers wholly unreliable
        results. It is not guaranteed to cover the full enumeration range,
        but only the listed names.
      
      - Remove the unused strings() method.
        Duplicated functionality of the words(), but was never used.
      
      - Change access of words() method from static to object.
        Better code isolation. Permits the constructor to take over
        as the single point of failure for bad input.
      
      - Add values() method
      
      - do not expose internal (HashTable) lookup since it makes it more
        difficult to enforce constness and the implementation detail should
        not be exposed. However leave toc() and sortedToc() for the interface.
      
      STYLE: relocated NamedEnum under primitives (was containers)
      
      - internal typedef as 'value_type' for some consistency with STL conventions
      fb497164
  7. 09 Dec, 2016 1 commit
  8. 30 Sep, 2016 1 commit
  9. 18 Aug, 2016 1 commit
  10. 17 Aug, 2016 1 commit
  11. 16 Aug, 2016 1 commit
    • Henry Weller's avatar
      functionObjects::writeObjects: Added option "writeOption" · 9a739863
      Henry Weller authored
      Description
          Allows specification of different writing frequency of objects registered
          to the database.
      
          It has similar functionality as the main time database through the
          \c writeControl setting:
            - timeStep
            - writeTime
            - adjustableRunTime
            - runTime
            - clockTime
            - cpuTime
      
          It also has the ability to write the selected objects that were defined
          with the respective write mode for the requested \c writeOption, namely:
            - \c autoWrite - objects set to write at output time
            - \c noWrite   - objects set to not write by default
            - \c anyWrite  - any option of the previous two
      
          Example of function object specification:
          \verbatim
          writeObjects1
          {
              type        writeObjects;
              libs        ("libutilityFunctionObjects.so");
              ...
              objects     (obj1 obj2);
              writeOption anyWrite;
          }
          \endverbatim
      
      Patch contributed by Bruno Santos
      Resolves bug-report http://bugs.openfoam.org/view.php?id=2090
      9a739863
  12. 13 Jun, 2016 1 commit
  13. 10 Jun, 2016 1 commit
  14. 09 Jun, 2016 1 commit
  15. 28 May, 2016 1 commit
    • Henry Weller's avatar
      postProcessing: Replaced 'foamCalc' and the 'postCalc' utilities · e4dc50dc
      Henry Weller authored
      with the more general and flexible 'postProcess' utility and '-postProcess' solver option
      
      Rationale
      ---------
      
      Both the 'postProcess' utility and '-postProcess' solver option use the
      same extensive set of functionObjects available for data-processing
      during the run avoiding the substantial code duplication necessary for
      the 'foamCalc' and 'postCalc' utilities and simplifying maintenance.
      Additionally consistency is guaranteed between solver data processing
      and post-processing.
      
      The functionObjects have been substantially re-written and generalized
      to simplify development and encourage contribution.
      
      Configuration
      -------------
      
      An extensive set of simple functionObject configuration files are
      provided in
      
      OpenFOAM-dev/etc/caseDicts/postProcessing
      
      and more will be added in the future.  These can either be copied into
      '<case>/system' directory and included into the 'controlDict.functions'
      sub-dictionary or included directly from 'etc/caseDicts/postProcessing'
      using the '#includeEtc' directive or the new and more convenient
      '#includeFunc' directive which searches the
      '<etc>/caseDicts/postProcessing' directories for the selected
      functionObject, e.g.
      
      functions
      {
          #includeFunc Q
          #includeFunc Lambda2
      }
      
      '#includeFunc' first searches the '<case>/system' directory in case
      there is a local configuration.
      
      Description of #includeFunc
      ---------------------------
      
          Specify a functionObject dictionary file to include, expects the
          functionObject name to follow (without quotes).
      
          Search for functionObject dictionary file in
          user/group/shipped directories.
          The search scheme allows for version-specific and
          version-independent files using the following hierarchy:
          - \b user settings:
            - ~/.OpenFOAM/\<VERSION\>/caseDicts/postProcessing
            - ~/.OpenFOAM/caseDicts/postProcessing
          - \b group (site) settings (when $WM_PROJECT_SITE is set):
            - $WM_PROJECT_SITE/\<VERSION\>/caseDicts/postProcessing
            - $WM_PROJECT_SITE/caseDicts/postProcessing
          - \b group (site) settings (when $WM_PROJECT_SITE is not set):
            - $WM_PROJECT_INST_DIR/site/\<VERSION\>/caseDicts/postProcessing
            - $WM_PROJECT_INST_DIR/site/caseDicts/postProcessing
          - \b other (shipped) settings:
            - $WM_PROJECT_DIR/etc/caseDicts/postProcessing
      
          An example of the \c \#includeFunc directive:
          \verbatim
              #includeFunc <funcName>
          \endverbatim
      
      postProcess
      -----------
      
      The 'postProcess' utility and '-postProcess' solver option provide the
      same set of controls to execute functionObjects after the run either by
      reading a specified set of fields to process in the case of
      'postProcess' or by reading all fields and models required to start the
      run in the case of '-postProcess' for each selected time:
      
      postProcess -help
      
      Usage: postProcess [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
        -field <name>     specify the name of the field to be processed, e.g. U
        -fields <list>    specify a list of fields to be processed, e.g. '(U T p)' -
                          regular expressions not currently supported
        -func <name>      specify the name of the functionObject to execute, e.g. Q
        -funcs <list>     specify the names of the functionObjects to execute, e.g.
                          '(Q div(U))'
        -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
        -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
      
       pimpleFoam -postProcess -help
      
      Usage: pimpleFoam [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
        -field <name>     specify the name of the field to be processed, e.g. U
        -fields <list>    specify a list of fields to be processed, e.g. '(U T p)' -
                          regular expressions not currently supported
        -func <name>      specify the name of the functionObject to execute, e.g. Q
        -funcs <list>     specify the names of the functionObjects to execute, e.g.
                          '(Q div(U))'
        -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
      
      The functionObjects to execute may be specified on the command-line
      using the '-func' option for a single functionObject or '-funcs' for a
      list, e.g.
      
      postProcess -func Q
      postProcess -funcs '(div(U) div(phi))'
      
      In the case of 'Q' the default field to process is 'U' which is
      specified in and read from the configuration file but this may be
      overridden thus:
      
      postProcess -func 'Q(Ua)'
      
      as is done in the example above to calculate the two forms of the divergence of
      the velocity field.  Additional fields which the functionObjects may depend on
      can be specified using the '-field' or '-fields' options.
      
      The 'postProcess' utility can only be used to execute functionObjects which
      process fields present in the time directories.  However, functionObjects which
      depend on fields obtained from models, e.g. properties derived from turbulence
      models can be executed using the '-postProcess' of the appropriate solver, e.g.
      
      pisoFoam -postProcess -func PecletNo
      
      or
      
      sonicFoam -postProcess -func MachNo
      
      In this case all required fields will have already been read so the '-field' or
      '-fields' options are not be needed.
      
      Henry G. Weller
      CFD Direct Ltd.
      e4dc50dc
  16. 21 May, 2016 1 commit
    • Henry Weller's avatar
      functionObjects, foamCalcFunctions, fvOptions: Standardized keywords for... · f5ce4306
      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
      f5ce4306
  17. 17 May, 2016 1 commit
  18. 15 May, 2016 1 commit
    • Henry Weller's avatar
      functionObjects: rewritten to all be derived from 'functionObject' · 78d2971b
      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'.
      78d2971b
  19. 11 May, 2016 1 commit
  20. 03 May, 2016 1 commit
  21. 02 May, 2016 1 commit
    • Henry Weller's avatar
      functionObjects: Moved into the functionObjects namespace and rationalized and... · 0534a225
      Henry Weller authored
      functionObjects: Moved into the functionObjects namespace and rationalized and simplified failable construction
      
      Rather than requiring each functionObject to handle failed construction
      internally (using the active_ flag) the static member function "viable"
      is provided which returns true if construction of the functionObject is
      likely to be successful.  Failed construction is then handled by the
      wrapper-class which constructs the functionObject,
      e.g. "OutputFilterFunctionObject".
      0534a225
  22. 01 May, 2016 1 commit
  23. 25 Nov, 2015 1 commit
    • Andrew Heather's avatar
      ENH: Multiple updates to function objects · 6838df9c
      Andrew Heather authored
      Updated objects
      - corrected Peclet number for compressible cases
      - propagated log flag and resultName across objects
      
      New function objects
      - new fluxSummary:
        - calculates positive, negative, absolute and net flux across face
          zones
      - new runTimeControl
        - abort the calculation when a user-defined metric is achieved.
          Available options include:
          - average value remains unchanged wrt a given threshold
          - equation initial residual exceeds a threshold - useful to abort
            diverging cases
          - equation max iterations exceeds a threshold - useful to abort
            diverging cases
          - min/max of a function object value
          - min time step exceeds a threshold - useful to abort diverging
            cases
      - new valueAverage:
        - average singular values from other function objects, e.g. Cd, Cl and
          Cm from the forceCoeffs function object
      6838df9c
  24. 11 Nov, 2015 1 commit
  25. 11 Oct, 2013 1 commit
  26. 04 Oct, 2013 1 commit
  27. 12 Sep, 2013 1 commit
  28. 09 Sep, 2013 1 commit
  29. 14 Aug, 2013 1 commit
  30. 07 Jun, 2013 1 commit
  31. 17 Dec, 2012 1 commit
  32. 05 Mar, 2012 2 commits
  33. 14 Aug, 2011 1 commit
  34. 20 May, 2011 1 commit
  35. 11 May, 2011 1 commit
  36. 19 Jan, 2011 1 commit
  37. 14 Jan, 2011 1 commit
  38. 07 Jan, 2011 1 commit
  39. 05 Jan, 2011 1 commit