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.

Sign up for GitHub

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

preCICE23: Add registration information #232

Merged
merged 3 commits into from
Dec 2, 2022
Merged

preCICE23: Add registration information #232

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
2bab1cf
preCICE23: Add registration information
MakisH Dec 2, 2022
25801c4
Fix CI in couple-your-code
MakisH Dec 2, 2022
b694d06
Add contact information
MakisH Dec 2, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Fix CI in couple-your-code
  • Loading branch information
@MakisH
MakisH authored Dec 2, 2022
commit 25801c4101da82e45cbd9a927d8be572754df63e
2 changes: 1 addition & 1 deletion pages/docs/couple-your-code/couple-your-code-porting-v2-3.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,7 @@ Please add breaking changes here when merged to the `develop` branch.
## preCICE API

- Migrate connectivity information to the vertex-only API. All `setMeshX` methods take vertex IDs as input and return nothing.
- Directly define face elements or cells of your coupling mesh available in your solver by passing their vectices to preCICE, which automatically handles edges of triangles etc. See [Mesh Connectivity](couple-your-code-defining-mesh-connectivity) for more information.
- Directly define face elements or cells of your coupling mesh available in your solver by passing their vectices to preCICE, which automatically handles edges of triangles etc. See [Mesh Connectivity](couple-your-code-defining-mesh-connectivity) for more information.
- Rename `setMeshTriangleWithEdges` to `setMeshTriangle` and `setMeshQuadWithEdges` to `setMeshQuad`. The edge-based implementation was removed.
- Use the new bulk functions to reduce sanitization overhead: `setMeshEdges`, `setMeshTriangles`, `setMeshQuads`, `setMeshTetrahedra`
- Remove `mapWriteDataFrom()` and `mapReadDataTo()`.
Expand Down