|
[Sponsors] |
Interesting Bug in InterDyMFOAM (Dynamic Mesh Refinement) parallel restart |
![]() |
|
LinkBack | Thread Tools | Search this Thread | Display Modes |
![]() |
![]() |
#1 |
Senior Member
mohammad
Join Date: Sep 2015
Posts: 281
Rep Power: 12 ![]() |
Hello my friends,
I have found an issue in my refined grid, specifically when I restart my parallel case from a non-zero time. The solver in InterDyMFOAM. Here you can see the details in my dynamicMeshDict Code:
dynamicFvMesh dynamicRefineFvMesh;//staticFvMesh; dynamicRefineFvMeshCoeffs { refineInterval 1;//refine every refineInterval timesteps field interFace; lowerRefineLevel 0.0001; upperRefineLevel 0.99; unrefineLevel 10; nBufferLayers 1; maxRefinement 2;//maximum refinement level (starts from 0) maxCells 20000000; correctFluxes ( (phi U) (phi_0 U) ); dumpLevel true; } BTW, As I restart my case, the mesh in the processors boundary does not return to its zero cellLevel when it passes the processors boundary. Indeed, the processor interface location maintains its level 1 value even if the moving object passes from that region. It seems that something is wrong with decomposition of reconstruction of the latest Time. Code:
if [ -f "processor0/constant/polyMesh/points" ]; then echo "constant is within the processors" if [ -f "polyMeshFiles/processor0/constant/polyMesh/points" ]; then rm -r polyMeshFiles/ fi for proc_ in processor*; do mkdir -p polyMeshFiles/$proc_ cp -r $proc_/constant polyMeshFiles/$proc_ done else echo "constant needs to be copied" for proc_ in processor*; do cp -r polyMeshFiles/$proc_/constant $proc_/ done fi reconstructParMesh -mergeTol 1e-06 reconstructPar -noLagrangian Thank you for you help, in advance, Foamers! Last edited by mostanad; November 23, 2020 at 23:07. |
|
![]() |
![]() |
![]() |
![]() |
#2 |
Senior Member
mohammad
Join Date: Sep 2015
Posts: 281
Rep Power: 12 ![]() |
Update:
Fixed Its a bug in the new decomposition for your restart run. Don't remove and use decomposePar in your restart run again. This will remove the processor directories for the latest Time, so by doing the new decomposePar, all the things for the new decomposed latest time is messed up. |
|
![]() |
![]() |
![]() |
|
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
Reconstruction of the parallel case with dynamic mesh | makaveli_lcf | OpenFOAM Post-Processing | 8 | December 3, 2024 12:16 |
[snappyHexMesh] SnappyHexMesh for internal Flow | vishwa | OpenFOAM Meshing & Mesh Conversion | 24 | June 27, 2016 09:54 |
Interesting problem: Parallel Processor VOF Fluent + Dynamic Mesh + System Coupling | spaceprop | FLUENT | 5 | September 2, 2014 10:43 |
Dynamic mesh, interDymFoam : refinement on 2 fields | tek_cfd | OpenFOAM Pre-Processing | 1 | May 30, 2013 04:07 |
[snappyHexMesh] Layers:problem with curvature | giulio.topazio | OpenFOAM Meshing & Mesh Conversion | 10 | August 22, 2012 10:03 |