[fshak92]

Hi,

Does anybody know what correctBoundaryConditionas does exactly?
It calls three functions, setUpToDate(), storeOldTimes() and evaluate().
I think the first two don't do anything to the vector(scalar)Field, but i want to know what exactly boundaryField_.evaluate() does.
Because the boundary surfaces are always same as the initial boundary condition, regardless of using correctBoundaryConditions or not. If this is true, why we need this function at all?

Thanks in advance.

[kmooney]

Just because you never changed the BC 'type' doesn't mean the BC 'value' doesn't change.

For example, for zeroGradient pressure BC in an unsteady flow over a sphere: its a zeroGrad BC every time step but you re-evaluate (hint:evaluate()) what the surface pressure values are every time step which is more than likely changing.

[superkelle]

Originally Posted by kmooney

Just because you never changed the BC 'type' doesn't mean the BC 'value' doesn't change.

For example, for zeroGradient pressure BC in an unsteady flow over a sphere: its a zeroGrad BC every time step but you re-evaluate (hint:evaluate()) what the surface pressure values are every time step which is more than likely changing.

Maybe a stupid question, sry in advance, when I write my own new application is it mandatory to add this after each fv equation that I solve? Or are there exceptions like for example in special numeric schemes or loops?