View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0004115 | OpenFOAM | Bug | public | 2024-07-20 16:11 | 2024-07-20 16:38 |
Reporter | cgoessni | Assigned To | henry | ||
Priority | low | Severity | minor | Reproducibility | always |
Status | closed | Resolution | no change required | ||
Product Version | dev | ||||
Summary | 0004115: pointLevel and cellLevel invalid after mergeMeshes | ||||
Description | When running mergeMeshes on two or more snappyHexMesh generated meshes, pointLevel and cellLevel seem to be invalid, which leads to crashes in some circumstances. | ||||
Steps To Reproduce | Run the attached case. Although it does not crash, one can observe the following awkward results: 1.) While the mesh has 47,296 cells, cellLevel only contains a list of length 22,192. 2.) While the mesh as 51,837 points, pointLevel file only contains a list of length 23,505. 3.) The entries in processor0/constant/polyMesh/cellLevel contain unrealistic values, here I see: 2604 ( 1335766454 -796560312 -1922004567 1063789059 1064700592 -1083439681 -733203955 1064569157 83007612 ... While this case does not crash, few of our engine meshes, generated in a similar way, make decomposePar crash with the following stack trace: Number of processor faces = 126314 Max number of cells = 29602 (1.32773% above average 29214.1) Max number of processor patches = 55 (348.98% above average 12.25) Max number of faces between processors = 5173 (96.5768% above average 2631.54) #0 Foam::error::printStack(Foam::Ostream&) at ??:? #1 Foam::sigSegv::sigHandler(int) at ??:? #2 ? in "/lib64/libc.so.6" #3 Foam::hexRef8Data::hexRef8Data(Foam::IOobject const&, Foam::hexRef8Data const&, Foam::List<int> const&, Foam::List<int> const&) at ??:? #4 Foam::domainDecomposition::writeProcs(bool) const at ??:? #5 Foam::domainDecomposition::writeReadDecompose(bool, bool) at ??:? #6 Foam::multiDomainDecomposition::readDecompose(bool) at ??:? #7 ? at ??:? #8 __libc_start_main in "/lib64/libc.so.6" #9 ? at ??:? Removing cellLevel and pointLevel files manually before decomposePar resolves the issue. | ||||
Tags | No tags attached. | ||||
|
|
|
Simply delete the pointLevel and cellLevel files or better still set snappyHexMesh to not write them. |
Date Modified | Username | Field | Change |
---|---|---|---|
2024-07-20 16:11 | cgoessni | New Issue | |
2024-07-20 16:11 | cgoessni | File Added: cylinderTest.tgz | |
2024-07-20 16:38 | henry | Assigned To | => henry |
2024-07-20 16:38 | henry | Status | new => closed |
2024-07-20 16:38 | henry | Resolution | open => no change required |
2024-07-20 16:38 | henry | Note Added: 0013317 |