Skip to content

Commit c4ff67c

Browse files
committed
Remove experimental banner from direct mesh access
1 parent dd0b1d1 commit c4ff67c

1 file changed

Lines changed: 0 additions & 4 deletions

File tree

pages/docs/couple-your-code/couple-your-code-direct-access.md

Lines changed: 0 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -7,10 +7,6 @@ summary: "You can access received meshes and their data directly by using specif
77

88
<!-- TODO: needs update -->
99

10-
{% warning %}
11-
These API functions are work in progress, experimental, and are not yet released. The API might change during the ongoing development process. Use with care.
12-
{% endwarning %}
13-
1410
This concept is required if you want to access received meshes directly. It might be relevant in case you don't want to use the mapping schemes in preCICE, but rather want to use your own solver for data mapping. As opposed to the usual preCICE mapping, only a single mesh (from the other participant) is now involved in this situation since an 'own' mesh defined by the participant itself is not required any more. In order to re-partition the received mesh, the participant needs to define the mesh region it wants read data from and write data to. The complete concept on the receiving participant looks as follows:
1511

1612
```cpp

0 commit comments

Comments
 (0)