|
|
|
|
|
|
Have you changed the code to dump and read meshPhi? What difference do you see by doing this? I see no need to dump and read meshPhi when running with first-order in time. |
|
|
|
Look at the two cases I have attached, they are exactly the same apart from the meshPhi file. Run them with your pimpleDyMFoam, it will run for one time step starting from t=0.0002. Open up ParaView and see the difference between the two cases at t=0.000205. The pressure field for the case with meshPhi is more or less the same as at t=0.0002. The case without meshPhi, however, exhibits a pressure drop from -7 to -9. |
|
|
|
This of course confirms that meshPhi is read when present. |
|
|
|
Thanks for the details. The problem with using meshPhi from the previous time-step is that it needs to be mapped following tompology change. To avoid this I have been changing the solvers to operate on intensive properties only thus avoiding the need to read and write meshPhi. This new approach is much more general and reliable and will be used in all the "DyM" solvers in the next release. Some of the changes for topology change have been back-ported to OpenFOAM-2.2.x which is why meshPhi is not written but not all the changes to support this -- appologies for confusion and the bug.
I will revert the fvMesh code in OpenFOAM-2.2.x to write meshPhi again which will be sufficient for mesh-morphing cases but is not ideal for topology change. All this will be fixed in the next release. |
|
|
|
Resolved by commit cde97091ebaba91cbb15d57da65793c4d30d6a17 |
|
