openfoam/applications/solvers/heatTransfer
Mark Olesen 2f86cdc712 STYLE: more consistent use of dimensioned Zero
- when constructing dimensioned fields that are to be zero-initialized,
  it is preferrable to use a form such as

      dimensionedScalar(dims, Zero)
      dimensionedVector(dims, Zero)

  rather than

      dimensionedScalar("0", dims, 0)
      dimensionedVector("zero", dims, vector::zero)

  This reduces clutter and also avoids any suggestion that the name of
  the dimensioned quantity has any influence on the field's name.

  An even shorter version is possible. Eg,

      dimensionedScalar(dims)

  but reduces the clarity of meaning.

- NB: UniformDimensionedField is an exception to these style changes
  since it does use the name of the dimensioned type (instead of the
  regIOobject).
2018-03-16 10:24:03 +01:00
..
buoyantBoussinesqPimpleFoam GIT: Initial state after latest Foundation merge 2016-09-20 14:49:08 +01:00
buoyantBoussinesqSimpleFoam GIT: Initial state after latest Foundation merge 2016-09-20 14:49:08 +01:00
buoyantPimpleFoam ENH: Updated dpdt and K field construction 2017-06-21 12:20:58 +01:00
buoyantSimpleFoam Fixing externalWallHeatFluxTemperature mapping scalarFields. 2017-06-14 13:58:52 -07:00
chtMultiRegionFoam STYLE: more consistent use of dimensioned Zero 2018-03-16 10:24:03 +01:00
thermoFoam BUG: thermoFoam - corrected to enable restart and post-processing using thermoFoam -postProcess. Fixes #598 2017-09-25 13:25:34 +01:00
heatTransferSolversDoc.H ENH: Solvers - updated group documentation 2015-12-03 22:05:55 +00:00