|
[Sponsors] |
Basic Question about Time Directories Created |
|
LinkBack | Thread Tools | Search this Thread | Display Modes |
December 9, 2020, 14:27 |
Basic Question about Time Directories Created
|
#1 |
Member
Mike Tree
Join Date: Feb 2016
Location: Charlotte, NC
Posts: 37
Rep Power: 10 |
I am running v2006. I ran a very basic pipe flow simulation for a certain number of time steps (setting a Co max and using adjustTimeStep). I also set an initial deltaT. Everything runs fine. All of the solution time step directories I requested are present, but there is an additional one present. A time directory is created that is named "5e-05", the value I used for deltaT. This time directory only contains "U" and "p" files, and a "polyMesh" subdirectory.
Why is this directory written? At the end of the simulation I realized I wanted to go back and restart the sim halfway through, seeding the flow with massless Lagrangian particles. Again, everything worked fine and all time directories output after my restart contain Lagrangian particle data. Once again, though, I have an additional output time directory this one is called "4.02742e-05", and contains "U" and "p" files, and a "polyMesh" subdirectory as well. This value doesn't correspond to the deltaT in my controlDict, nor does it correspond to the deltaT at my restart time step (my time step is always changing because it is controlled via Courant number). These new directories I don't remember asking for actually appear any time I attempt another restart of the sim. It seems OpenFoam is re-writing out the mesh every time I attempt a restart, but nothing about the mesh is changing. I'm not imposing any mesh motion or adaptation. Is there someway to tell OpenFoam to instead use the mesh in constant/polyMesh? |
|
December 9, 2020, 14:46 |
|
#2 |
Member
Mike Tree
Join Date: Feb 2016
Location: Charlotte, NC
Posts: 37
Rep Power: 10 |
WAIT!!!!!!
I'm running a script to kick off my simulation and it includes a decomposePar command. I believe these directories are the parallelized mesh. That makes a lot more sense! |
|
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
[General] Extracting ParaView Data into Python Arrays | Jeffzda | ParaView | 30 | November 6, 2023 21:00 |
Setting up Lid driven Cavity Benchmark with 1M cells for multiple cores | puneet336 | OpenFOAM Running, Solving & CFD | 11 | April 7, 2019 00:58 |
Floating point exception error | lpz_michele | OpenFOAM Running, Solving & CFD | 53 | October 19, 2015 02:50 |
simpleFoam error - "Floating point exception" | mbcx4jc2 | OpenFOAM Running, Solving & CFD | 12 | August 4, 2015 02:20 |
same geometry,structured and unstructured mesh,different behaviour. | sharonyue | OpenFOAM Running, Solving & CFD | 13 | January 2, 2013 22:40 |