Dear preCICE Community,
We have a fresh new release, after a sleepless week and some final tweaks during the FOSDEM conference. 🎉
Breaking news: we have breaking changes 😉. We decided to move to v2.0.0 to clean up some old baggage. You will need to change a few things in your applications to move to v2.x, but it’s worth it, many things will get much simpler. And promised: we will no do this too often. We have a rough schedule of every 2 years in mind.
Good friends help you moving: we prepared a porting guide. Also, during the preCICE workshop in two weeks, we will give an introduction to preCICE v2.0, which will be recorded and available online afterwards.
The most important changes:
- You can now (finally) use the same preCICE configuration file for serial and parallel runs.
- The extensive configuration reference can now also be generated in markdown. A recent version is always in the wiki.
- We cleaned up the duplicated meaning of “timestep”. preCICE now uses “time windows” and the participants do their “timesteps”.
- Mesh handling is much faster. 🚀
- We moved the Python and (new) Matlab bindings as well as the Fortran Module (formerly known as f2003 bindings) to separate repositories. Btw, the Python bindings are now really pythonic.
- For the first time, two-level initialization is available, allowing for fast initialization of very large cases 🚀🚀. The feature is, however, still in beta testing and switched off by default. We will have a presentation at the workshop (and afterwards online) about the new initialization concept.
- We restructured the repository a bit: developer tools are now in
tools, user tools inextras, native bindings inextras/bindings, and solver dummies inexamples. These examples are now also shipped with our binary packages, and you can use them to test your installation.
Have a look at the changelog for more details.
A big "thank you" to everybody who contributed in code, issues, documentation, testing, and every other way.
See you in a week,
The preCICE team