|
[Sponsors] |
[OLAFLOW] OLAFOAM baseWaveFlume ,adding slope resulted in Simulation Termination |
|
LinkBack | Thread Tools | Search this Thread | Display Modes |
September 4, 2017, 07:11 |
OLAFOAM baseWaveFlume ,adding slope resulted in Simulation Termination
|
#1 |
New Member
Ahmed
Join Date: Aug 2017
Location: Germany
Posts: 2
Rep Power: 0 |
Dear All,
I am new with OpenFOAM(v4.1) and OLAFOAM even with forums, so pardon my irrelevancy if that is so. I want to simulate waves hitting on a dike + its wave run up so i picked up base wave flume tutorial, it worked fine , then i changed the blockMeshDict by bringing two of the right points closer towards origin to model a slope of 1/5 (which is close to what i need). The simulation ran for two iterations and then the following statements occurred and the simulation got completed: blockMesh meshing... Preparing 0 folder... Setting the fields... Running... #0 Foam::error:rintStack(Foam::Ostream&) at ??:? #1 Foam::sigFpe::sigHandler(int) at ??:? #2 ? in "/lib/x86_64-linux-gnu/libc.so.6" #3 double Foam::sumProd<double>(Foam::UList<double> const&, Foam::UList<double> const&) at ??:? #4 Foam::PCG::solve(Foam::Field<double>&, Foam::Field<double> const&, unsigned char) const at ??:? #5 Foam::fvMatrix<double>::solveSegregated(Foam::dict ionary const&) at ??:? #6 Foam::fvMatrix<double>::solve(Foam::dictionary const&) at ??:? #7 ? at ??:? #8 __libc_start_main in "/lib/x86_64-linux-gnu/libc.so.6" #9 ? at ??:? ./runCase: line 16: 2570 Floating point exception(core dumped) olaFoam > olaFoam.log Simulation complete. I tried checkMesh to re assure and it seemed : Build : 4.1 Exec : checkMesh Date : Sep 04 2017 Time : 12:19:21 Host : "siddiqui" PID : 3137 Case : /home/siddiqui/OpenFOAM/siddiqui-4.1/OLAFOAM/tutorials/OF_OF+_latest/baseWaveFlume nProcs : 1 sigFpe : Enabling floating point exception trapping (FOAM_SIGFPE). fileModificationChecking : Monitoring run-time modified files using timeStampMaster allowSystemOperations : Allowing user-supplied system call operations // * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * // Create time Create polyMesh for time = 0 Time = 0 Mesh stats points: 17892 internal points: 0 faces: 35195 internal faces: 17305 cells: 8750 faces per cell: 6 boundary patches: 5 point zones: 0 face zones: 0 cell zones: 0 Overall number of cells of each type: hexahedra: 8750 prisms: 0 wedges: 0 pyramids: 0 tet wedges: 0 tetrahedra: 0 polyhedra: 0 Checking topology... Boundary definition OK. Cell to face addressing OK. Point usage OK. Upper triangular ordering OK. Face vertices OK. Number of regions: 1 (OK). Checking patch topology for multiply connected surfaces... Patch Faces Points Surface topology inlet 70 142 ok (non-closed singly connected) outlet 70 142 ok (non-closed singly connected) bottom 125 252 ok (non-closed singly connected) atmosphere 125 252 ok (non-closed singly connected) frontAndBack 17500 17892 ok (non-closed singly connected) Checking geometry... Overall domain bounding box (0 -0.2 0) (10 0 1) Mesh has 2 geometric (non-empty/wedge) directions (1 0 1) Mesh has 2 solution (non-empty) directions (1 0 1) All edges aligned with or perpendicular to non-empty directions. Boundary openness (4.21952e-18 -3.44198e-15 4.18793e-17) OK. Max cell openness = 2.15085e-16 OK. Max aspect ratio = 10.56 OK. Minimum face area = 0.00057551. Maximum face area = 0.016. Face area magnitudes OK. Min volume = 0.000115102. Max volume = 0.000227755. Total volume = 1.5. Cell volumes OK. Mesh non-orthogonality Max: 78.6458 average: 62.4877 *Number of severely non-orthogonal (> 70 degrees) faces: 7784. Non-orthogonality check OK. <<Writing 7784 non-orthogonal faces to set nonOrthoFaces Face pyramids OK. Max skewness = 1.78278 OK. Coupled point location match (average 0) OK. Mesh OK. End The blockMesh.log is : nProcs : 1 sigFpe : Enabling floating point exception trapping (FOAM_SIGFPE). fileModificationChecking : Monitoring run-time modified files using timeStampMaster allowSystemOperations : Allowing user-supplied system call operations // * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * // Create time Creating block mesh from "/home/siddiqui/OpenFOAM/siddiqui-4.1/OLAFOAM/tutorials/OF_OF+_latest/baseWaveFlume/system/blockMeshDict" Creating curved edges Creating topology blocks Creating topology patches Reading patches section Creating block mesh topology Reading physicalType from existing boundary file Default patch type set to empty Check topology Basic statistics Number of internal faces : 0 Number of boundary faces : 6 Number of defined boundary faces : 6 Number of undefined boundary faces : 0 Checking patch -> block consistency Creating block offsets Creating merge list . Creating polyMesh from blockMesh Creating patches Creating cells Creating points with scale 1 Block 0 cell size : i : 0.04 .. 0.04 j : 0.2 .. 0.2 k : 0.0142857 .. 0.0142857 Writing polyMesh ---------------- Mesh Information ---------------- boundingBox: (0 -0.2 0) (10 0 1) nPoints: 17892 nCells: 8750 nFaces: 35195 nInternalFaces: 17305 ---------------- Patches ---------------- patch 0 (start: 17305 size: 70) name: inlet patch 1 (start: 17375 size: 70) name: outlet patch 2 (start: 17445 size: 125) name: bottom patch 3 (start: 17570 size: 125) name: atmosphere patch 4 (start: 17695 size: 17500) name: frontAndBack End As far as what i get from different sources is that i am having some divide by zero issue somewhere and i don't know how to trace it . I have not changed anything in alpha.water, p_rgh , U and alpha.water.org Please help me out with this.Let me know where am i loosing. Thankyou so much. and sorry for such long post. The blockTopology is attached. BlockTopology_Slope.jpg |
|
September 4, 2017, 07:37 |
|
#2 |
Senior Member
Pablo Higuera
Join Date: Jan 2011
Location: Auckland
Posts: 627
Rep Power: 19 |
Hi Ahmed,
welcome. There are lots of things that can go wrong with cfd simulations, so we usually need more information to check what is going on. I suggest that you read this thread: How to give enough info to get help Creating the mesh this way may generate significant non-orthogonality. Keep in mind that having checkMesh report 'Mesh OK' does not mean that your mesh is going to work. Before getting additional information, I can think of: what boundary conditions are you using? how does your alpha initial conditions look like? what is your wave height compared to the cell resolution? what is your initial wave phase (might a discontinuity in time 0 occur)?... The list is endless (and all of them have happened to me). If you upload your case I can have a look. Best, Pablo |
|
September 4, 2017, 07:59 |
|
#3 |
New Member
Ahmed
Join Date: Aug 2017
Location: Germany
Posts: 2
Rep Power: 0 |
Thankyou so much for your prompt reply,
I have uploaded the case in dropbox, It would be very kind of you if you have a look at it. https://www.dropbox.com/sh/2ci8tuhqb...IeBETcQRa?dl=0 Awaiting in anticipation. Thankyou so much |
|
September 5, 2017, 02:08 |
|
#4 |
Senior Member
Pablo Higuera
Join Date: Jan 2011
Location: Auckland
Posts: 627
Rep Power: 19 |
Hi Ahmed,
there are lots of mistakes here. When you use a case as a base you should not forget to modify what will be different in the new case. For example, the outlet patch now needs to become a wall, therefore, it needs wall boundary conditions. You are also filling your 1 m high mesh with 2 m of water, so your domain is completely underwater. Also, the mesh is not good. As a newcomer to OpenFOAM I suggest that you spend some time reading and training yourself in creating meshes, changing boundary conditions and postprocessing. Check other tutorials and the extensive posts in this forum to gain a better understanding. Best, Pablo |
|
Thread Tools | Search this Thread |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Help in FSI : termination due to maximum simulation time | kqlee | CFX | 5 | August 16, 2012 03:14 |