decomposePar corrupting mesh
I have a mesh which passes checkMesh serial no problems. However if I use decomposePar, and run checkMesh in parallel, it fails for the same mesh as follows:
Face pyramids OK.
***Max skewness = 4.28888, 475 highly skew faces detected which may impair the quality of the results
<<Writing 475 skew faces to set skewFaces
Coupled point location match (average 2.60702e-16) OK.
Failed 1 mesh checks.
The number of skewed faces depends on the number of processors I use (with greater #processors seemingly corrupting the mesh more)
numberOfSubdomains $NSLOTS ;
I have cyclic boundaries in spanwise direction (which are exactly the same on patch cyc_half0 and cyc_half1). Not sure if this could have an effect?
Does anyone else see this happen at all? The mesh does seem to work OK, but it strikes me as odd that the cell quality should deteriorate by domain decomposition. decomposePar should not be affecting the coordinates of the mesh vertices, so this shouldn't happen...
Is this a bug?
preservePatches may only take 1 augment.
I detailed my cyclic BC issues in the following thread:
|All times are GMT -4. The time now is 18:29.|