whoa there, pardner!
Your request has been blocked due to a network policy.
Try logging in or creating an account here to get back to browsing.
If you’re running a script or application, please register or sign in with your developer credentials here. Additionally make sure your User-Agent is not empty and is something unique and descriptive and try again. if you’re supplying an alternate User-Agent string, try changing back to default as that can sometimes result in a block.
You can read Reddit’s Terms of Service here.
if you think that we’ve incorrectly blocked you or you would like to discuss easier ways to get the data you want, please file a ticket here.
when contacting us, please include your ip address which is: 95.214.216.211 and reddit account
Plaxis 3D — как решить ошибку при разбитии сетки КЭ
Здравствуйте форумчане. При разбитии сетки КЭ вылазит следующая ошибка:
Meshing failed with the following error:
Meshing failed. Check your model for inaccurately snapped objects, or try using different local coarseness.
Bounding box around problem area: (81.916; 70.942; -7.934), (91.333; 75.000; -7.916).
При удалении одного элемента (нужного в дальнейшем) — проблема исчезает! Подскажите пожалуйста как решить данную проблему.
Просмотров: 5653
Meshing problem
I’m trying to mesh race car.
Everything went ok before we added diffuser to the floor.
After that meshing time increased 3 times and I got errors after checking mesh and cannot do potentialFoam.
Please help.
// * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * // Create time Create polyMesh for time = 0 Time = 0 Mesh stats points: 8311921 faces: 22546314 internal faces: 21680401 cells: 7144048 faces per cell: 6.19071 boundary patches: 6 point zones: 0 face zones: 0 cell zones: 0 Overall number of cells of each type: hexahedra: 6305947 prisms: 113448 wedges: 2 pyramids: 0 tet wedges: 4703 tetrahedra: 68 polyhedra: 719880 Breakdown of polyhedra by number of faces: faces number of cells 4 38309 5 31075 6 143250 7 131096 8 40681 9 231452 10 2317 11 485 12 79586 13 74 14 115 15 20545 16 2 17 4 18 885 21 4 Checking topology. Boundary definition OK. Cell to face addressing OK. Point usage OK. Upper triangular ordering OK. Face vertices OK. *Number of regions: 141 The mesh has multiple regions which are not connected by any face.
Attached Images
| Screenshot_30.png (74.5 KB, 26 views) | |
| Screenshot_29.png (61.7 KB, 24 views) |
New Member
Join Date: Nov 2021
Location: Saint-Petersburg
Rep Power: 4
If ignore it and run mpirun potentialFoam, I get this error:
cannot solve incomplete matrix, no diagonal or off-diagonal coefficient
Senior Member
Join Date: Dec 2019
Location: Cologne, Germany
Rep Power: 8
could you post the checkMesh-result from the simulation that runs without a problem?
New Member
Join Date: Nov 2021
Location: Saint-Petersburg
Rep Power: 4
Originally Posted by geth03
could you post the checkMesh-result from the simulation that runs without a problem?
Hi.
Here it is:
/*---------------------------------------------------------------------------*\ ========= | \\ / F ield | OpenFOAM: The Open Source CFD Toolbox \\ / O peration | Website: https://openfoam.org \\ / A nd | Version: 9 \\/ M anipulation | \*---------------------------------------------------------------------------*/ Build : 9-a0f1846504f2 Exec : checkMesh Date : Dec 05 2021 Time : 13:04:48 Host : "openfoam-vm" PID : 6527 I/O : uncollated Case : /home/anton/dif9 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: 6266492 faces: 16854825 internal faces: 16205092 cells: 5317779 faces per cell: 6.21687 boundary patches: 6 point zones: 0 face zones: 0 cell zones: 0 Overall number of cells of each type: hexahedra: 4616017 prisms: 86743 wedges: 0 pyramids: 0 tet wedges: 5159 tetrahedra: 28 polyhedra: 609832 Breakdown of polyhedra by number of faces: faces number of cells 4 27460 5 23128 6 133257 7 112616 8 40010 9 184467 10 3022 11 1055 12 66868 13 117 14 185 15 16753 16 6 17 4 18 880 21 4 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 frontAndBack 1640 1792 ok (non-closed singly connected) inlet 120 143 ok (non-closed singly connected) outlet 120 143 ok (non-closed singly connected) lowerWall 30740 32145 ok (non-closed singly connected) upperWall 400 451 ok (non-closed singly connected) motorBike 616713 665767 ok (non-closed singly connected) Checking geometry. Overall domain bounding box (-6 -0.69 -2.5) (14 4.31 2.5) Mesh has 3 geometric (non-empty/wedge) directions (1 1 1) Mesh has 3 solution (non-empty) directions (1 1 1) Boundary openness (7.98522e-17 6.70506e-16 2.90347e-16) OK. Max cell openness = 7.42443e-16 OK. Max aspect ratio = 37.0962 OK. Minimum face area = 1.43585e-08. Maximum face area = 0.255204. Face area magnitudes OK. Min volume = 3.02126e-10. Max volume = 0.125899. Total volume = 493.879. Cell volumes OK. Mesh non-orthogonality Max: 64.8274 average: 9.24804 Non-orthogonality check OK. Face pyramids OK. ***Max skewness = 8.86648, 5 highly skew faces detected which may impair the quality of the resultsPC-Progress Discussion Forums
How can I check where or what the error is and correct it? I have to admit that I am trying to build a rather large, irregularly shaped domain with 2 sublayers (small watershed) by importing a DEM.
Mirek Posts: 498 Joined: Sat Mar 16, 2002 4:00 pm Location: Czech Republic Contact:
Post by Mirek » Thu Oct 23, 2008 6:28 pm
This error can be caused for example by two boundary points with almost identical coordinates, i.e. they look like a single point but there actually are two different points. Their distance can be extremely small, which can cause problems during FE-mesh generation.
I suggest that you should:
1/ Check duplicity of your boundary points (if the number of points is not too large): Select each point by the rectangle and pres Alt + Enter to display the “Edit Points” dialog. Check that there is the only one number in the field “Point No.”, otherwise you have overlapping points.
2/ Download and install the latest version of HYDRUS (1.07) which contains several improvements and fixes of the FE-mesh generator http://www.pc-progress.cz/Fr_Hydrus3D_Downloads.htm
3/ If your problems continue, please, send me your project, I’ll look at it.
Luisa Posts: 35 Joined: Tue Mar 06, 2007 8:22 pm Location: USA
Post by Luisa » Thu Oct 23, 2008 6:58 pm
I am using version 1.07 and will try your first option although I do have a lot of boundary points. I will get back to you if I can't figure out the problem.
Thanks a lot! Luisa
Liesbeth Posts: 1 Joined: Fri Feb 05, 2010 4:57 pm Location: Belgium
Post by Liesbeth » Mon Feb 08, 2010 10:06 am
I have some problems with the Fe-Mesh generation for my 2D-project (with a general domain definition). I always got the error message of internal error nr. 70 (the mesh on surface no. 1 fails to satisfy the model precision criterion…)
The project concerns a 2D-transect of +/- 1000 m length and a depth of 120 m. The upper surface layer follows the topography and contains a node every 5 m, exept at the side of the river, where we added nodes every meter over a distance of 100 m. This line (upper surface layer) is copied 10 times and placed at 0.1 m distance of each other in order to specify the root distribution precisely over a distance of 1m in the upper layer. We also specified some additional nodes (1 m distance) at the side boundary lines in the upper layer (over a distance of 5 m). For the rest, there are only nodes at the corners of the lower surface layer. At the river side, mesh refinement (S=0.1) was inserted at the boundary nodes and some extra nodes which are lying just near the boundary.
I tried already to change the mesh-parameters like the stretching factor, the smoothing factor,… but with no result. Lowering the epsilon value (which is not recommended) gave already better results, but I still get the error message. Also a simpler version of the project (without copies of the upper layer) could not help to solve the problem.
The strange thing is that similar projects were run a year ago by someone else without any problems. But if we remove the mesh in these ‘old’ projects and try to generate again a mesh, we got the same error message.
Any idea where the problem is situated?
Thanks in advance,
Liesbeth