ENH: Doxygen docs - using Note instead of \note

This commit is contained in:
andy
2012-08-03 11:43:28 +01:00
parent db306003ab
commit d9912c2003
47 changed files with 88 additions and 91 deletions

View File

@ -57,7 +57,7 @@ Description
refGrad | patch normal gradient | yes | refGrad | patch normal gradient | yes |
\endtable \endtable
\note Note
This condition is not usually applied directly; instead, use a derived This condition is not usually applied directly; instead, use a derived
mixed condition such as \c inletOutlet mixed condition such as \c inletOutlet

View File

@ -31,11 +31,6 @@ Description
This boundary condition enforces a cyclic condition between a pair of This boundary condition enforces a cyclic condition between a pair of
boundaries. boundaries.
\note
The patches must be topologically similar, i.e. if the owner patch is
transformed to the neighbour patch, the patches should be identical (or
very similar).
\heading Patch usage \heading Patch usage
Example of the boundary condition specification: Example of the boundary condition specification:
@ -46,6 +41,11 @@ Description
} }
\endverbatim \endverbatim
Note
The patches must be topologically similar, i.e. if the owner patch is
transformed to the neighbour patch, the patches should be identical (or
very similar).
SourceFiles SourceFiles
cyclicFvPatchField.C cyclicFvPatchField.C

View File

@ -32,11 +32,6 @@ Description
boundaries, whereby communication between the patches is performed using boundaries, whereby communication between the patches is performed using
an arbitrary mesh interface (AMI) interpolation. an arbitrary mesh interface (AMI) interpolation.
\note
The outer boundary of the patch pairs must be similar, i.e. if the owner
patch is transformed to the neighbour patch, the outer perimiter of each
patch should be identical (or very similar).
\heading Patch usage \heading Patch usage
Example of the boundary condition specification: Example of the boundary condition specification:
@ -47,6 +42,11 @@ Description
} }
\endverbatim \endverbatim
Note
The outer boundary of the patch pairs must be similar, i.e. if the owner
patch is transformed to the neighbour patch, the outer perimiter of each
patch should be identical (or very similar).
SeeAlso SeeAlso
Foam::AMIInterpolation Foam::AMIInterpolation

View File

@ -58,22 +58,19 @@ Description
lInf | distance beyond patch for \c fieldInf | no | lInf | distance beyond patch for \c fieldInf | no |
\endtable \endtable
\note
If \c lInf is specified, \c fieldInf will be required; \c rho is only
required in the case of a mass-based flux.
Example of the boundary condition specification: Example of the boundary condition specification:
\verbatim \verbatim
myPatch myPatch
{ {
type advective; type advective;
phi phi; phi phi;
// rho rho; // Not needed for volumetric-based flux
// fieldInf 1e5; // Optional
// lInf 0.1; // Optional
} }
\endverbatim \endverbatim
Note
If \c lInf is specified, \c fieldInf will be required; \c rho is only
required in the case of a mass-based flux.
SourceFiles SourceFiles
advectiveFvPatchField.C advectiveFvPatchField.C

View File

@ -56,7 +56,7 @@ Description
} }
\endverbatim \endverbatim
\note Note
The \c axialVelocity, \c radialVelocity and \c rpm entries are DataEntry The \c axialVelocity, \c radialVelocity and \c rpm entries are DataEntry
types, able to describe time varying functions. The example above gives types, able to describe time varying functions. The example above gives
the usage for supplying constant values. the usage for supplying constant values.

View File

@ -66,7 +66,7 @@ Description
The above example shows the use of a comma separated (CSV) file to specify The above example shows the use of a comma separated (CSV) file to specify
the jump condition. the jump condition.
\note Note
The underlying \c patchType should be set to \c cyclic The underlying \c patchType should be set to \c cyclic
SeeAlso SeeAlso

View File

@ -43,7 +43,7 @@ Description
} }
\endverbatim \endverbatim
\note Note
This is used as a base for conditions such as the turbulence \c epsilon This is used as a base for conditions such as the turbulence \c epsilon
wall function, which applies a near-wall constraint for high Reynolds wall function, which applies a near-wall constraint for high Reynolds
number flows. number flows.

View File

@ -30,7 +30,7 @@ Group
Description Description
Base class for "jump" of a field<type> Base class for "jump" of a field<type>
\note Note
not used directly not used directly
SeeAlso SeeAlso

View File

@ -64,7 +64,7 @@ Description
The \c flowRate entry is a \c DataEntry type, meaning that it can be The \c flowRate entry is a \c DataEntry type, meaning that it can be
specified as constant, a polynomial fuction of time, and ... specified as constant, a polynomial fuction of time, and ...
\note Note
- the value is positive into the domain (as an inlet) - the value is positive into the domain (as an inlet)
- may not work correctly for transonic inlets - may not work correctly for transonic inlets
- strange behaviour with potentialFoam since the U equation is not solved - strange behaviour with potentialFoam since the U equation is not solved

View File

@ -64,7 +64,7 @@ Description
} }
\endverbatim \endverbatim
\note Note
If reverse flow is possible or expected use the If reverse flow is possible or expected use the
pressureInletOutletVelocity condition instead. pressureInletOutletVelocity condition instead.

View File

@ -42,7 +42,7 @@ Description
} }
\endverbatim \endverbatim
\note Note
This condition is designed to operate with a freestream velocity condition This condition is designed to operate with a freestream velocity condition
SeeAlso SeeAlso

View File

@ -53,7 +53,7 @@ Description
The mode of operation is determined by the sign of the flux across the The mode of operation is determined by the sign of the flux across the
patch faces. patch faces.
\note Note
Sign conventions: Sign conventions:
- positive flux (out of domain): apply zero-gradient condition - positive flux (out of domain): apply zero-gradient condition
- negative flux (into of domain): apply the user-specified fixed value - negative flux (into of domain): apply the user-specified fixed value

View File

@ -53,7 +53,7 @@ Description
} }
\endverbatim \endverbatim
\note Note
Since this condition can be applied on a per-field and per-patch basis, Since this condition can be applied on a per-field and per-patch basis,
it is possible to duplicate the mapping information. If possible, employ it is possible to duplicate the mapping information. If possible, employ
the \c mapped condition in preference to avoid this situation, and only the \c mapped condition in preference to avoid this situation, and only

View File

@ -51,7 +51,7 @@ Description
} }
\endverbatim \endverbatim
\note Note
This boundary condition can only be applied to patches that are of This boundary condition can only be applied to patches that are of
the \c mappedPolyPatch type. the \c mappedPolyPatch type.

View File

@ -52,7 +52,7 @@ Description
} }
\endverbatim \endverbatim
\note Note
This boundary condition can only be applied to patches that are of This boundary condition can only be applied to patches that are of
the \c mappedPolyPatch type. the \c mappedPolyPatch type.

View File

@ -65,7 +65,7 @@ Description
boundary faces and both faces sample into the cell, both faces will get the boundary faces and both faces sample into the cell, both faces will get the
same value. same value.
\note Note
It is not possible to sample internal faces since volume fields are not It is not possible to sample internal faces since volume fields are not
defined on faces. defined on faces.

View File

@ -51,7 +51,7 @@ Description
The underlying sample mode should be set to \c nearestPatchFace or The underlying sample mode should be set to \c nearestPatchFace or
\c nearestFace \c nearestFace
\note Note
This boundary condition can only be applied to patches that are of This boundary condition can only be applied to patches that are of
the \c mappedPolyPatch type. the \c mappedPolyPatch type.

View File

@ -68,7 +68,7 @@ Description
} }
\endverbatim \endverbatim
\note Note
The amplitude and frequency entries are DataEntry types, able to describe The amplitude and frequency entries are DataEntry types, able to describe
time varying functions. The example above gives the usage for supplying time varying functions. The example above gives the usage for supplying
constant values. constant values.

View File

@ -53,7 +53,7 @@ Description
The mode of operation is determined by the sign of the flux across the The mode of operation is determined by the sign of the flux across the
patch faces. patch faces.
\note Note
Sign conventions: Sign conventions:
- positive flux (out of domain): apply the user-specified fixed value - positive flux (out of domain): apply the user-specified fixed value
- negative flux (into of domain): apply zero-gradient condition - negative flux (into of domain): apply zero-gradient condition

View File

@ -54,7 +54,7 @@ Description
} }
\endverbatim \endverbatim
\note Note
Sign conventions: Sign conventions:
- positive flux (out of domain): apply zero-gradient condition - positive flux (out of domain): apply zero-gradient condition
- negative flux (into of domain): derive from the flux with specified - negative flux (into of domain): derive from the flux with specified

View File

@ -53,7 +53,7 @@ Description
} }
\endverbatim \endverbatim
\note Note
If reverse flow is possible or expected use the If reverse flow is possible or expected use the
pressureDirectedInletOutletVelocityFvPatchVectorField condition instead. pressureDirectedInletOutletVelocityFvPatchVectorField condition instead.

View File

@ -54,7 +54,7 @@ Description
} }
\endverbatim \endverbatim
\note Note
Sign conventions: Sign conventions:
- positive flux (out of domain): apply zero-gradient condition - positive flux (out of domain): apply zero-gradient condition
- negative flux (into of domain): derive from the flux with specified - negative flux (into of domain): derive from the flux with specified

View File

@ -54,7 +54,7 @@ Description
} }
\endverbatim \endverbatim
\note Note
Sign conventions: Sign conventions:
- positive flux (out of domain): apply zero-gradient condition - positive flux (out of domain): apply zero-gradient condition
- negative flux (into of domain): derive from the flux in the patch-normal - negative flux (into of domain): derive from the flux in the patch-normal

View File

@ -45,7 +45,7 @@ Description
} }
\endverbatim \endverbatim
\note Note
If reverse flow is possible or expected use If reverse flow is possible or expected use
the pressureInletOutletVelocityFvPatchVectorField condition instead. the pressureInletOutletVelocityFvPatchVectorField condition instead.

View File

@ -52,7 +52,7 @@ Description
} }
\endverbatim \endverbatim
\note Note
Sign conventions: Sign conventions:
- positive flux (out of domain): apply zero-gradient condition - positive flux (out of domain): apply zero-gradient condition
- negative flux (into of domain): derive from the flux and patch-normal - negative flux (into of domain): derive from the flux and patch-normal

View File

@ -56,7 +56,7 @@ Description
The \c omega entry is a DataEntry type, able to describe time varying The \c omega entry is a DataEntry type, able to describe time varying
functions. functions.
\note Note
Sign conventions: Sign conventions:
- positive flux (out of domain): apply zero-gradient condition - positive flux (out of domain): apply zero-gradient condition
- negative flux (into of domain): derive from the flux in the patch-normal - negative flux (into of domain): derive from the flux in the patch-normal

View File

@ -58,7 +58,7 @@ Description
} }
\endverbatim \endverbatim
\note Note
This boundary condition is ill-posed if the free-stream flow is normal This boundary condition is ill-posed if the free-stream flow is normal
to the boundary. to the boundary.

View File

@ -47,7 +47,7 @@ Description
} }
\endverbatim \endverbatim
\note Note
Sign conventions: Sign conventions:
- the value is positive for outward-pointing vectors - the value is positive for outward-pointing vectors

View File

@ -57,7 +57,7 @@ Description
} }
\endverbatim \endverbatim
\note Note
- the \c flowRate and \c rpm entries are DataEntry types, able to describe - the \c flowRate and \c rpm entries are DataEntry types, able to describe
time varying functions. The example above gives the usage for supplying time varying functions. The example above gives the usage for supplying
constant values. constant values.

View File

@ -56,7 +56,7 @@ Description
The above example shows the use of a constant jump condition. The above example shows the use of a constant jump condition.
\note Note
The underlying \c patchType should be set to \c cyclic The underlying \c patchType should be set to \c cyclic
SeeAlso SeeAlso

View File

@ -61,7 +61,7 @@ Description
} }
/endverbatim /endverbatim
\note Note
Switch on debug flag to have it dump the triangulation (in transformed Switch on debug flag to have it dump the triangulation (in transformed
space) and transform face centres. space) and transform face centres.

View File

@ -101,9 +101,6 @@ Description
p0 | static pressure reference | yes | p0 | static pressure reference | yes |
\endtable \endtable
\note
The default boundary behaviour is for subsonic, incompressible flow.
Example of the boundary condition specification: Example of the boundary condition specification:
\verbatim \verbatim
myPatch myPatch
@ -118,6 +115,9 @@ Description
} }
\endverbatim \endverbatim
Note
The default boundary behaviour is for subsonic, incompressible flow.
SeeAlso SeeAlso
Foam::fixedValueFvPatchField Foam::fixedValueFvPatchField

View File

@ -46,7 +46,7 @@ Description
} }
\endverbatim \endverbatim
\note Note
The uniformValue entry is a DataEntry type, able to describe time The uniformValue entry is a DataEntry type, able to describe time
varying functions. The example above gives the usage for supplying a varying functions. The example above gives the usage for supplying a
constant value. constant value.

View File

@ -44,9 +44,6 @@ Description
pressure | total pressure as a function of time | yes | pressure | total pressure as a function of time | yes |
\endtable \endtable
\note
The default boundary behaviour is for subsonic, incompressible flow.
Example of the boundary condition specification: Example of the boundary condition specification:
\verbatim \verbatim
myPatch myPatch
@ -62,10 +59,13 @@ Description
} }
\endverbatim \endverbatim
The \c pressure entry is specified as a DataEntry type, able to describe The \c pressure entry is specified as a DataEntry type, able to describe
time varying functions. time varying functions.
Note
The default boundary behaviour is for subsonic, incompressible flow.
SeeAlso SeeAlso
Foam::DataEntry Foam::DataEntry
Foam::uniformFixedValueFvPatchField Foam::uniformFixedValueFvPatchField

View File

@ -51,7 +51,7 @@ Description
} }
\endverbatim \endverbatim
\note Note
- the value is positive into the domain - the value is positive into the domain
- may not work correctly for transonic inlets - may not work correctly for transonic inlets
- strange behaviour with potentialFoam since the momentum equation is - strange behaviour with potentialFoam since the momentum equation is

View File

@ -44,9 +44,6 @@ Description
- base: average over 'time', or 'iteration' (\f$N\f$ in the above) - base: average over 'time', or 'iteration' (\f$N\f$ in the above)
- window: optional averaging window, specified in 'base' units - window: optional averaging window, specified in 'base' units
\note
To employ the \c prime2Mean option, the \c mean option must be selecetd.
Average field names are constructed by concatenating the base field with Average field names are constructed by concatenating the base field with
the averaging type, e.g. when averaging field 'U', the resultant fields the averaging type, e.g. when averaging field 'U', the resultant fields
are: are:
@ -99,6 +96,9 @@ Description
} }
\endverbatim \endverbatim
Note
To employ the \c prime2Mean option, the \c mean option must be selecetd.
SourceFiles SourceFiles
fieldAverage.C fieldAverage.C
fieldAverageTemplates.C fieldAverageTemplates.C

View File

@ -74,7 +74,7 @@ Description
For example, to calculate the volumetric or mass flux across a patch, For example, to calculate the volumetric or mass flux across a patch,
apply the 'sum' operator to the flux field (typically \c phi) apply the 'sum' operator to the flux field (typically \c phi)
\note Note
- faces on empty patches get ignored - faces on empty patches get ignored
- if the field is a volField the \c faceZone can only consist of boundary - if the field is a volField the \c faceZone can only consist of boundary
faces faces

View File

@ -46,9 +46,6 @@ Description
L | length scale L | length scale
\endvartable \endvartable
\note
In the event of reverse flow, a zero-gradient condition is applied
\heading Patch usage \heading Patch usage
\table \table
@ -68,6 +65,9 @@ Description
} }
\endverbatim \endverbatim
Note
In the event of reverse flow, a zero-gradient condition is applied
SeeAlso SeeAlso
Foam::inletOutletFvPatchField Foam::inletOutletFvPatchField

View File

@ -45,9 +45,6 @@ Description
L | length scale L | length scale
\endvartable \endvartable
\note
In the event of reverse flow, a zero-gradient condition is applied
\heading Patch usage \heading Patch usage
\table \table
@ -67,6 +64,9 @@ Description
} }
\endverbatim \endverbatim
Note
In the event of reverse flow, a zero-gradient condition is applied
SeeAlso SeeAlso
Foam::inletOutletFvPatchField Foam::inletOutletFvPatchField

View File

@ -55,8 +55,8 @@ Description
} }
\endverbatim \endverbatim
\note Note
Only supply \h an \c Ta, or \c q in the dictionary (see above) Only supply \c h and \c Ta, or \c q in the dictionary (see above)
SourceFiles SourceFiles
externalWallHeatFluxTemperatureFvPatchScalarField.C externalWallHeatFluxTemperatureFvPatchScalarField.C

View File

@ -73,7 +73,7 @@ Description
} }
\endverbatim \endverbatim
\note Note
The underlying \c patchType should be set to \c cyclic The underlying \c patchType should be set to \c cyclic
SourceFiles SourceFiles

View File

@ -64,12 +64,6 @@ Description
layer", Journal of Wind Engineering and Industrial Aerodynamics layer", Journal of Wind Engineering and Industrial Aerodynamics
95(2007), pp 355-369. 95(2007), pp 355-369.
\note
D.M. Hargreaves and N.G. Wright recommend Gamma epsilon in the
k-epsilon model should be changed from 1.3 to 1.11 for consistency.
The roughness height (Er) is given by Er = 20 z0 following the same
reference.
\heading Patch usage \heading Patch usage
\table \table
@ -98,6 +92,12 @@ Description
} }
\endverbatim \endverbatim
Note
D.M. Hargreaves and N.G. Wright recommend Gamma epsilon in the
k-epsilon model should be changed from 1.3 to 1.11 for consistency.
The roughness height (Er) is given by Er = 20 z0 following the same
reference.
SourceFiles SourceFiles
atmBoundaryLayerInletVelocityFvPatchVectorField.C atmBoundaryLayerInletVelocityFvPatchVectorField.C

View File

@ -41,11 +41,6 @@ Description
alphaEff | turbulent thermal diffusivity field name | yes | alphaEff | turbulent thermal diffusivity field name | yes |
\endtable \endtable
\note
- it is assumed that the units of \c alphaEff are [kg/m/s]
- the specific heat capcaity is read from the transport dictionary entry
\c Cp0
Example of the boundary condition specification: Example of the boundary condition specification:
\verbatim \verbatim
myPatch myPatch
@ -58,6 +53,11 @@ Description
} }
\endverbatim \endverbatim
Note
- it is assumed that the units of \c alphaEff are [kg/m/s]
- the specific heat capcaity is read from the transport dictionary entry
\c Cp0
SourceFiles SourceFiles
turbulentHeatFluxTemperatureFvPatchScalarField.C turbulentHeatFluxTemperatureFvPatchScalarField.C

View File

@ -46,9 +46,6 @@ Description
L | length scale L | length scale
\endvartable \endvartable
\note
In the event of reverse flow, a zero-gradient condition is applied
\heading Patch usage \heading Patch usage
\table \table
@ -68,6 +65,9 @@ Description
} }
\endverbatim \endverbatim
Note
In the event of reverse flow, a zero-gradient condition is applied
SeeAlso SeeAlso
Foam::inletOutletFvPatchField Foam::inletOutletFvPatchField

View File

@ -45,9 +45,6 @@ Description
L | length scale L | length scale
\endvartable \endvartable
\note
In the event of reverse flow, a zero-gradient condition is applied
\heading Patch usage \heading Patch usage
\table \table
@ -67,6 +64,9 @@ Description
} }
\endverbatim \endverbatim
Note
In the event of reverse flow, a zero-gradient condition is applied
SeeAlso SeeAlso
Foam::inletOutletFvPatchField Foam::inletOutletFvPatchField

View File

@ -32,9 +32,6 @@ Description
This boundary condition provides a kinematic turbulent thermal conductivity This boundary condition provides a kinematic turbulent thermal conductivity
for using wall functions, using the Jayatilleke 'P' function. for using wall functions, using the Jayatilleke 'P' function.
\note
The units of kinematic turbulent thermal conductivity are m2/s
\heading Patch usage \heading Patch usage
\table \table
@ -53,6 +50,9 @@ Description
} }
\endverbatim \endverbatim
Note
The units of kinematic turbulent thermal conductivity are [m2/s]
SeeAlso SeeAlso
Foam::fixedValueFvPatchField Foam::fixedValueFvPatchField

View File

@ -33,10 +33,6 @@ Description
of U+ as a function of near-wall Reynolds number. The table should be of U+ as a function of near-wall Reynolds number. The table should be
located in the $FOAM_CASE/constant folder. located in the $FOAM_CASE/constant folder.
\note
the tables are not registered since the same table object may be used for
more than one patch.
\heading Patch usage \heading Patch usage
\table \table
@ -53,6 +49,10 @@ Description
} }
\endverbatim \endverbatim
Note
The tables are not registered since the same table object may be used for
more than one patch.
SeeAlso SeeAlso
Foam::nutWallFunctionFvPatchScalarField Foam::nutWallFunctionFvPatchScalarField