I read that you do surface coupling?
Do you support volume coupling too?
Makis
October 8, 2019, 12:17pm
2
Yes, but it will be computationally expensive. preCICE is mainly designed to couple simulations that share a common surface boundary. In this case, all the coupled volume nodes should be specified in the coupling mesh.
preCICE only knows about points and their connectivity, so it doesn’t make much of a difference if the points are on a surface or on a volume. However, in the case of volume coupling, nearest-projection mapping would not be available. You may still use the nearest-neighbor or RBF mapping, however.
Moved from our FAQ on precice.org .
Makis
October 13, 2019, 7:35pm
3
For the OpenFOAM adapter, there is an open Pull Request for supporting volume coupling: https://github.com/precice/openfoam-adapter/pull/97
Feedback or further work on this would be very welcome.
We have volume coupling on the radar and are currently gathering plans, ideas, information and work packages in the GitHub issue 468 .
Feel free to participate in shaping this feature!
Makis
July 3, 2020, 3:04pm
5
There have also been talks about volume coupling at the preCICE Workshop 2020:
We have news!
We are actively working on a new linear cell interpolation mapping.
For 2D cases, you will be able to define a triangular mesh and configure preCICE to interpolate inside the cells
For 3D cases, we plan to add support for tetrahedral elements to both the API and the above mapping.
2 Likes
More updates on volume coupling:
We recently finished developing a partition-of-unity RBF data mapping. This should be a game changer for volume coupling.
precice:develop
← davidscn:pou-mapping
opened 01:38PM - 18 Nov 22 UTC
## Main changes of this PR
Adds the partition of unity RBF mapping as a new m… apping variant.
## Motivation and additional information
There are a few details yet to be clarified and a few TODOs in the code, but I'm sure these changes are ready for a first review. We need to fix a user interface in the configuration file.
Post TODO: Adjust the auto-selection of our mapping-config.
Closes #1273.
## Author's checklist
* [x] I used the [`pre-commit` hook](https://precice.org/dev-docs-dev-tooling.html#setting-up-pre-commit) to prevent dirty commits and used `pre-commit run --all` to format old commits.
* [x] I added a changelog file with `make changelog` if there are user-observable changes since the last release.
* [x] I added a test to cover the proposed changes in our test suite.
* [x] I sticked to C++17 features.
* [x] I sticked to CMake version 3.16.3.
* [x] I squashed / am about to squash all commits that should be seen as one.
* [x] Fixing a proper user-interface (related to #1417)
## Reviewers' checklist
* [x] Does the changelog entry make sense? Is it formatted correctly?
* [ ] Do you understand the code changes?
Rethinking and properly evaluating our communication backends for volume coupling is also on our roadmap.
fsimonis:
We are actively working on a new linear cell interpolation mapping.
For 2D cases, you will be able to define a triangular mesh and configure preCICE to interpolate inside the cells
For 3D cases, we plan to add support for tetrahedral elements to both the API and the above mapping.
Short update: The linear cell interpolation mapping was released with preCICE version 2.5.0 .