View Issue Details

IDProjectCategoryView StatusLast Update
0000704OpenFOAMBugpublic2013-03-19 13:28
Reporteruser565Assigned Touser4 
PriorityimmediateSeveritycrashReproducibilityalways
Status resolvedResolutionfixed 
PlatformUbuntu 12.01OSUbuntu OS Version12.01
Summary0000704: parallel running error with cyclic BCs for pimpleDyMFoam
Description   When I use pimpleDyMFoam together with cyclic boundary conditions,(actually I use waveDisplacement, you can try the movingCylinder case, with a pair of cyclic boundaries and oscillatingVelocity for the cylinder, the same thing happens) parallel running cracks: after about 2 or 3 timeSteps, running stopped with the message " face o area does not match neighbour by 0.0195% --possible face ordering problem", no matter what kind of decomposition method I use, the same problem always appears. But when I use a single core to run it, no such problem happens. So I assume there might be some bugs in parallel running of dynamic mesh cases with cyclic BCs.
Steps To ReproduceRun the following applications in turn:
 blockMesh
 decomposePar
 mpirun -np 2 pimpleDyMFoam -parallel

# It cracks!
TagsNo tags attached.

Activities

user565

2012-12-16 09:13

 

bugReport.tar.gz (10,240 bytes)

wyldckat

2012-12-22 21:35

updater   ~0001845

Just to share my findings on this:
1- The (almost) latest 2.1.x from commit 0eb2250690e3090f340899d1d8177eed0880301c, locks up instead of crashing.


2- Changing to cyclicAMI (+ a few needed adjustments) should make the case work in parallel.
Example available here: http://www.cfd-online.com/Forums/openfoam-bugs/109854-parallel-error-cyclic-bcs-pimpledymfoam-trouble-resuming-running.html#post398703

user4

2013-03-19 13:28

  ~0002022

Fixed in 0df303480d00a3bd9773c7b9c28ad57cb201a3d6

It was probably working for 'blocking' commsType. It now works for nonBlocking as well. It should now also handle multiple cyclics between the same two processors.

Thanks for reporting.

Issue History

Date Modified Username Field Change
2012-12-16 09:13 user565 New Issue
2012-12-16 09:13 user565 File Added: bugReport.tar.gz
2012-12-22 21:35 wyldckat Note Added: 0001845
2013-03-19 13:28 user4 Note Added: 0002022
2013-03-19 13:28 user4 Status new => resolved
2013-03-19 13:28 user4 Fixed in Version => 2.2.x
2013-03-19 13:28 user4 Resolution open => fixed
2013-03-19 13:28 user4 Assigned To => user4