I firstly ran the OpenFOAM CFD simulation solely for 3 second of flow time to get a stable solution by removing the libpreciceAdapterFunctionObject.so from the system/controlDict.
Then, I took this latest time step output as my initial input for the FSI case and I ran the FSI simulation.
From the figure it can be seen that the error occurred at the 2nd iteration in the 1st coupling step.
My question is that whether this issue originated from OF side? I have checked all units in the OF and no mistakes are found. Or, is this a potential issue during the preCICE coupling stage.
p.s. I used turbulence model in the OF side for the force predictions.
it looks like there is an issue with reading checkpoints (in the error trace I see the function readCheckpoint()). This seems to be an issue in the OpenFOAM adapter that we should fix, please open an issue describing your turbulence model settings.
In the meantime, you could try using explicit coupling (which will probably not be stable enough, at least not with large time step sizes).
I have a new question, in my opinion, the precise only need force and displacement for data interpolations, doesn’t it?
The force is calculated by OpenFOAM where the momentum equations are solved, even if the turbulence model is turned on (e.g. k-omega SST is used), only the precision of the force will be affected but it has nothing to do data mapping, right?
(please open a new thread for each new larger question, but fine here! )
The OpenFOAM adapter cannot (or does not at the moment) directly access everything that is available inside OpenFOAM, mainly due to the function object approach (which offers several advantages). For this reason, we compute the force again. There are discussions for delegating such computations to OpenFOAM or to boundary conditions, but this would be a large redesign that we cannot prioritize at the moment. Additionally, it is not completely clear how it would affect compatibility with the different OpenFOAM versions.
)