Benjamin Uekermann
Benjamin Uekermann
Exactly, and that would also solve the problem that our configuration is hard to understand (which meshes should I send, over which mesh do I exchange data etc.).
@BenjaminRodenberg Did we maybe solve this on-the-fly already?
> We could solve this by exposing BaseCouplingScheme::sendsInitializedData(). @uekerman what do you think? Does this make sense? Yes, I think this would be the right way to go. > I...
> ERROR: Send using sockets failed with system error: write: Broken pipe means typically that the "other side" crashed. What behavior do you get there?
@fsimonis Did you apply the patch from the [mingw installation](https://github.com/precice/precice/wiki/mingw-(Windows-version))? If I recall correctly, we also had problems with `prettyprint.hpp` there.
I agree that this feature would be very helpful. One should always have the current alternative in mind: Simply defining multiple meshes (let's call this variant **Old**): ``` setMeshVertices.(meshIDTop, sizeTop,...
> * How do we handle repeated Vertex/Edge definitions in the Mesh? It is not forbidden to define multiple vertices with the same coordinates. We treat them as multiple vertices...
I like the inheritance solution. The concrete API functions, we would probably need to tweak a bit more. > * How to handle vertices without patch ids in the mappings?...
True, could be easier than I originally thought.
In principle, a solution with a stand-alone action sounds interesting. The technical limitation though is that we do not know the value to scale with in the action. To compute...