Closed kastnerp closed 3 months ago
Quick question: What does checkMesh -allGeometry -allTopology
reveal on both cases?
Thanks, Bruno!
Case working: https://github.com/kastnerp/Eddy3D-BoxDomainIssue/blob/main/Eindhoven_51.44844_5.46475_dir0/0/checkMesh.log Case crashing: https://github.com/kastnerp/Eddy3D-BoxDomainIssue/blob/main/Eindhoven_51.44844_5.46475_dir100/100/checkMesh.log
Ok, I figured it would have something to do with the mesh (as it always does). Would you possibly know of any suggestions w.r.t. snappyHexMeshDict to make this more robust? The building geometries come straight from OpenStreetMaps, there is not much I can do here if I want to keep my pre-processing effort minimal.
Sidenote: Turning snapping off via
castellatedMesh true;
snap false;
does not solve the problem either. Hence, I wasn't sure if there something more fundamental going wrong.
Best,
Patrick
Quick answer:
Checking topology...
Boundary definition OK.
Cell to face addressing OK.
Point usage OK.
Upper triangular ordering OK.
Face vertices OK.
Topological cell zip-up check OK.
Face-face connectivity OK.
<<Writing 12 cells with zero or one non-boundary face to set oneInternalFaceCells
*Number of regions: 13
The mesh has multiple regions which are not connected by any face.
<<Writing region information to "0/cellToRegion"
<<Writing region 0 (fully disconnected) with 1 cells to cellSet region0
<<Writing region 1 (fully disconnected) with 1 cells to cellSet region1
<<Writing region 2 (fully disconnected) with 1 cells to cellSet region2
<<Writing region 3 (fully disconnected) with 1 cells to cellSet region3
<<Writing region 4 (fully disconnected) with 1 cells to cellSet region4
<<Writing region 5 (fully disconnected) with 1 cells to cellSet region5
<<Writing region 6 (fully disconnected) with 1 cells to cellSet region6
<<Writing region 7 (fully disconnected) with 1 cells to cellSet region7
<<Writing region 8 (fully disconnected) with 1 cells to cellSet region8
<<Writing region 9 (fully disconnected) with 1 cells to cellSet region9
<<Writing region 10 (fully disconnected) with 1 cells to cellSet region10
<<Writing region 11 (fully disconnected) with 1 cells to cellSet region11
<<Writing region 12 (fully disconnected) with 944059 cells to cellSet region12
Fully disconnected regions cannot be solved for, hence the crash while solving the matrix:
ZN4Foam17DICPreconditioner15calcReciprocalDERNS_5FieldIdEERKNS_9lduMatrixE [0x106b488+0xc8]
i.e. Foam::DICPreconditioner::calcReciprocal(FieldId, lduMatrix)
Solution: Use subsetMesh
to extract region12
.
Dear Bruno,
I am the developer of Eddy3D and I was wondering if you would be able to look at an issue we are experiencing. I copied two cases of isothermal, external wind analysis for buildings with
simpleFoam
here: https://github.com/kastnerp/Eddy3D-BoxDomainIssueThis uses the same building geometry, one case runs fine, the other one doesn't even start. The difference between the two is the rotation of the wind tunnel.
For the crashing case we get:
I know from experience the error usually refers to some boundary conditions problem or some division by 0. However, here we're using identical BCs, same geometry, really only the wind tunnel in rotated. Do you see any issue with the setup that might be an oversight?
Thank you very much for your time.
Best,
Patrick