fvConstraints: Remove 'Constraint' from constraint names

The fact that these names refer to constraints is clear in context, so
the name does not need to contain 'Constraint'.

Having 'Constraint' in the name is a historic convention that dates back
to when fvConstraints and fvModels were combined in a single fvOptions
interface. In this interface, disambiguation between sources and
constraints was necessary.

This change has been applied to the 'fixedValue' and 'fixedTemperature'
constraints, which were formerly named 'fixedValueConstraint' and
'fixedTemperatureConstraint', respectively.

The old names are still available for backwards compatibility.
This commit is contained in:
Will Bainbridge
2023-10-12 15:25:47 +01:00
parent ad3d25dc30
commit 16ecc4fe08
12 changed files with 70 additions and 61 deletions

View File

@ -4,9 +4,7 @@ cd ${0%/*} || exit 1 # Run from this directory
# Source tutorial run functions
. $WM_PROJECT_DIR/bin/tools/RunFunctions
application=$(getApplication)
runApplication blockMesh -dict $FOAM_TUTORIALS/resources/blockMesh/angledDuct
runApplication $application
runApplication $(getApplication)
#------------------------------------------------------------------------------

View File

@ -24,7 +24,7 @@ limitp
fixedTemperature
{
type fixedTemperatureConstraint;
type fixedTemperature;
cellZone porosity;
@ -32,10 +32,9 @@ fixedTemperature
temperature 350;
}
porosityTurbulence
{
type fixedValueConstraint;
type fixedValue;
cellZone porosity;

View File

@ -24,7 +24,7 @@ limitp
source1
{
type fixedTemperatureConstraint;
type fixedTemperature;
cellZone porosity;

View File

@ -16,7 +16,8 @@ FoamFile
/*
fixedTemperature
{
type fixedTemperatureConstraint;
type fixedTemperature;
select all;
mode uniform;

View File

@ -16,7 +16,7 @@ FoamFile
ignition
{
type fixedTemperatureConstraint;
type fixedTemperature;
cellSet ignition;

View File

@ -16,7 +16,7 @@ FoamFile
source1
{
type fixedTemperatureConstraint;
type fixedTemperature;
timeStart 0.1;
duration 0.4;