View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001278 | OpenFOAM | Bug | public | 2014-04-29 09:51 | 2014-05-02 11:11 |
| Reporter | Assigned To | ||||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | resolved | Resolution | no change required | ||
| Platform | Unix | OS | Ubuntu | OS Version | 12.04 | 13.10 | |
| Summary | 0001278: checkMesh screws up when dealing with a mesh with cyclicACMI boundaries | ||||
| Description | In my case I have successfully used cyclicACMI BC in order to compute the field inside a circular duct that suddenly become squared (but the same issue is present in all the other cyclicACMI cases I have tried). In this case of course I have a cyclicACMI in order to switch from a circular to a squared geometry, and one of the cyclicACMI surfaces is completely coupled with the opposite boundary, while the other has a portion that is defined as wall. Even if the computations are ok, running a checkMesh on the mesh leads to an error on boundary openess: Boundary openness (-6.686007e-17 -0.01217516 -3.776272e-17) possible hole in boundary description. This issue is present in all the cases I've run even if results are ok and cyclicACMI bc work well | ||||
| Steps To Reproduce | 1. Create the computational domain in pointwise as a series of different polyMeshes 2. Run mergeMesh to merge the different portions 3. Run topoSet in order to create faceSets and faceZones with the cyclicACMI bcs 4. Run createBaffles in order to split the cyclicACMI bcs in the coupled regions and the non-coupled (in all my cases wall) regions 5. Running a checkMesh now will lead to the error described above 6. Run createPatch to get rid of empty patches generated from the above process 7. Running a checkMesh now will lead again to the error described above 8. Run simpleFoam, and everything works! | ||||
| Tags | No tags attached. | ||||
|
|
The ACMI only gets coupled on the finite volume level - on the polyMesh level it does not know about the 'mixing' of boundary conditions and so sees duplicate sets of faces. This causes the warning about the openness. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2014-04-29 09:51 |
|
New Issue | |
| 2014-05-02 11:11 |
|
Note Added: 0003039 | |
| 2014-05-02 11:11 |
|
Status | new => resolved |
| 2014-05-02 11:11 |
|
Fixed in Version | => 2.3.x |
| 2014-05-02 11:11 |
|
Resolution | open => no change required |
| 2014-05-02 11:11 |
|
Assigned To | => user4 |
