1. 31 Oct, 2019 1 commit
  2. 06 Feb, 2019 1 commit
  3. 16 Jul, 2017 2 commits
  4. 19 Jun, 2016 1 commit
  5. 17 Jun, 2016 3 commits
  6. 21 May, 2016 1 commit
    • Henry Weller's avatar
      Standardized the selection of required and optional fields in BCs, fvOptions, functionObjects etc. · 3eec5854
      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.
      3eec5854
  7. 10 Feb, 2016 1 commit
  8. 09 Feb, 2016 1 commit
  9. 08 Feb, 2016 1 commit
    • Henry Weller's avatar
      Rename DataEntry -> Function1 · 968c888f
      Henry Weller authored
      Function1 is an abstract base-class of run-time selectable unary
      functions which may be composed of other Function1's allowing the user
      to specify complex functions of a single scalar variable, e.g. time.
      The implementations need not be a simple or continuous functions;
      interpolated tables and polynomials are also supported.  In fact form of
      mapping between a single scalar input and a single primitive type output
      is supportable.
      
      The primary application of Function1 is in time-varying boundary
      conditions, it also used for other functions of time, e.g. injected mass
      is spray simulations but is not limited to functions of time.
      968c888f
  10. 07 Feb, 2016 1 commit
  11. 10 Jan, 2016 1 commit
  12. 18 May, 2014 1 commit
  13. 24 Sep, 2012 1 commit
  14. 20 Sep, 2012 2 commits
  15. 03 Aug, 2012 1 commit
  16. 19 Jul, 2012 1 commit
  17. 12 Jul, 2012 3 commits
  18. 10 Jul, 2012 1 commit
  19. 06 Jul, 2012 1 commit
  20. 30 May, 2012 1 commit
  21. 02 May, 2012 1 commit
  22. 21 Nov, 2011 1 commit
  23. 14 Aug, 2011 1 commit
  24. 08 Feb, 2011 1 commit
  25. 19 Jan, 2011 1 commit
  26. 07 Jan, 2011 1 commit
  27. 05 Jan, 2011 2 commits
  28. 28 Jul, 2010 1 commit
  29. 18 May, 2010 2 commits
  30. 29 Mar, 2010 1 commit
  31. 31 Dec, 2008 1 commit
  32. 07 Jul, 2008 1 commit