You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Probably straight-forward to implement. I would add a new locationsType ('meshless`) and then accumulate the data we have in the data fields. Wouldn't it even be possible to use a python or summation action with out current approach/ by just adding the additional interface? Would make things more complicated to configure, though.
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.
Regarding the benchmark case you mentioned: Note that there are no adapter modifications required for the force calculation right now. If the receiving side operates only on a single vertex in space, the 'integration' happens through a conservative mapping constraint.
We are currently extending preCICE towards handling of global data, so data not associated to meshes: precice/precice#202 @kanishkbh
A potential application could be to write lift and drag integrated over a boundary patch to preCICE.
Two motivations:
As long as global data in preCICE is not ready, we could write the data instead to a dummy (0,0,0) vertex and then later change to the new feature.
How complicated does this sound?
The text was updated successfully, but these errors were encountered: