You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
All important and notable changes in the _CoSimIO_ will be documented in this file.
4
+
5
+
## 2.0.0
6
+
- Changes in Connecting:
7
+
- Now instead of specifying `connection_name` directly, `my_name` and `connect_to` are used for the call to `Connect`.
8
+
- The `CoSimIO::Info` that is returned from `Connect` now contains the `connection_name` that needs to be used in subsequent calls to _CoSimIO_.
9
+
- This change was done to make the connection more robust and to make the selection of primary/secondary partner clear. This is only used internally e.g. for who opens a port and who connects to it.
10
+
- Introduced `CoSimIO::ModelPart` for exchanging of meshes
11
+
- Simplified version of [`Kratos::ModelPart`](https://github.com/KratosMultiphysics/Kratos/blob/master/kratos/includes/model_part.h)
12
+
- Simplifies and unifies the usage of `Import-/ExportMesh`
13
+
- See the tutorials on how to use it:
14
+
-[C++](tutorial/cpp/model_part.md)
15
+
-[C](tutorial/c/model_part.md)
16
+
-[Python](tutorial/python/model_part.md)
17
+
- FileCommunication:
18
+
- By default now done in folder. This way leftovers from previous simulations can be easily deleted (done automatically).
19
+
- working directory can be specified
20
+
- stability of initial connection was significantly improved.
21
+
- Python interface: Data is no longer copied when going from Python to C++ and vice versa.
22
+
-`Import-/ExportData` now uses `CoSimIO::DoubleVector` (small wrapper around `std::wrapper`)
23
+
-`Import-/ExportMesh` now uses `CoSimIO::ModelPart`
The argument `model_part` is a container for mesh, it contains nodes and elements. Check the [implementation](../../co_sim_io/c/co_sim_io_c_model_part.h) and the [tests](../../tests/co_sim_io/c/model_part/test_model_part.c) for details of `CoSimIO::ModelPart`.
<!-- For connecting to Kratos it is very important to have in mind that Kratos also uses *CoSimIO* for interprocess communication so its python interface reflects the CoSimIO. So we may create a python script for connecting and disconnecting in the same way described in the [python tutorial](https://github.com/KratosMultiphysics/CoSimIO/blob/master/tutorial/python/README.md):
249
+
For connecting to Kratos it is very important to have in mind that Kratos also uses *CoSimIO* for interprocess communication so its python interface reflects the CoSimIO. So we may create a python script for connecting and disconnecting in the same way described in the [python tutorial](https://github.com/KratosMultiphysics/CoSimIO/blob/master/tutorial/python/README.md):
275
250
276
251
```Python
277
252
from KratosMultiphysics.CoSimulationApplication import CoSimIO
@@ -297,11 +272,11 @@ Then you may run your executable with python script of Kratos from your working
<!-- Here we try to send some data to Kratos and get it back from it. Then we can check if both data are the same. Again the python file forKratos side is very similar to the one descirbedin the [python tutorial](https://github.com/KratosMultiphysics/CoSimIO/blob/master/tutorial/python/README.md):
279
+
Here we try to send some data to Kratos and get it back from it. Then we can check if both data are the same. Again the python file for Kratos side is very similar to the one descirbed in the [python tutorial](https://github.com/KratosMultiphysics/CoSimIO/blob/master/tutorial/python/README.md):
<!-- This tutorial shows how to map data between (non matching) meshes with Kratos. It is based on tutorials 9 & 10.
487
+
This tutorial shows how to map data between (non matching) meshes with Kratos. It is based on tutorials 9 & 10.
513
488
514
489
In this tutorial we first send two meshes based on the same geometry but with different discretizations to Kratos. Those meshes are used as basis for the mapping. In Kratos teminology those are the origin and the destination.
For more information check the [implementation](../../co_sim_io/c/co_sim_io_c_model_part.h) and the [tests](../../tests/co_sim_io/c/model_part/test_model_part.c).
0 commit comments