Trouble with running FSI with buoyantPimplFoam (request for pointVectorField pointDisplacement from objectRegistry region0 faild)

Hi all,

While attempting to run a two-way FSI coupling of buoyantPimplFoam and an in-house solid mechanics solver, I encountered the following errors. I noticed that these errors were already discussed in the discourse but in a different context and I did not find a solution that may help me. Anyone knows what this may be due to? I have attached the entire log file, xml file, along with the case folder containing only the Fluid portions of the files. The solid ones are not necessary for anyone to reproduce the problem. Thanks for your help in advance.

Fluid.log (3.6 KB)

Starting time loop

—[preciceAdapter] Loaded the OpenFOAM-preCICE adapter v1.0.0.
—[preciceAdapter] Reading preciceDict…
[precice] This is preCICE version 2.2.0
[precice] Revision info: v2.2.0
[precice] Configuration: Release (Debug and Trace log unavailable)
[precice] Configuring preCICE with configuration "precice-config.xml"
[precice] I am participant "Fluid"
→ FOAM Warning : **
** From function void adapterInfo(std::string, std::string)

** in file Utilities.C at line 50**
** e[31mError (deferred - will exit later) in the preCICE adapter: e[0m**

** request for pointVectorField pointDisplacement from objectRegistry region0 failed**
** available objects of type pointVectorField are**
0()

Courant Number mean: 0 max: 0
Time = 0.25

diagonal: Solving for rho, Initial residual = 0, Final residual = 0, No Iterations 0
DILUPBiCGStab: Solving for h, Initial residual = 3.53967e-05, Final residual = 2.30722e-13, No Iterations 1
GAMG: Solving for p_rgh, Initial residual = 0.170739, Final residual = 0.000820212, No Iterations 5
diagonal: Solving for rho, Initial residual = 0, Final residual = 0, No Iterations 0
time step continuity errors : sum local = 0.0104676, global = 1.08446e-17, cumulative = 1.08446e-17
GAMG: Solving for p_rgh, Initial residual = 0.838498, Final residual = 9.47089e-09, No Iterations 14
diagonal: Solving for rho, Initial residual = 0, Final residual = 0, No Iterations 0
time step continuity errors : sum local = 6.47517e-08, global = 4.02935e-19, cumulative = 1.12475e-17
ExecutionTime = 0.41 s ClockTime = 2 s

→ FOAM FATAL ERROR: **
e[31mError in the preCICE adapter: e[0m
There was a problem while configuring the adapter. See the log for details.
** pointVectorField are

0()

** From function void adapterInfo(std::string, std::string)**
** in file Utilities.C at line 32.**

FOAM exiting

buoyantPimplFoam.zip (1.3 MB)
precice-config (4).xml (2.5 KB)

Regards,
Satish

Hi @Satish_Chimakurthi,

we used to have the same issue when OpenFOAM was separating between pimpleFoam and pimpleDyMFoam, and trying to do FSI with a solver that does not support moving meshes.

Are you sure that buoyantPimpleFoam supports moving meshes? I have the impression that it does not.

Hi @Makis,

Ah! OK. I am not sure if buoyantPimpleFoam supports moving meshes actually. I was actually using a different solver to run an implicit coupling use case and that did not work. Therefore, I reproduced the case settings in buoyantPimpleFoam (because my case involves gravity) and naively thought that this new solver would work for FSI. If you think that it does not, then, I must look for another solver in which I can use gravity.

Do you know of another solver that supports not only implicit FSI couplings but also allows us to specify gravity load? My problem is pretty simple - a tank of water under hydrostatic conditions in which there is an inflating balloon.

Thanks in advance,
Satish

I think that people have used, for example, interFoam or twoPhaseEulerFoam (see e.g., 6-way coupling of DEM+CFD+FEM with preCICE (Alban Rousset, preCICE Workshop 2020) - YouTube), which sounds pretty close to what you need.

Other than that, maybe you can find something in the list of OpenFOAM solvers (not sure which of them actually work with our adapter, but I would expect many of them to work): A.1 Standard solvers

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.