[burt]

Hi there

this problem has been bothering me for days!

Info << newMesh().thisDb().lookupObject<dictionary>("fvSch emes") << endl;

error comes:
lookup of fvSchemes from objectRegistry background successful
but it is not a dictionary, it is a dictioanry

personally I think there is someting wrong with the ptr, just can not figure out the solution.

anyone has ever been through this??

thanks a lot for your attention!!!

burt

[wyldckat]

Quick questions:

1. Which OpenFOAM version or variant are you using?
2. How can we reproduce the same error?

[burt]

hi wyldckat
I am using OF 2.2.2
I got this problem after I wrote hundreds of codes, this error occur when it came to this line
fvm::ddt(U_subdomain)
I was trying to solve UEqn in a subdomain

Originally Posted by wyldckat

Quick questions:

1. Which OpenFOAM version or variant are you using?
2. How can we reproduce the same error?

[wyldckat]

Hi burt,

This is an interesting result... it stating that it is a dictionary and not a dictionary

From what I figure out, you can have access to this particular dictionary like this:

Info << newMesh().schemesDict() << endl;

This is possible because the class "fvMesh" inherits directly from the class "fvSchemes".

Actually, this also works:

Info << newMesh().thisDb().lookupObject<IOdictionary>("fvSchemes") << endl;

The difference is that "IOdictionary" is derived from "dictionary" and essentially have the same type names, but "IOdictionary" is specific for handling the dictionary files.

Best regards,
Bruno

[burt]

Hi Bruno

it is so nice of you, and obviously you are professional.
when I tried

Info << fluidRegions[0] .schemesDict() << endl;

the scheme shows well
when I typed

Info << newMesh() .schemesDict() << endl;

nothing useful appeared
newMesh is a subdomain of fluidRegion[0]
I will dig more!

thanks again for your kindly help!!

Originally Posted by wyldckat

Hi burt,

This is an interesting result... it stating that it is a dictionary and not a dictionary

From what I figure out, you can have access to this particular dictionary like this:

Info << newMesh().schemesDict() << endl;

This is possible because the class "fvMesh" inherits directly from the class "fvSchemes".

Actually, this also works:

Info << newMesh().thisDb().lookupObject<IOdictionary>("fvSchemes") << endl;

The difference is that "IOdictionary" is derived from "dictionary" and essentially have the same type names, but "IOdictionary" is specific for handling the dictionary files.

Best regards,
Bruno