|
[Sponsors] |
[snappyHexMesh] snappyhexmesh running for first 3 time steps |
|
LinkBack | Thread Tools | Search this Thread | Display Modes |
May 16, 2018, 16:42 |
snappyhexmesh running for first 3 time steps
|
#1 |
New Member
Ishan Anjikar
Join Date: Mar 2018
Posts: 21
Rep Power: 8 |
Hi,
After running the snappyHexMesh it creates folders for first 3 time step and also it the meshing start from the first time step rather than than the start time,0. Can someone tell me why this is happening. I want it to create mesh for time=0 only. I have attached my snappyHexMeshdict file |
|
May 17, 2018, 03:49 |
|
#2 |
Senior Member
Anton Kidess
Join Date: May 2009
Location: Germany
Posts: 1,377
Rep Power: 30 |
It's happening because that's what you told it to do. Set your startTime in controlDict to 0, and run snappyHexMesh -overwrite.
__________________
*On twitter @akidTwit *Spend as much time formulating your questions as you expect people to spend on their answer. |
|
May 17, 2018, 12:54 |
|
#3 |
New Member
Ishan Anjikar
Join Date: Mar 2018
Posts: 21
Rep Power: 8 |
||
June 4, 2018, 21:22 |
|
#4 |
Member
Andrew O. Winter
Join Date: Aug 2015
Location: Seattle, WA, USA
Posts: 78
Rep Power: 11 |
You could also copy the polyMesh directory inside the final time directory to the constant directory in the main case directory and then delete all of the time steps past 0 before actually running your case, but using the -overwrite flag is clearly easier.
In general though, each of the 3 potential operations (castellatedMesh, snap, addLayers) you can do using snappyHexMesh are done in separate time steps so you really only need the last one, providing each step was completed successfully. Also, if you aren't happy with the results of say the addLayers option, then you could use one of the partway steps that are saved in different time directories if building your mesh takes a long time as a starting point to redo the addLayers step. I think that's one of the main reasons they write each step separately instead of overwriting them by default, but I guess this is unnecessary if everything works okay for you. |
|
June 4, 2018, 23:43 |
|
#5 | |
New Member
Ishan Anjikar
Join Date: Mar 2018
Posts: 21
Rep Power: 8 |
Quote:
|
||
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
[General] Extracting ParaView Data into Python Arrays | Jeffzda | ParaView | 30 | November 6, 2023 22:00 |
Setting up Lid driven Cavity Benchmark with 1M cells for multiple cores | puneet336 | OpenFOAM Running, Solving & CFD | 11 | April 7, 2019 01:58 |
pressure in incompressible solvers e.g. simpleFoam | chrizzl | OpenFOAM Running, Solving & CFD | 13 | March 28, 2017 06:49 |
Micro Scale Pore, icoFoam | gooya_kabir | OpenFOAM Running, Solving & CFD | 2 | November 2, 2013 14:58 |
How to write k and epsilon before the abnormal end | xiuying | OpenFOAM Running, Solving & CFD | 8 | August 27, 2013 16:33 |