Limiting the pressure (p or p_rgh) as an fvOption entry rather than having it in the fvSolutions file
Functionality to add/problem to solve
For compressible flows it might be beneficial to limit the pressure values to some defined ranges in order to avoid non-physical behavior such as negative pressure or values which will never occur in the simulation one is performing. E.g., external aerodynamics might have a defined range around the atmospheric pressure value but will never get negative or too high.
We can limit the pressure values by using the pMin and pMax keywords inside the system/fvSolutions subDict (SIMPLE/PIMPLE/PISO) but personally, I would prefer to have some fvOption model that takes care of that such as the limitVelocity or limitTemperature. That would unify the code and we would have everything in one place.
Checking our actual implementation of the pMin and pMax results in the pressureControl class. So its implemented but maybe it would make sense to change it to be used with the fvOptions file?
Target audience
As we have already an working implementation, probably no-one. However, we would have limitVelocity, limitPressure as well as limitTemperature in one place.
Proposal
Its already implemented in the .org version. https://github.com/OpenFOAM/OpenFOAM-dev/tree/master/src/fvConstraints/limitPressure
What does success look like, and how can we measure that?
Success: Probably having all "limiting" constraints in one file (fvOptions) rather than split into fvSolution and fvOptions.
Links / references
https://github.com/OpenFOAM/OpenFOAM-dev/commit/ab7d010a9aa91576a93ed7b09bb0f4e607a0fbd8
Funding
Functionality already exist in the .org version.