1. 02 Jun, 2020 1 commit
    • Mark Olesen's avatar
      ENH: unify use of dictionary method names · 3e43edf0
      Mark Olesen authored
      - previously introduced `getOrDefault` as a dictionary _get_ method,
        now complete the transition and use it everywhere instead of
        `lookupOrDefault`. This avoids mixed usage of the two methods that
        are identical in behaviour, makes for shorter names, and promotes
        the distinction between "lookup" access (ie, return a token stream,
        locate and return an entry) and "get" access (ie, the above with
        conversion to concrete types such as scalar, label etc).
      3e43edf0
  2. 31 Oct, 2019 1 commit
  3. 06 Feb, 2019 1 commit
  4. 11 Dec, 2018 1 commit
    • Mark Olesen's avatar
      ENH: use Zero when zero-initializing types · 1d85fecf
      Mark Olesen authored
      - makes the intent clearer and avoids the need for additional
        constructor casting. Eg,
      
            labelList(10, Zero)    vs.  labelList(10, 0)
            scalarField(10, Zero)  vs.  scalarField(10, scalar(0))
            vectorField(10, Zero)  vs.  vectorField(10, vector::zero)
      1d85fecf
  5. 12 Oct, 2018 1 commit
    • Mark Olesen's avatar
      ENH: avoid readScalar, readLabel etc from dictionary (#762, #1033) · 8eddcc07
      Mark Olesen authored
      - use the dictionary 'get' methods instead of readScalar for
        additional checking
      
           Unchecked:  readScalar(dict.lookup("key"));
           Checked:    dict.get<scalar>("key");
      
      - In templated classes that also inherit from a dictionary, an additional
        'template' keyword will be required. Eg,
      
           this->coeffsDict().template get<scalar>("key");
      
        For this common use case, the predefined getXXX shortcuts may be
        useful. Eg,
      
           this->coeffsDict().getScalar("key");
      8eddcc07
  6. 05 Nov, 2017 1 commit
  7. 22 Jun, 2017 1 commit
    • Henry Weller's avatar
      Rationalize the "pos" function · 56bfc759
      Henry Weller authored
      "pos" now returns 1 if the argument is greater than 0, otherwise it returns 0.
      This is consistent with the common mathematical definition of the "pos" function:
      
      https://en.wikipedia.org/wiki/Sign_(mathematics)
      
      However the previous implementation in which 1 was also returned for a 0
      argument is useful in many situations so the "pos0" has been added which returns
      1 if the argument is greater or equal to 0.  Additionally the "neg0" has been
      added which returns 1 if if the argument is less than or equal to 0.
      56bfc759
  8. 25 Sep, 2016 1 commit
  9. 16 Jun, 2016 1 commit
    • Henry Weller's avatar
      totalPressureFvPatchScalarField, uniformTotalPressureFvPatchScalarField:... · 64aa9925
      Henry Weller authored
      totalPressureFvPatchScalarField, uniformTotalPressureFvPatchScalarField: simplified and rationalized
      
          The modes of operation are set by the dimensions of the pressure field
          to which this boundary condition is applied, the \c psi entry and the value
          of \c gamma:
          \table
              Mode                    | dimensions | psi   | gamma
              incompressible subsonic | p/rho      |       |
              compressible subsonic   | p          | none  |
              compressible transonic  | p          | psi   | 1
              compressible supersonic | p          | psi   | > 1
          \endtable
      
          For most applications the totalPressure boundary condition now only
          requires p0 to be specified e.g.
          outlet
          {
              type            totalPressure;
              p0              uniform 1e5;
          }
      64aa9925
  10. 30 Apr, 2016 2 commits
    • Henry Weller's avatar
      Updated headers · 81f31acb
      Henry Weller authored
      81f31acb
    • Henry Weller's avatar
      GeometricField: Renamed internalField() -> primitiveField() and... · 3c053c2f
      Henry Weller authored
      GeometricField: Renamed internalField() -> primitiveField() and dimensionedInternalField() -> internalField()
      
      These new names are more consistent and logical because:
      
      primitiveField():
      primitiveFieldRef():
          Provides low-level access to the Field<Type> (primitive field)
          without dimension or mesh-consistency checking.  This should only be
          used in the low-level functions where dimensional consistency is
          ensured by careful programming and computational efficiency is
          paramount.
      
      internalField():
      internalFieldRef():
          Provides access to the DimensionedField<Type, GeoMesh> of values on
          the internal mesh-type for which the GeometricField is defined and
          supports dimension and checking and mesh-consistency checking.
      3c053c2f
  11. 10 Nov, 2015 1 commit
  12. 14 Aug, 2011 1 commit
  13. 04 Jul, 2011 2 commits
  14. 19 Jan, 2011 1 commit
  15. 14 Jan, 2011 1 commit
  16. 07 Jan, 2011 1 commit
  17. 05 Jan, 2011 2 commits
  18. 30 Dec, 2010 1 commit
  19. 17 Dec, 2010 1 commit
  20. 28 Jul, 2010 1 commit
  21. 29 Mar, 2010 1 commit
  22. 26 Jun, 2009 1 commit
  23. 26 Mar, 2009 1 commit
  24. 27 Feb, 2009 1 commit
  25. 19 Feb, 2009 1 commit
  26. 31 Dec, 2008 1 commit
  27. 19 Sep, 2008 2 commits
  28. 25 Jun, 2008 2 commits
  29. 15 Apr, 2008 1 commit