We so far avoid calling participants and data generic names, but try to relate to a specific physical domain and application use case. This is currently only partially described in the naming conventions.

Of course, this is fine for now (and fine for an integration test), but before merging, we should better have more descriptive names.

They both represent the same mesh and don't model any physical behaviour.

Not sure what we would name them.

There is a physical motivation for this scenario. We could borrow names there?

The pyhsical motivation is to couple a hydrogeological and geomechanical model and let them iterate until they agree on effective stress.
Without the iterative scheme, there is no correction and the geomechanical model doesn't have a function.

So, I cannot see obvious names that we can use here.

But then we need to better express the motivation in the description and say that the modeling is (extremely) simplified, as is the case in general in our tutorials.

With the current formulation, it is a great integration test, but it looks a bit odd as a tutorial.

I added the motivation and more details about the solver.

Could we give a more descriptive name?
Not necessary, but If a user were to install this outside the venv, a growing binary lying around would be quite strange.

One direction could be growing-mesh-solver-python.

Do we need the title case (with PreCICE) here? 😬

The original was a bit difficult for me to read, maybe this is better:

"A and B" are mentioned below, but not introduced. Compromise:

A post-processing section would be nice, hinting to what the user should see in the end. Note that there is no other figure (besides the config visualization) in this tutorial. Someone that does not yet know what "growing mesh" means would need to read and imagine a bit first, before being able to get a first overview.

An image with the mesh in two different times (potentially with partitions shown) would be helpful.

Does this case even produce any results to show how the mesh grows?

I fixed the formatting of these strings (here and in line 58). Cross-check.

Interestingly, while the solver messages show up in the correct order when running with two ranks, they show up separately at the end when running serially:

--[precice] time-window 11 (max: 12), t 10, Dt 1, max-dt 1
---[precice] Time window completed
---[precice] Mapping "Data-B" for t=11 from "B-Mesh" to "A-Mesh"
---[precice] time-window 12 (max: 12), t 11, Dt 1, max-dt 1
---[precice] Reinitializing Participant
---[precice] Close distributed communication channels
---[precice] Setting up primary communication to coupling partner/s
---[precice] Primary ranks are connected
---[precice] Setting up preliminary secondary communication to coupling partner/s
---[precice] Prepare partition for mesh A-Mesh
---[precice] Gather mesh A-Mesh
---[precice] Send global mesh A-Mesh
---[precice] Receive global mesh B-Mesh
---[precice] Setting up secondary communication to coupling partner/s
---[precice] Secondary ranks are connected
---[precice] Time window completed
---[precice] Computing "nearest-neighbor" mapping from mesh "B-Mesh" to mesh "A-Mesh" in "read" direction.
---[precice] Mapping distance min:0 max:0 avg: 0 var: 0 cnt: 2621440
---[precice] Mapping "Data-B" for t=12 from "B-Mesh" to "A-Mesh"
---[precice] Reached end at: final time-window: 12, final time: 12
---[precice] Implicitly finalizing in destructor
---[precice] Close communication channels
Rank 0/1 has partition (0, 0)/(1, 1)
Each of 1 partitions has node size 512x512 = 262144 for a total of 262144 nodes on the base
A: data: 0.0 * 524288
A: data: 1.0 * 524288
A: data: 2.0 * 524288
A: Event grows local mesh from 524288 to 1048576 and global mesh from 524288 to 1048576
A: data: 3.0 * 1048576
A: data: 4.0 * 1048576
A: data: 5.0 * 1048576
A: Event grows local mesh from 1048576 to 1572864 and global mesh from 1048576 to 1572864
A: data: 6.0 * 1572864
A: data: 7.0 * 1572864
A: data: 8.0 * 1572864
A: Event grows local mesh from 1572864 to 2097152 and global mesh from 1572864 to 2097152
A: data: 9.0 * 2097152
A: data: 10.0 * 2097152
A: data: 11.0 * 2097152
A: Event grows local mesh from 2097152 to 2621440 and global mesh from 2097152 to 2621440