[yossi]

hello,

running chtMultiRegionFoam I get the following output:

"
Create time

Create fluid mesh for region topAir for time = 0

Create solid mesh for region heater for time = 0



--> FOAM FATAL IO ERROR:
keyword startFace is undefined in dictionary "::zones"

file: ::zones from line 55 to line 55.

From function dictionary::lookupEntry(const word&, bool, bool) const
in file db/dictionary/dictionary.C at line 395.

FOAM exiting
"


but I don't know which file or dict to look for 'startFace'

Does anyone know if this is BC problem or what cause this error?

thanks,

[Linse]

Hi Yossi,

I don't know if it helps, but I had a similar problem - though it was not in zones but in minX. I simply had tried to implement another geometry and had taken over all of the names, patches, etc...

The entry "startFace" in my case was missing within bottomAir/polyMesh/boundary .
Entering the entries for nFaces and startFace (and doing similar in a few initial solutions within the 0-folder) did make the simulation cross that point at least.
Perhaps that already works for you?

In my case though the simulation failed afterwards with a segfault, because I was doing weird things with the geometry. ;-)

[yossi]

Hi Bernard,
thank you for your replay.
it exactly as you described, and I've solved it.

thank you!

[vitors]

Originally Posted by Linse

Hi Yossi,

I don't know if it helps, but I had a similar problem - though it was not in zones but in minX. I simply had tried to implement another geometry and had taken over all of the names, patches, etc...

The entry "startFace" in my case was missing within bottomAir/polyMesh/boundary .
Entering the entries for nFaces and startFace (and doing similar in a few initial solutions within the 0-folder) did make the simulation cross that point at least.
Perhaps that already works for you?

In my case though the simulation failed afterwards with a segfault, because I was doing weird things with the geometry. ;-)

I know this is an old post, but I think providing I little more information would help this thread:

When editin the changeDictionaryDict, the 'boundary' entries will add the boundary information to the boundary file inside the polyMesh directory of the related region. So, removing the boundary entry if it is not necessary, will avoid this error and its weird error message.

Regards,

Vitor

[yossi]

Hi Vigor

Indeed it was a problem with the completeness of the boundary file

Thanks