David Schneider

To sum this up: I cannot reproduce the original issue here with a partitioned-heat example and I still think that you cannot simply use `fixedValue` (not even an inlet) and...

@MakisH what I observed for the CHT cases now (considering the fixes) looks as follows:  I only observe this for intermediate time steps, not for the final time step....

After some further investigations I'm a bit stuck here. Trying to visualize the results with paraFoam or vtk exports results always in a small 'gap' between the participants. Grouping the...

> I also noticed that the previous coupling of ATHLET-OpenFOAM (by GRS) used modified boundary conditions based on inletOutlet (for the temperature), normalInletOutletVelocity (velocity), fixedMean (velocity), fixedValue/buoyantPressure (pressure). See presentation...

> Only between ATHLET and OpenFOAM, using an in-house system, not preCICE. Reproducing something similar with preCICE is the project I am working on. Ah ok, but all Fluid-Fluid OpenFoam...

 Generated with `paraFoam` by loading the temperature field exclusively.

> In the contributing guidelines of preCICE we have already chosen the snake-case format. This would also be consistent with our precice-config.xml. Sounds good :+1:

That's indeed something I did not yet consider. I'm a bit afraid that a warning is not enough as OpenFOAM has a very verbose output and also preCICE (potentially also...

> follow with all solvers the standard way, where you have an independent directory for every solver. We will replace fenics and nutils with fenics-dirichlet, fenics-neumann, nutils-dirichlet, nutils-neumann. This would...

> What is not clear to me is where to store shared files (e.g. solver files). The distinction into openfoam-solver and openfoam- goes already in a good direction, but I...