Benjamin Uekermann
Benjamin Uekermann
> Ah yes. There was actually nothing new in GlobalCouplingData, so I've removed it altogether. Now CouplingData class is being used for both mesh and global data (like DataContext). Sounds...
> Tests for Multi Coupling schemes Multi coupling is not yet supported in this PR, see #1716
Good point. Alternatively, if we want to keep things simple here and extend later, we could restrict the feature to scalar first. ```xml ``` In principle, ```xml ``` sounds good,...
> Why the too much additional work (compared to vector2d, vector3d)? I would assume that this is the simpler solution. Just had a look again: It should actually be easier...
But then who decides which timestamps to use in the results data field?
> On the other hand, there are only a limited number of mapping methods, for which this indirect access makes sense: namely PUM, nearest neighbor and nearest projection, where connectivity...
Good point. Yes, I think currently, we only raise an error when an empty provided mesh is communicated. If it is not communicated, then no error is thrown. We should...
IIRC installing mkl should held to some extend. Then, Nutils picks a different solver backend. Note that the `fluid-nutils` case uses different numerics than the other fluid cases. We solve...
There is already https://github.com/precice/tutorials/pull/429 which touches the case quite a bit.
Thought about this one too, but we don't yet have the necessary functionality in preCICE (using a global data in an action). Probably more complicated.