CFD Online Logo CFD Online URL
www.cfd-online.com
[Sponsors]
Home > Forums > Software User Forums > OpenFOAM > OpenFOAM Community Contributions > OpenFOAM CC Toolkits for Fluid-Structure Interaction

[solids4Foam] zoneA point addressing is not correct

Register Blogs Community New Posts Updated Threads Search

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
Old   July 22, 2021, 18:00
Post zoneA point addressing is not correct
  #1
Member
 
Mike Tree
Join Date: Feb 2016
Location: Charlotte, NC
Posts: 37
Rep Power: 10
treem22 is on a distinguished road
I'm attempting to simulate flow through a deformable bifurcating artery using solids4Foam. I've successfully compiled solids4Foam with OpenFOAM-v1912 and have run a few tutorials. I get a few warnings, but things seem to be running fine.

Now that I'm moving to my own application, I receive the following error:
Code:
Interpolating face values using AMI
Create AMI zone-to-zone interpolator
AMI: Creating addressing and weights between 341040 source faces and 381744 target faces
AMI: using globalPolyPatch
AMI: Patch source sum(weights) min:0 max:1.20346469417 average:1.00020820214
AMI: Patch target sum(weights) min:0.747306539956 max:1.04230453565 average:0.998972235832
interface-to-interface face error: 0.00021922629281
Total force on fluid interface 0: (0 0 0)
Total force on solid interface 0: (0 0 0)

Evolving solid solver
Corr 0, relative residual = 0
FDICPCG: Solving for D, Initial residual = 0, Final residual = (0 0 0), No outer iterations = 0
 Max relative residual = 0, Relative residual = 0, enforceLinear = false
Interpolating point values using AMI
zoneA point orientation (< 0), max: 2.56982010576e-316, min: -0.999999997617, nIncorrectPoints: 1/22051
[2]
[2]
[2] --> FOAM FATAL ERROR:
[2] zoneA point addressing is not correct
[2]
[2]     From function void
Foam::amiInterfaceToInterfaceMapping::transferPointsZoneToZone
(                                                                                                                  
     ...                                                                                                             ) const                                                                                                             [2]     in file fluidSolidInterfaces/fluidSolidInterface/interfaceToInterfaceMapping/amiInterfaceToInterfaceMapping/amiInterfaceToInterfaceMappingTemplates.C at line 193.
[2]                                                                                                                
FOAM parallel run aborting
A few things I'm noticing:
  1. AMI source patches have a weight as low as 0. I'm assuming the source patches are the fluid side? I'm assuming a weight of 0 means that these patches are not contributing to the transfer of pressure to the solid? This is fine, I guess, as long as there aren't a lot of patches under this scenario
  2. Upon beginning its interpolation between the fluid mesh interface and the solid mesh interface, the AMI routines first check to see if there is any penetration between the two interfaces. In my case, it found a single point on the fluid mesh that is BARELY penetrating the solid mesh interface. Is this a correct interpretation of what's happening?

Assuming those observations are correct, I have a few questions:
  1. If I were to switch to GGI or RBF for my interfaceTransferMethod, is interpenetrating surface meshes still an issue? Of course, I would have to switch to using foam-extend 4.0 instead of OpenFOAM-v1912, correct?
  2. If I stick with OpenFOAM-v1912 and AMI, how can I create an interface surface mesh that is the EXACT SAME such that not only is there no interpenetration, but the interpolation will be minimal? I'm no snappyHexMesh wizard, so any pointers are helpful here.

Finally, I attached an image of the setup. ParaView visualization looks like there is a lot of interpenetration, but the code output highlights only 1 point.
Attached Images
File Type: jpg Picture1.jpg (62.6 KB, 9 views)
treem22 is offline   Reply With Quote

Old   August 11, 2021, 16:34
Default
  #2
Member
 
Mike Tree
Join Date: Feb 2016
Location: Charlotte, NC
Posts: 37
Rep Power: 10
treem22 is on a distinguished road
I remeshed each of the fluid and solid domains and am no longer confronted with this error. I believe it was simply that there was some overlap that the AMI interpolation could not handle at initialization.
treem22 is offline   Reply With Quote

Old   February 2, 2023, 08:36
Default
  #3
Member
 
Thangam Natarajan
Join Date: Dec 2010
Location: Perth
Posts: 70
Rep Power: 16
Thangam is on a distinguished road
Can you share a simple working case please? I'm working on something similar but the simulation blows up after a few iterations with floating point exception. I think my settings arent favoring displacements as I see a very large number just before the simulation explodes i.e
Code:
Maximal accumulated displacement of interface 0: 1812.38
Thangam is offline   Reply With Quote

Reply


Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are Off
Pingbacks are On
Refbacks are On


Similar Threads
Thread Thread Starter Forum Replies Last Post
Sampling air passing through multiple windows b.simpson OpenFOAM Post-Processing 3 September 4, 2020 08:07
Define Profile, using mass fraction of different point Kosch Fluent UDF and Scheme Programming 0 October 2, 2017 20:10
CFD-post: defining (or projecting) point on surface bongbang CFX 1 April 1, 2015 12:16
a reconstructPar issue immortality OpenFOAM Post-Processing 8 June 16, 2013 11:25
an odd(at least for me!) reconstructPar error on a field immortality OpenFOAM Running, Solving & CFD 3 June 3, 2013 22:36


All times are GMT -4. The time now is 08:44.