Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Provide lift and drag as global data #286

Open
uekerman opened this issue Mar 22, 2023 · 3 comments
Open

Provide lift and drag as global data #286

uekerman opened this issue Mar 22, 2023 · 3 comments
Labels
enhancement Nice to have, but not a problem

Comments

@uekerman
Copy link
Member

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:

  • Simply as a useful testcase for the global data feature
  • As a building block for a benchmark, @LeonardWilleke could use to test the new FMI Runner coupling OpenFOAM to an FMU PID controller

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?

@uekerman uekerman added the enhancement Nice to have, but not a problem label Mar 22, 2023
@davidscn
Copy link
Member

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.

@uekerman
Copy link
Member Author

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.

@davidscn
Copy link
Member

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Nice to have, but not a problem
Projects
None yet
Development

No branches or pull requests

2 participants