View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0004142 | OpenFOAM | Bug | public | 2024-08-29 13:03 | 2024-09-03 10:50 |
| Reporter | cgoessni | Assigned To | will | ||
| Priority | low | Severity | minor | Reproducibility | always |
| Status | resolved | Resolution | fixed | ||
| Product Version | dev | ||||
| Fixed in Version | dev | ||||
| Summary | 0004142: MeshPhi does not work with meshToMesh | ||||
| Description | When trying to use MeshPhi correction, we get crashes / error messages after a meshToMesh mapping | ||||
| Steps To Reproduce | Set correctMeshPhi to yes in fluid/engine2Valve2D/system/fvSolution:PIMPLE: ... Creating patchToPatch between source patch NCC_ev_port_on_nonCouple_ep_ev and target patch NCC_ev_port_on_nonCouple_ep_ev using intersection Creating patchToPatch between source patch NCC_ev_port_on_nonCouple_ev_ep and target patch NCC_ev_port_on_nonCouple_ev_ep using intersection Creating patchToPatch between source patch nonConformalError_on_nonCouple_iv_cyl and target patch nonConformalError_on_nonCouple_iv_cyl using intersection Creating patchToPatch between source patch nonConformalError_on_nonCouple_cyl_iv and target patch nonConformalError_on_nonCouple_cyl_iv using intersection Creating patchToPatch between source patch nonConformalError_on_nonCouple_ev_cyl and target patch nonConformalError_on_nonCouple_ev_cyl using intersection Creating patchToPatch between source patch nonConformalError_on_nonCouple_cyl_ev and target patch nonConformalError_on_nonCouple_cyl_ev using intersection Creating patchToPatch between source patch nonConformalError_on_nonCouple_ip_iv and target patch nonConformalError_on_nonCouple_ip_iv using intersection Creating patchToPatch between source patch nonConformalError_on_nonCouple_iv_ip and target patch nonConformalError_on_nonCouple_iv_ip using intersection Creating patchToPatch between source patch nonConformalError_on_nonCouple_ep_ev and target patch nonConformalError_on_nonCouple_ep_ev using intersection Creating patchToPatch between source patch nonConformalError_on_nonCouple_ev_ep and target patch nonConformalError_on_nonCouple_ev_ep using intersection - selecting all cells Time = 0.1CAD PIMPLE: Iteration 1 Updating scale field patchToPatch: Calculating couplings between 66 source faces and 66 target faces Source min/average/max coverage = 1/1/1 Target min/average/max coverage = 1/1/1 Source average openness/error/depth/angle = 2.602083464e-17/7.485941525e-16/1.204792225e-16/0 Source max openness/error/depth/angle = 1.431146624e-16/7.328868186e-15/2.376845029e-15/0 132 couplings calculated in 0.01s patchToPatch: Calculating couplings between 66 source faces and 66 target faces Source min/average/max coverage = 1/1/1 Target min/average/max coverage = 1/1/1 Source average openness/error/depth/angle = 2.602083464e-17/1.127199255e-15/1.771465797e-16/0 Source max openness/error/depth/angle = 1.431146624e-16/7.327820108e-15/2.376845029e-15/0 132 couplings calculated in 0.01s patchToPatch: Calculating couplings between 16 source faces and 16 target faces Source min/average/max coverage = 1/1/1 Target min/average/max coverage = 1/1/1 Source average openness/error/depth/angle = 1.084202172e-17/3.608550042e-16/9.708664934e-17/0 Source max openness/error/depth/angle = 1.734723476e-16/2.92653949e-15/1.29190244e-15/0 32 couplings calculated in 0s patchToPatch: Calculating couplings between 16 source faces and 16 target faces Source min/average/max coverage = 1/1/1 Target min/average/max coverage = 1/1/1 Source average openness/error/depth/angle = 2.168404345e-17/2.818186644e-16/2.6708794e-16/0 Source max openness/error/depth/angle = 1.734723476e-16/2.484929023e-15/2.101508562e-15/0 32 couplings calculated in 0s fvMeshStitcher: Connecting smoothSolver: Solving for MeshPhi, Initial residual = 0.9983484782, Final residual = 0.009959911311, No Iterations 345 --> FOAM FATAL ERROR: Face data requested from a non-face correction info FOAM exiting The same happens for one of our real engine cases in a similar setup. | ||||
| Tags | No tags attached. | ||||
|
|
The problem here is that this case is creating NCC interfaces on patches which have not been point separated; specifically, the intake and exhaust NCC-s. NCC is in general not reliable for a variety of reasons (this being one of them) if the patches involved share points. The error message could be better, but this is actually an issue of case setup. Running splitBaffles in this case after createBaffles fixes the issue. I have made this change to the tutorial. https://github.com/OpenFOAM/OpenFOAM-dev/commit/1f0fef23881fb6daa548aeec19e84d89943ed678 In general, this scenario is quite unlikely to occur. NCC-s are always point separated, otherwise they would not be non-conformal. This case is odd in that it creates an NCC interface on a patch that is actually conformal. Clearly, ordinarily, this would not be a good idea. As I understand it, it is only done in this instance to demonstrate the workflow for a more complex configuration in which this NCC interface is necessary (i.e., constructing a complete mesh from separately meshed sub-modules), and for which the points are truly separate. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2024-08-29 13:03 | cgoessni | New Issue | |
| 2024-09-03 10:49 | will | Assigned To | => will |
| 2024-09-03 10:49 | will | Status | new => resolved |
| 2024-09-03 10:49 | will | Resolution | open => fixed |
| 2024-09-03 10:49 | will | Fixed in Version | => dev |
| 2024-09-03 10:49 | will | Note Added: 0013391 | |
| 2024-09-03 10:50 | will | Note Edited: 0013391 |
