v2306: New and improved post-processing
TOP
The Lagrangian cloud function objects have received multiple updates:
- patchPostProcessing and patchParticleHistogram have been renamed particlePostProcessing and particleHistogram, respectively, to better reflect their functionality;
- writeFile support has been added for improved control over file output; and
- faceZone support has been added for improved control over particle collection.
A minimal example usage follows:
ParticlePostProcessing1
{
// Mandatory entries
type particlePostProcessing;
maxStoredParcels <scalar>;
// Optional entries
fields (<wordRes>);
// Conditional entries
// Option-1
patches (<wordRes>);
// Option-2
faceZones (<wordRes>);
// Inherited entries
// writeFile entries
...
}
particleHistogram1
{
// Mandatory entries
type particleHistogram;
nBins <label>;
min <scalar>;
max <scalar>;
maxStoredParcels <scalar>;
// Conditional entries
// Option-1
patches (<wordRes>);
// Option-2
faceZones (<wordRes>);
// Inherited entries
// writeFile entries
...
}
Source code
- $FOAM_SRC/lagrangian/intermediate/submodels/CloudFunctionObjects/ParticleHistogram
- $FOAM_SRC/lagrangian/intermediate/submodels/CloudFunctionObjects/ParticlePostProcessing
Merge request
TOP
The forces and forceCoeffs function objects have been optimised to reduce run times.
Tests indicated that employing multiple forces and forceCoeffs function objects previously caused slowdowns in the range of 2-10% total run time, largely due to the calculation of velocity gradients and redundant computations performed for various internal fields.
For example, tests on the simpleCar tutorial, when complemented by caching the velocity gradient, demonstrated that the execution time of the forces function object reduced by a factor of approximately three.
Source code
Merge request