Benjamin Uekermann
Benjamin Uekermann
As discussed in #474. TODO: * [ ] Add patch names to configuration * [ ] Integration test * [ ] Test with OpenFOAM adapter
There is no use case anymore, especially after #1222 https://github.com/precice/precice/blob/67b0e6d9c9629b69d923cc540056bfd63a258a56/src/mapping/config/MappingConfiguration.hpp#L47-L51 See also #859
... and also the associated mapping timing. There is currently no use case for these functions.
Currently, we get a problem if we use "first-participant" as timestepping method and, at the same time, initialize any data. Sadly, we cannot fix this in a non-breaking way. Most...
A consistent data mapping can be made "conservative" by a scaling sweep on the output mesh after the mapping. Please see [Bernhard's thesis](https://www5.in.tum.de/pub/Gatzhammer2014_preCICE.pdf), section 4.2.3. Such an option might be...
We regularly face the issues that users have problems with understanding the mapping configuration and how well the mapping works, in particular for RBF data mapping. On the other hand,...
There are still a few details that need to be sorted out before we can enable two-level intitialization by default. * [x] `ReceivedPartition::createOwnerInformation` still applies a gather-scatter approach and is...
For several applications users asked about sending global data, meaning data that is not associated to a mesh. Examples: * Angles between coordinate systems (CAMRAD-CFD) * Global background pressure (fluid-acoustic...
Open TODOs: - [ ] Change geometry to include step - [ ] Get proper cell coordinates (currently first-order average) - [ ] Allow arbitrary polynomial degree (currently hacked to...
Leftover from #279 Needs major clean-up and porting to preCICE v3. Originally contributed by @KyleDavisSA