Skip to content



The fields declared in a descriptor alias (e.g. AV_SHEAR and FORCE in ShearSmagorinskyForcedD3Q19Descriptor) are primarily for documentation – it only means that those fields will be made available by default. The code would continue to work if you remove or extend this list as “missing” fields are allocated on demand. So from a core perspective you can combine both field lists into a new alias WallFunctionForcedD3Q19Descriptor. However you will still need to set appropriate dynamics and boundary conditions that actually use those fields in the manner that you desire.

Which specific model do you mean by “dynamic smagorinsky”? There are many LES models already available in OpenLB and new ones are easy to add using the tuple-based framework.