|
[Sponsors] |
June 26, 2020, 00:27 |
pimpleFoam crash
|
#1 |
Member
WY
Join Date: Mar 2020
Posts: 36
Rep Power: 6 |
Hi, everyone. My pimpleFoam case crashed because of the error:
[CODE][/ #0 Foam::error:rintStack(Foam::Ostream&) at ??:? #1 Foam::sigFpe::sigHandler(int) at ??:? #2 ? in "/lib/x86_64-linux-gnu/libc.so.6" #3 Foam::GAMGSolver::scale(Foam::Field<double>&, Foam::Field<double>&, Foam::lduMatrix const&, Foam::FieldField<Foam::Field, double> const&, Foam::UPtrList<Foam::lduInterfaceField const> const&, Foam::Field<double> const&, unsigned char) const at ??:? #4 Foam::GAMGSolver::Vcycle(Foam::PtrList<Foam::lduMa trix::smoother> const&, Foam::Field<double>&, Foam::Field<double> const&, Foam::Field<double>&, Foam::Field<double>&, Foam::Field<double>&, Foam::Field<double>&, Foam::Field<double>&, Foam::PtrList<Foam::Field<double> >&, Foam::PtrList<Foam::Field<double> >&, unsigned char) const at ??:? #5 Foam::GAMGSolver::solve(Foam::Field<double>&, Foam::Field<double> const&, unsigned char) const at ??:? #6 Foam::fvMatrix<double>::solveSegregated(Foam::dict ionary const&) at ??:? #7 Foam::fvMatrix<double>::solve(Foam::dictionary const&) in "/home/ying/OpenFOAM/OpenFOAM-7/platforms/linux64GccDPInt32Opt/bin/pimpleFoam" #8 Foam::fvMatrix<double>::solve() in "/home/ying/OpenFOAM/OpenFOAM-7/platforms/linux64GccDPInt32Opt/bin/pimpleFoam" #9 ? in "/home/ying/OpenFOAM/OpenFOAM-7/platforms/linux64GccDPInt32Opt/bin/pimpleFoam" #10 __libc_start_main in "/lib/x86_64-linux-gnu/libc.so.6" #11 ? in "/home/ying/OpenFOAM/OpenFOAM-7/platforms/linux64GccDPInt32Opt/bin/pimpleFoam"] According to the similar threads, I think there might something wrong with mesh, BCs, ICs, or fvScheme ... I use a different mesh with the same settings, and it can run normally, so there should be the problem of my mesh. But checkMesh shows that my current mesh is ok, and the following is checkMesh result. [CODE][/ nProcs : 1 sigFpe : Enabling floating point exception trapping (FOAM_SIGFPE). fileModificationChecking : Monitoring run-time modified files using timeStampMaster (fileModificationSkew 10) allowSystemOperations : Allowing user-supplied system call operations // * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * // Create time Create polyMesh for time = 0 Time = 0 Mesh stats points: 14570 internal points: 0 faces: 28465 internal faces: 13895 cells: 7060 faces per cell: 6 boundary patches: 5 point zones: 0 face zones: 0 cell zones: 0 Overall number of cells of each type: hexahedra: 7060 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 60 122 ok (non-closed singly connected) outlet 60 122 ok (non-closed singly connected) topAndBottom 210 424 ok (non-closed singly connected) ellipse 120 240 ok (non-closed singly connected) frontAndBack 14120 14570 ok (non-closed singly connected) Checking geometry... Overall domain bounding box (-15 -10 0) (30 10 1) Mesh has 2 geometric (non-empty/wedge) directions (1 1 0) Mesh has 2 solution (non-empty) directions (1 1 0) All edges aligned with or perpendicular to non-empty directions. Boundary openness (-1.37738e-18 -1.28556e-17 -4.40304e-16) OK. Max cell openness = 1.95596e-16 OK. Max aspect ratio = 39.9198 OK. Minimum face area = 0.0009276. Maximum face area = 1.36373. Face area magnitudes OK. Min volume = 0.0009276. Max volume = 1.36373. Total volume = 899.126. Cell volumes OK. Mesh non-orthogonality Max: 42.3783 average: 8.85474 Non-orthogonality check OK. Face pyramids OK. Max skewness = 0.481758 OK. Coupled point location match (average 0) OK. Mesh OK. End] I really confused about this problem, and I have stucked here for long time. This error would happen immediately after the running begins, about 41 iterations. I also attach the log file. If there is something wrong with my current mesh, how can I find and solve it when checkMesh is ok? I would be very appreciate for any help!! Many thanks!! |
|
June 26, 2020, 18:30 |
|
#2 |
Senior Member
Troy Snyder
Join Date: Jul 2009
Location: Akron, OH
Posts: 220
Rep Power: 19 |
You have provided little information to diagnose your troubles, beyond 'checkMesh' output appears ok.
But based on what I do see, I would suggest trying one of the following as a first start: 1. Decrease the time step if running with a constant time step, and/or switch to adaptive time-stepping with a max CFL of 0.5 (just to be safe) 2. If you want to run with a CFL > 1.0, then you need to increase the number of 'nOuterCorrectors' to some number larger than 2. Ideally, you would set this to a very large number (e.g. 100) and control the number of temporal sub-iterations with 'residualControl', see... https://openfoamwiki.net/index.php/O...hm_in_OpenFOAM This is just a quick guess, as I see from you log file that the solution diverges shortly after the CFL numbers become large. |
|
Tags |
mesh 2d, pimplefoam |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
pimpleFoam runs slower than rhoPimpleFoam | Kosuke Seto | OpenFOAM Running, Solving & CFD | 3 | May 27, 2023 15:12 |
pisoFoam and pimpleFoam are unstable in foam-extend 4.0/4.1 (misunderstanding ?) | Kombinator | OpenFOAM Running, Solving & CFD | 4 | January 14, 2021 05:10 |
Crash with renumberMesh and pimpleFoam LES | jmt | OpenFOAM Running, Solving & CFD | 0 | December 4, 2019 16:31 |
naca12 laminar pimpleFoam | uni | OpenFOAM Running, Solving & CFD | 2 | March 17, 2018 08:17 |
pimpleFoam: turbulence->correct(); is not executed when using residualControl | hfs | OpenFOAM Running, Solving & CFD | 3 | October 29, 2013 09:35 |