Dear preCICE Community,
We prepared a fresh, new release: preCICE v1.6.0.
We worked on many different things in the last three months. The highlights, we summarize for you in this mail. For the complete picture, have a look at the changelog.
- We took significant steps in complying with xSDK, see the xSDK Community Policy Compatibility for preCICE. In terms of usability and visibility, this step would bring preCICE on the same level as the most important software projects in scientific computing. Membership of preCICE is currently under review.
- We introduced better logging during initialization and more safeguards against wrong user or adapter input.
- The connection publishing mechanism now follows a hash-based approach. The new approach is faster, more robust and NFS-friendly. An important change is that the connection files are now rooted in a folder named
precice-run
. If your simulation crashed please look for and remove this folder. - We reduced the memory consumption and significantly improved the performance of the mesh handling during initialization. For large cases, you will feel the difference.
- The nearest-projection mapping is now finally fast (no quadratic complexity anymore) and correct.
- Finally, we redesigned the Python bindings (
src/precice/bindings/python_future
, packageprecice_future
). The previous Python bindings (src/precice/bindings/python
, packageprecice
) are now deprecated and will be removed in preCICE v2.0.0. If you still want to use the old bindings, please installprecice
andprecice_future
. Our recommendation, if you want to use the new bindings: Useimport precice_future as precice
.
A big "thank you" to everybody that contributed in code, issues, documentation, testing, and every other way.
Happy Coupling,
The preCICE team
PS: Let us remind you on our first preCICE Workshop, February 17-18, 2020 in Garching (Munich). Registration will open soon.