Benjamin Uekermann

So sth like this ```yml participant-name: Solid interfaces: - nodes-mesh: Solid-Mesh patch: surface read-data: [Force] write-data: [Displacement] precice-config-file: ../precice-config.xml ``` Let's do this when releasing preCICE v3 as it breaks...

The SU2 adapter overwrites some of the main files of SU2. This means that we have to do a new adapter for every new SU2 version currently (there are long...

The number of coupling iterations is an ill-conditioned observable and therefore sometimes system dependent. We went through the same pain with an integration test in preCICE. I recommend to not...

Good points! > merge both solver in a single executable instead of two. Do not merge the codes itself, but rather bundle the codes together. In the long run, a...

Not sure if this is of any help, but for the OpenFOAM-Nutils cases the time sync in vtks work. https://github.com/precice/tutorials/tree/master/CHT/flow-over-plate/buoyantPimpleFoam-nutils Maybe we could borrow some ideas from there?

I see the points. I really meant it for very short codes, such as https://github.com/precice/tutorials/blob/master/flow-over-heated-plate/solid-nutils/solid.py Here, a class hierarchy or if-else code blocks would make things more complicated and less...

In principle, yes, but the even better solution would be the move the documentations into a folder `docs` and render it on the website. Similar, to how we treat e.g....

There is also https://github.com/precice/precice/issues/311

You could use the [MBDyn tutorial](https://github.com/precice/mbdyn-adapter/tree/master/tutorials/cavityFSI) as a coupling partner.

Files to remove (they are part of preCICE, not the adapter, if they need to be in the same folder as the adapter due to the way Fluent links things...