|
[Sponsors] |
April 25, 2018, 04:23 |
GGI interpolation issues with foam-extend3.2
|
#1 |
New Member
Evelyn
Join Date: Nov 2017
Posts: 7
Rep Power: 9 |
Hi there, you helpful lot
I am trying to solve a problem regarding my FSI case based on the BeamInCrossFlow. I am using foam-extend 3.2. I have 2 meshes that I created via a third software. I made them into msh files and converted them for OpenFOAM. All looks fine in ParaView apart from the nodes of the two meshes not matching on the interface. However, I seem to have issues with GGI, or so says the log file of the fsi solver: Starting time loop Creating beamReport function object. History point ID: 0 History point coordinates: (0 0 0) Reference point coordinates: (0.45 0.15 -0.15) Seting inlet velocity Umax = 0.1 Time = 0.5 Create extended GGI zone-to-zone interpolator Checking fluid-to-solid face interpolator --> FOAM Warning : From function Foam::SutherlandHodgman::lineSegmentIntersection() in file algorithms/polygon/clipping/SutherlandHodgman.C at line 125 ub does not match with ua: delta: 2.05637e-15 : epsilon: 1e-15 --> FOAM Warning : From function Foam::SutherlandHodgman::lineSegmentIntersection() in file algorithms/polygon/clipping/SutherlandHodgman.C at line 125 ub does not match with ua: delta: 1.36985e-15 : epsilon: 1e-15 Fluid-to-solid face interpolation error: 95.3407 Checking solid-to-fluid point interpolator (GGI) Extended GGI, master point distance, max: 1e+15, avg: 9.06867e+10, min: -3.21149 Extended GGI, master point orientation (<0), max: 0.999999, min: -1, nIncorrectPoints: 11008/452106 --> FOAM FATAL ERROR: Master point addressing is not correct From function ExtendedGGIInterpolation::masterToSlavePointInterp olate(const Field<Type> pf) in file ./numerics/ggi/ExtendedGGIInterpolation/ExtendedGGIInterpolation.C at line 703. I know this topic came up on another thread under HronTurekFsi3 foam-extend3.1, but it doesn't apply to me, as I have imported a mesh that hasn't been created using blockMesh. Could anyone tell me how to identify the problem and how to solve it? I am fairly new to OpenFOAM, so I am totally lost. Any help would be much appreaciated. Kind regards |
|
June 5, 2018, 13:50 |
|
#2 |
New Member
Joe Mattson
Join Date: Nov 2016
Location: Ithaca, NY
Posts: 3
Rep Power: 10 |
Did you ever resolve this issue? I'm facing the same problem.
|
|
August 14, 2018, 05:04 |
|
#3 |
Member
Sangeet
Join Date: Jun 2017
Location: India
Posts: 43
Rep Power: 9 |
Hello,
I have the exact same problem, my fluid and solid meshes are from snappyHexMesh. Could you please tell me if you managed to resolve this issue? |
|
September 21, 2019, 02:26 |
|
#4 |
New Member
Pradeepkumar Jagdale
Join Date: Jun 2019
Location: Kharagpur
Posts: 7
Rep Power: 7 |
This problem occurs due to gap between fluid-solid interface. Open both Fluid and solid in Paraview by command
paraFoam -nativeReader (in fluid folder) ans see whether there is a gap between the fuid and solid surface. If gap is found edit the geometry. Thank you |
|
Tags |
beamincrossflow, extend3.2, fsi, ggi |
Thread Tools | Search this Thread |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
[Salome] Salome import "Cannot find file "points" in directory..." | mismichael | OpenFOAM Meshing & Mesh Conversion | 6 | June 24, 2024 04:17 |
[mesh manipulation] RefineMesh Error and Foam warning | jiahui_93 | OpenFOAM Meshing & Mesh Conversion | 4 | March 3, 2018 12:32 |
[OpenFOAM] Take derivative of mean velocity in paraFoam | hiuluom | ParaView | 13 | April 26, 2016 07:44 |
[snappyHexMesh] Problem with parallel run of snappyHexMesh | Lorenzo92 | OpenFOAM Meshing & Mesh Conversion | 5 | April 15, 2016 05:12 |
GGI in OpenFOAM-1.5-dev | philippose | OpenFOAM Running, Solving & CFD | 14 | November 13, 2011 15:55 |