|
[Sponsors] |
[snappyHexMesh] Problem with SnappyHexMesh and force monitoring |
|
LinkBack | Thread Tools | Search this Thread | Display Modes |
March 23, 2021, 18:46 |
Problem with SnappyHexMesh and force monitoring
|
#1 |
New Member
Yousef
Join Date: Dec 2015
Posts: 14
Rep Power: 10 |
Hello OpenFoam users.
Just wondering if anyone else is facing an issue with unrealistic force monitor output that occurs when executing snappyHexMeshing in parallel. My code solves with no issues in pimpleFoam and the forces calculated in paraFoam are reasonable, so its not an issue with the solver or the case setup. But the forces generated by the force monitor in forces.dat are off by several orders of magnitude. The issue resolves when running the case with snappyHexMesh in serial. The following warning appears in SHM parallel: From function Foam::treeBoundBox::treeBoundBox(const Foam::UList<Foam::Vector<double> >&) in file meshes/treeBoundBox/treeBoundBox.C at line 136 cannot find bounding box for zero-sized pointField, returning zero Any insight would be greatly appreciated |
|
Thread Tools | Search this Thread |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Offset on the force derived for each cylinder composing a float | ConstanceC | OpenFOAM Post-Processing | 0 | October 14, 2020 04:29 |
Force SnappyHexMesh to match the surface | Magistrane | OpenFOAM Pre-Processing | 2 | September 30, 2020 06:39 |
snappyHexMesh parallel, avoid reconstructParMesh | Tom Lauriks | Main CFD Forum | 2 | April 27, 2020 12:47 |
[snappyHexMesh] Problem with skewd faces in SnappyHexMesh | Friendly | OpenFOAM Meshing & Mesh Conversion | 1 | June 19, 2019 08:05 |
[snappyHexMesh] Problem with decomposePar, snappyHexMesh | luca1992 | OpenFOAM Meshing & Mesh Conversion | 12 | August 23, 2017 20:06 |