openfoam-adapter
openfoam-adapter copied to clipboard
Different dimensions for dimensions Issue in FSI when turbulence model is used - OpenFOAM adapter
Hi there,
This issue was found when I was doing a FSI simulation using OpenFOAM v7 / CalculiX v2.15 / preCICE v2.0.0. Please let me lead you to this discourse-post for more details.
As suggested by @MakisH , a brief introduction to the settings of turbulence model in OpenFOAM is to simply turn on the turbulence by setting /constant/turbulenceProperties
file, using:
simulationType RAS;
RAS
{
RASModel kOmegaSST;
turbulence on;
}
Of course, the corresponding initial conditions such as k
, omega
, nut
, p
and U
are well defined in the 0/
directory.
When the turbulence model is turned on, the FSI simulation stops at the 2nd iteration of the first time step of the coupling (shown in the figure in the post)
Interestingly however, when I turned off the turbulence (switch to laminar
):
simulationType laminar;
The FSI simulation went well and no errors are reported. However, the results are definitely not I'm expecting since the turbulent behaviours cannot be well resolved in my FSI simulation.
As @MakisH said, I do also suspect this issue might be originated from the OpenFOAM adapter side, so I'm looking for help from developers.
Should you requires more information please contact me directly and I'm happy to assists.
This issue has been mentioned on preCICE Forum on Discourse. There might be relevant details there:
https://precice.discourse.group/t/different-dimensions-for-dimensions-issue/535/6
I cannot reproduce this issue with OpenFOAM v2012 and since I have at the moment no foundation version installed I cannot try with another OpenFOAM version. Are you tied to use OpenFOAM v7?
Yes, I use OpenFOAM v7. New updates: I also implemented other 3 types of turbulence models : SA one equation / k-epsilon / k-omega. None of them throw back any dimension mismatch errors.
I'm having the same issue with OpenFOAM v7 and kOmegaSST for turbolence.
I also tried with kOmega and I get MPI_ERR_TRUNCATE.
There are any news for fixing the dimensions error for kOmegaSST?
I am having the same issue with OF10 and Calculix using kOmegaSST turbulence model. Is there any news regarding this?
If I understand correctly, this seems to be specific to the Foundation versions.
As I wrote in the preCICE forum, I would assume that the operator=
of some related fields modifies the dimensions. So, every time we call it when reading a checkpoint, we unintentionally modify the dimensions. Of course, the whole checkpointing concept is something that OpenFOAM would not expect under normal operation.
Another user reported that with OpenFOAM v2212:
-
kOmegaSST
fails with this issue -
kOmega
works -
laminar
works
In any case, this only affects checkpointing, i.e., only implicit coupling (explicit should work with any turbulence model). This is only a software issue, which we don't yet understand.
Yes i have the same exact issue with komega sst on OpenFOAM v2312
Hello @MakisH I still have the same problem with the K-omega sst and the OpenFOAM adapter, did you manage to figure out where is the issue, please?
Hi! No, we have not yet looked into it. It is clear that we need to fix it, it is near the top of the list, but we currently have other priorities.
Any clues or contributions in this direction are welcome! :hugs:
@KariimAhmed let's look into this together. I think that, by fixing this, we will fix more strange issues. But first, I need to be able to reproduce it.
I modified our flow-over-heated-plate
case, but I cannot yet trigger the issue with v2312. Could you please help me modify the case so that it triggers it?
https://github.com/precice/tutorials/pull/476
This issue has been mentioned on preCICE Forum on Discourse. There might be relevant details there:
https://precice.discourse.group/t/fsi-openfoam-my-solver-using-python/1823/2
@MakisH Thanks for considering this issue, the problem is triggered with me when I use the K-omega sst with my flapping foil with FSI. Also when using k-omega it simulates some time steps then it diverges and crashes, only the laminar is working fine. Concerning the case you mentioned I don't know exactly how can the issue be triggered, I saw that people are reporting this issue when using turbulent models in different cases but we don't know why this happens.
It is clear that this issue happens to user's cases, but if I don't have a failing example at hand, it is very challenging for me to fix the problem.