[theBananaTrick]

Hello,

I am trying to create a solver as a functionObject (FO) utility in OF2106.

As such, I am trying to read values from a IOdictionary in the constant directory.

I have modified the public inheritance of the FO to inherit publicly form the IOdictionary class.

class myFOSolver
:
    public fvMeshFunctionObject, public IOdictionary
{

Now, I need to initialize the IOdictionary part of this FO.

With "standard" initialization:

    IOdictionary
    (
        IOobject
        (
            "myPropertiesDict",
            mesh_.time().constant(),
            mesh_,
            IOobject::MUST_READ, 
            IOobject::NO_WRITE
        )
    );

The solver will just tell me that the dictionary does not exist and moves on.


I created a function to initialize the dictionary as:

Foam::IOdictionary Foam::functionObjects::myFOSolver::init()
{
 
    bool checkDict
    (
        IOobject
        (
            "myPropertiesDict",
            mesh_.time().constant(),
            mesh_,
            IOobject::MUST_READ, 
            IOobject::NO_WRITE,
            false
        ).typeHeaderOk<IOdictionary>()
    );
 
    if (!checkDict)
    {
        FatalErrorInFunction
            << "Dictionary does not exist in " << mesh_.time().constant() << "directory " << nl << nl 
            << abort(FatalError);
    }
 
    IOdictionary dict
    (
        IOobject
        (
            "myPropertiesDict",
            mesh_.time().constant(),
            mesh_,
            IOobject::MUST_READ, 
            IOobject::NO_WRITE
        )
    );
    
    return dict;
}

Is it possible to set the behavior upon construction of the IOdictionary to make the solver stop if the dictionary cannot be read? Or is initializing it throw a function the only way? If so, what is the purpose of using "MUST_READ" if it will not force the whole solver to stop?


I just get the following:

Starting time loop

--> FOAM Warning : 
cannot find file "/home/bananaTrick/Desktop/myCase/constant/myPropertiesDict

[olesen]

What it actually does is surrounding the construction in a try/catch block and discards the function object out of the list is there was a problem. You can customise that for all function objects or individual ones in the functions specification.
https://www.openfoam.com/documentati...t.html#details

you have the choice of default/warn/error/strict.

So many options because everyone has a different situation, or some function objects might be critical but others just "nice to have"

[theBananaTrick]

Thank you for the help!

With this, I also cleared several lines of code