ENH: avoid excess boundary evaluation
View options
- Truncate descriptions
Open Issue created
Functionality to add/problem to solve
E.g. in overPimpleDyMFoam/continuityErrs.H is calculates full vol fields but does not use these (weightedAverage is on DimensionedField level). A small benefit can be obtained by operating on the internalField() only - removes e.g. halo-swaps
Target audience
Proposal
Detect where boundary values are not used. In the overset codes one can run with
OptimisationSwitches
{
localConsistency 0;
// Ignore tiny differences due to truncation errors
volScalarField::Boundary::tolerance 1e-10;
volVectorField::Boundary::tolerance 1e-10;
volSphericalTensorField::Boundary::tolerance 1e-10;
volSymmTensorField::Boundary::tolerance 1e-10;
volTensorField::Boundary::tolerance 1e-10;
}
DebugSwitches
{
volScalarField 1;
overset 1;
// Enforce checking
volScalarField::Boundary 1;
volVectorField::Boundary 1;
volSphericalTensorField::Boundary 1;
volSymmTensorField::Boundary 1;
volTensorField::Boundary 1;
}
What does success look like, and how can we measure that?
- Show labels
- Show closed items