BUG: Unit test failures - 13.12.2016

Unknown dynamicFvMesh type solidBodyMotionFvMesh

• incompressible/pimpleDyMFoam/oscillatingInletPeriodicAMI2D - pimpleDyMFoam failed
• combustion/XiDyMFoam/annularCombustorTurbine - XiDyMFoam failed

keyword position is undefined, runTimePP FO

• incompressible/pisoFoam/LES/motorBike/motorBike -simpleFoam failed

pointProcAddressing missing - Add reconstructParMesh before constructing data

• multiphase/interFoam/RAS/DTCHull - reconstructPar failed
• multiphase/interDyMFoam/RAS/DTCHull - reconstructPar failed

#339 (closed)

#336 (closed)

@internal

Mentioned in commit c9244cb1ac72c9b65f4fa15911bc5996f4c72c9a

By Andrew Heather on 2016-12-13T12:41:18 (imported from GitLab project)

multiphase/interFoam/RAS/DTCHull : is should not need a reconstructParMesh. Is it working in feature-cellSetRemove branch?

pointProcAddressing missing - Add reconstructParMesh before constructing : is bug from my renumberMesh changes. I'll take this one.

Mentioned in commit 133cc3c27d83a5d8af3745f70d6149a02432b97f

c9c560d7c53ae2b798d5c40f5b918a6d0f40359a should fix the renumberMesh of pointProcAddressing (DTCHull).

Mentioned in commit 9abd5e45f02fc0382a94401b147c7dcd031d3c20

By Andrew Heather on 2016-12-15T16:28:55 (imported from GitLab project)

It appears renumberMesh no longer removes inconsistent processor decompositions... which causes issues when running redistributePar -reconstruct after running snappyHexMesh. Was the removing of the inconsistent processor decompositions functionality after snappyHexMesh replaced/moved somewhere?

By Justin Graupman on 2016-12-15T23:21:10 (imported from GitLab project)

c9c560d7 had fixed issue related to the tutorial cases.

@graups : if you are using renumberMesh with maps on this is reported in #344 (closed). Did you see any other case of failure?

All topics reported in first list are successful now.

@graups Please create new ticket if you have any failure not covered in #344 (closed)

Status changed to closed