CFD Online Discussion Forums

CFD Online Discussion Forums (http://www.cfd-online.com/Forums/)
-   OpenFOAM Running, Solving & CFD (http://www.cfd-online.com/Forums/openfoam-solving/)
-   -   face zones/sets in OpenFOAM-1.6-ext (http://www.cfd-online.com/Forums/openfoam-solving/83732-face-zones-sets-openfoam-1-6-ext.html)

cnsidero January 9, 2011 23:45

face zones/sets in OpenFOAM-1.6-ext
 
1 Attachment(s)
I was looking into switching to 1.6-ext (I currently use 1.5-dev) and I commonly use the GGI capabilities for turbomachinery applications so I started by trying to run the 2D centrifugal pump case from SIG Turbo validation cases: http://openfoamwiki.net/index.php/Si...vaned_diffuser

This case runs without issue in 1.5-dev but not so in 1.6-ext. There seems to be some differences in how 1.6-ext builds face zones (or it could be the face sets - I'm not 100% sure what the root cause is). I can run the makeMesh script Ok but when I run checkMesh to make sure the rotor, stator, GGI interfaces and cell zones were built properly I get an error. Here's the error reported from checkMesh (and I've attached a log file for completeness):

Code:

***FaceZone GGI_EXT_ZONE is not correctly synchronised across coupled boundaries. (coupled faces both present in set but with opposite flipmap)
 ***FaceZone GGI_INT_ZONE is not correctly synchronised across coupled boundaries. (coupled faces both present in set but with opposite flipmap)

I had to disable most of the libraries (libOpenFOAMTurbo) in the controlDict's for this case because I have not attempted to port the libraries to 1.6-ext yet. Other than that, I changed nothing in this case's setup or scripts.

Unless something changed about how face sets and zones are created from 1.5-dev to 1.6-ext, this appears to be a bug. If someone knows better feel free to enlighten me.

I would have logged this bug through the bug tracker on extend-project.de but it doesn't seem to be currently working.

cnsidero January 10, 2011 17:43

I was told there is in fact no error and to ignore checkMesh's warning (the error is actually in the error reporting). I haven't run it yet to verify it but it should run Ok.


All times are GMT -4. The time now is 09:53.