|August 19, 2008, 07:08||
Hello everyone! What is the
What is the recommended approach to handle "global" variables? For example a vector U0 which is calculated in a solvers main() function, but which is also required (and maybe modified) when boundary conditions are evaluated in a class myFvPatchField?
In order to avoid global variables I would assume that passing U0 through an objectRegistry, known to both main() and myFvPatchField, could be a common solution. If not, what else would you suggest?
Assuming myFvPatchField has a member variable mesh _ containing this objectRegistry, I can get retrieve U0 inside myFvPatchField with
But how do I get U0 *into* the objectRegistry mesh at the main() side? It must be something like
But I can't get sorted out how to use the regIOobject, IOobject, objectRegistry and IOdictionary in the correct way, because their interrelationship isn't clear to me.
Any hints how the ...checkIn... line has to look like? Or about other solutions to pass U0 between main() and fvPatchFields without looping over all patches from within main() and assigning U0 to each of the fvPatchFields through an additional setter function?
With kind regards
|Thread||Thread Starter||Forum||Replies||Last Post|
|MSHArequest for surfaceScalarField phi from objectRegistry||msha||OpenFOAM Running, Solving & CFD||11||March 21, 2014 04:35|
|Global variables||harly||OpenFOAM Running, Solving & CFD||0||December 5, 2008 21:41|
|Register pointer to class in mesh objectRegistry||kar||OpenFOAM||1||June 3, 2008 04:57|
|Global and local variables||Astrid||CFX||8||April 16, 2002 00:52|
|Global variables storage in CFX.||Fabio Kasper||CFX||1||October 6, 2000 08:21|