[Gerry Kan]

Howdy folks:

This question might seem a bit odd, but here it goes.

I implemented a boundary condition which updates the scalar / vector values of selected boundaries at regular simulated time intervals by reading an external file. While the BC picks up the external file at the correct times, I noticed that it rereads the file at every outer (PIMPLE) and inner (pressure correction) iteration during that time step.

The natural to do, I suppose, is to pass some kind of counter or flag, which tells the boundary condition whether the solver is at its first outer and inner iterations, thus signalling the boundary to read the external file at that time.

There is a certain "global" registry called "db" in the fvPatchField, from which I can access some global states from the solver (e.g., runtime), but I don't know whether I can introduce new objects / variables into the db object, or better, obtain information about the solver's state (i.e., inner / outer loop iteration count) from there.

Any insight on this would be greatly appreciated.

Gerry.

[Gerry Kan]

I figured it out, and it is quite straightforward. It appears that any global variable will have visibility from all modules.

Having said that, I have compiled and linked the boundary condition into the solver, i.e., the .so for the BC is referenced in Make/options under the solver's source code directory. I don't know if the same applies if the .so is loaded at runtime into the solver as a. function object.

Gerry.