Channel transport with particles

[davidscn]

The open question is a bit how to handle the MercuryDPM participant, as the coupled code is entirely compiled with MerucryDPM

https://bitbucket.org/mercurydpm/mercurydpm/pull-requests/266

In principle, using

make ChannelTransport

and copying the executable compiled in ./build/./Drivers/PreCICE/ChannelTransport is sufficient. Afterwards simply execute the case.

Checklist:

• I added a summary of any user-facing changes (compared to the last release) in the changelog-entries/<PRnumber>.md.
• I will remember to squash-and-merge, providing a useful summary of the changes of this PR.

[MakisH]

The README.md file is currently missing.

We need to rethink how we are distributing solver codes that are built directly in the build tree of the respective solver. A good place to document this then would be the adapter software engineering page.

[uekerman]

The open question is a bit how to handle the MercuryDPM participant, as the coupled code is entirely compiled with MerucryDPM

We could add a run.sh that (also) does the copying (and maybe also the building?)
What would be the standard to find out where MercuryDPM is? Define MERCURYDPM_PATH?

Do we also need a cleaning script there?

[precice-bot]

This pull request has been mentioned on preCICE Forum on Discourse. There might be relevant details there:

https://precice.discourse.group/t/the-precice-newsletter-archive/2868/2

[cheng5243]

When will bidirectional coupling be achieved