Document running participants in different systems

[MakisH]

@LouieVoit published a very interesting paper, using preCICE to couple a CFD solver running on a laptop ("while waiting at the airport and connected to a poor wi-fi") to a massively-parallel MD simulation running on a cluster.

The paper is helpful to demonstrate the concept, but lacks some technical details. I got these from Louis via e-mail and I am summarizing them in this documentation addition at the bottom of the communication configuration page.

Note that this is not the first user that has asked for something like this. In the context of the helicopter simulations Master's thesis I supervised, we had a very similar issue, where each code was licensed for a different system.

• @LouieVoit Have I forgotten any details?
• @fsimonis Does this make sense, especially regarding gather-scatter?
• @davidscn Do you maybe want to test this? Could be very easy for you, since you daily work on a cluster.

[fsimonis]

I think most of this information fits better in the Distributed Systems page.

Not so sure about where the licensing would fit though. Maybe this is a use-case that deserves far more attention and could even be a major selling point of preCICE.

A hint on using gather-scatter if you need to deal with a single port between solvers would be useful on the configuration page though.

[MakisH]

I think most of this information fits better in the Distributed Systems page.

A hint on using gather-scatter if you need to deal with a single port between solvers would be useful on the configuration page though.

Good point, I forgot we now have this. I can move it there, and duplicate the ports thingy here.

Not so sure about where the licensing would fit though. Maybe this is a use-case that deserves far more attention and could even be a major selling point of preCICE.

I deserves some attention, but the use-case is rather niche. I don't see any obvious solution, as we don't seem to mention such advantages anywhere.

What I can do, however, is create a page License, explaining what LGPL means, what licenses we follow for adapters, how everything else (e.g., the website) is licensed, and what other advantages our approach brings (e.g., this).

@uekerman what do you think?

[fsimonis]

I deserves some attention, but the use-case is rather niche. I don't see any obvious solution, as we don't seem to mention such advantages anywhere.

What I can do, however, is create a page License, explaining what LGPL means, what licenses we follow for adapters, how everything else (e.g., the website) is licensed, and what other advantages our approach brings (e.g., this).

To clarify: the feature I am talking about is the ability to couple commercial code whose licences are bound to machines or cannot be used/fetched outside the company network.

[MakisH]

I moved the section to the distributed systems page and left a note for the specific port in the communication. I will work on the license-related page in a separate PR.

To clarify: the feature I am talking about is the ability to couple commercial code whose licences are bound to machines or cannot be used/fetched outside the company network.

This is clear enough and also what I already wrote in the documentation. I will elaborate on these in the license page PR.

[LouieVoit]

@MakisH Looks good to me !

[MakisH]

I will work on the license-related page in a separate PR.

Done: #407.

[MakisH]

Rendering, to help with reviewing (@fsimonis @davidscn):