|April 6, 2010, 03:58||
strange behaviour of GGI in parallel on axis symmetrical case
Join Date: Mar 2010
Posts: 36Rep Power: 7
i'm running an axis symmetrical case with a moving element. This case runs perfectly with a simple decomposition on 4 CPUs (2 in x and 2 in y), but remains unfortunately quite slow, even using the last svn of 1.5-dev, and even if my domain is fairly small (1.4 Mcells).
This same case has a strange behaviour when i want to raise the number of CPUs to 8:
- cutting x y z axis in 2 2 2 brings my mesh to move where it shouldn't, quite far away from my GGI zone, even if i "preserve" my GGI interfaces when i decompose.
- i thought my problem came from the decomposition in z, which is the axis of symmetry, so i decomposed the case in an "azimuthal" (pie-like) way on 8 CPUs with a manual decomposition dictionary, which didn't help: my mesh was still moving at some other places where i didn't expect it.
Does anyone have an idea or observe the same behaviour? May my dynamicMeshDict or decomposeParDict be useful, i could of course post them here.
|axissymmetric problem, decomposition, ggi, parallel|
|Thread||Thread Starter||Forum||Replies||Last Post|
|Parallel case setup boundry conditions snappyhexmesh||oskar||OpenFOAM Pre-Processing||5||September 11, 2009 01:12|
|How to specify the axis in 2D axis-symmetric case?||B||FLUENT||4||February 9, 2009 10:09|
|How to send nonconformal case to parallel||Lily||FLUENT||5||September 10, 2007 14:53|
|Run in parallel a 2mesh case||cosimobianchini||OpenFOAM Running, Solving & CFD||2||January 11, 2007 07:33|
|Free surface boudary conditions with SOLA-VOF||Fan||Main CFD Forum||10||September 9, 2006 12:24|