Benjamin Uekermann

> The current workaround is to use either pseudo meshes or multiple meshes to communicate the data via preCICE, which is both tedious and inefficient. Isn't the current workaround to...

> https://github.com/precice/precice/issues/202: user-defined data allows exchanging data of any shape using a single vertex as global data, which can be more user-friendly than having to handle multiple data and vertices....

Mmh, I get your point to some extent, but not where we should head yet. I would still favor simply adding support for rank-2 tensors as described [above](https://github.com/precice/precice/issues/2085#issuecomment-2397552739).

Ideally using the Fortran module, for a better test coverage.

Could be a good fit to do this when moving to the preCICE adapter schema. @IshaanDesai IIRC you looked into a schema for the non-preCICE part of the micro manager...

IMO, there is no harm in providing it somewhere if you have a draft already. The earlier we find problems with the preCICE adapter schema, the better.

I like the suggestion of @fsimonis, sounds like "low effort some gain" to me. Keep in mind that through the course the Python bindings are often the first place where...

There is already https://github.com/precice/precice/tree/develop/extras/livegraph

> Regarding the FMI cases some input from @uekerman would be appreciated since I'm not that much into the topic. Only requiring `fmiprecice` should do the job, no? Everything else...

I agree on a)-d). > How and do we consider this breaking? My tendency is to consider this non-breaking or non-hurting at least. We change the functionality in two ways:...