co-simulation

Describe your setup

Current preCICE develop version

Describe the problem

When we allowed multiple read mappings to the same mesh in #849, we forgot to update the following assignment (which still assumes that there is only one read mapping to a certain mesh).

https://github.com/precice/precice/blob/ebce55ab5c563295909b0179f6610b6e4d4fa529/src/precice/config/ParticipantConfigur

preCICE v2.3.0 precice/precice#1080 introduces an API method to ask whether mesh connectivity is required. In the OpenFOAM adapter, we currently ask the user whether this is required, which the user should not need to configure, as it is system-internal information: https://precice.org/adapter-openfoam-config.html#nearest-projection-mapping

We could directly ask preCICE

Docker Hub Autobuilds is going away for the free tier - https://www.docker.com/blog/changes-to-docker-hub-autobuilds/

I think we have some builds running there, so we'll either need to try to join the Open Source program they have, or build the images elsewhere and push them to Docker Hub.

Currently PADE mix behaviours and protocols in a same file located in /pade/behaviours/protocols.py.

The idea is split behaviours and protocols in different files.

Once #61 is merged, serialization of the state functions should be tested using FMPy.

Maybe other stuff like the XML could be checked too.

Describe the bug
The pi-exchange examples for different languages have differences in implementation that make some of them behave differently.

What is the expected behavior?
The pi-exchange federates written in different languages should be drop in replacements for each other when running examples. A pisender written in Python should work with a pireceiver written in C.

The HELICS helper SetupFederate function currently creates a new federate each time it gets called. There should be a check to see if it has already been initialized before creating a new federate.