Sub-models, fvOptions: Removed 'active' switch

It is better to not select and instantiate a model, fvOption etc. than to create
it and set it inactive as the creation process requires reading of settings,
parameters, fields etc. with all the associated specification and storage
without being used.  Also the incomplete implementation added a lot of
complexity in the low-level operation of models introducing a significant
maintenance overhead and development overhead for new models.
This commit is contained in:
Henry Weller
2020-12-01 18:50:20 +00:00
parent 3838df8eac
commit 19b3a5c385
152 changed files with 432 additions and 982 deletions

View File

@ -18,7 +18,6 @@ FoamFile
MRF1
{
cellZone rotor;
active yes;
// Fixed patches (by default they 'move' with the MRF zone)
nonRotatingPatches ();

View File

@ -18,7 +18,6 @@ FoamFile
MRF1
{
cellZone rotor;
active yes;
// Fixed patches (by default they 'move' with the MRF zone)
nonRotatingPatches ();

View File

@ -18,7 +18,6 @@ FoamFile
MRF1
{
cellZone rotor;
active yes;
// Fixed patches (by default they 'move' with the MRF zone)
nonRotatingPatches ();

View File

@ -57,7 +57,6 @@ options
limitTsteam
{
type limitTemperature;
active yes;
selectionMode all;
min 270;
max 2000;
@ -67,7 +66,6 @@ options
limitTwater
{
type limitTemperature;
active yes;
selectionMode all;
min 270;
max 2000;

View File

@ -18,7 +18,6 @@ FoamFile
MRF1
{
cellZone rotor;
active yes;
// Fixed patches (by default they 'move' with the MRF zone)
nonRotatingPatches ();