Dear preCICE community,

We are happy to announce a new preCICE release v3.4.0.

This release adds configurable awareness of physical bounds to quasi-Newton acceleration. The consistent partition-of-unity mappings now feature a batched solver based on Kokkos and Kokkos-Kernels with support for OpenMP, CUDA, HIP, and SYCL executors. The axial geometric multiscale mapping now also supports 1D-2D and 2D-3D mappings, and added support for uniform field distributions when mapping 1D-3D.

Some further additions are the consistently named Fortran API for setting mesh connectivities precicef_set_mesh_X_, and some performance improvement in the mapping of vectorial data using linear-cell-interpolation and nearest-projection, as well as latency-avoiding measures when reading the configuration file from the filesystem.

Noteworthy bug fixes include a crashing bug in the IQN QR1 filter introduced in version 3.2.0, as well as a difficult-to-trigger race condition in the two-level initialization introduced in the initial release of the feature.

The version is compatible and tested with Boost 1.91.0 beta, libxml2 2.14, and Eigen 5.0.1.

For the highlights, read the upcoming blog post.
For all details, check the full list of changes in the changelog.

Happy coupling!

Dear preCICE community,

We are happy to announce a new bugfix preCICE release v3.3.1.

This is especially relevant for users of the Kokkos RBF mappings, users of user-defined profiling sections, and users on Windows.

We fixed a Boost detection issue that was introduced with their new CMake config files, and a range of compilation issues on Windows with MSVC.
This hotfix also adds support for the new Kokkos 5, which required internal compatibility with C++20.
Furthermore, nesting user-defined profiling sections with startProfilingSection("Name") now result in correct output files. While this didn't lead to a crash in preCICE, it crashed the profiling merge script.
Finally, we fixed a rare underflow in a log statement.

For all details, check the full list of changes in the changelog.

Special thanks go to all users who contributed to this hotfix with detailed issues, and PRs!

Happy coupling!

Dear preCICE community,

We are happy to announce a new preCICE release v3.3.0.

This release adds support for Quads in 2D for linear-cell-interpolation, simplifies running preCICE in parallel without MPI, and clarifies the output of the coupling state and error messages regarding unmet requirements, such as checkpointing.
The build-in profiling uses a significantly more space efficient output format and it's post-processing has been moved to a separate python package, accessible via the new precice-cli.

Noteworthy bug fixes include a bug in the IQN QR3 filter, which became the default in 3.2.0, and time desynchronization when using first-participant.

For users interested in Windows, we collaborated with the MSYS2 package maintainers to getting preCICE actively tested on Windows and fixed some compatibility issues.

The version is compatible and tested with Boost 1.89.0, libxml2 2.14, and Eigen 5.0.0.
Note that for the compatibility with Eigen 5, we now use the generated CMake configuration files of Eigen, meaning a simple local clone of Eigen will not be detected anymore. To fix: create a build directory, run cmake, and pass this as -DEigen3_DIR= to the configuration of preCICE.

For the highlights, read the blog post.
For all details, check the full list of changes in the changelog.

Happy coupling!

Dear preCICE community,

We are happy to announce a new preCICE release v3.2.0.

This release features significant enhancements to time interpolation with all acceleration schemes now supporting substeps, implicit schemes exchanging substeps by default, reduced sample communication latency, and more efficient waveform sampling. Direct mesh access has been expanded to support multiple meshes per participant. Adapter developers can now integrate custom profiling sections into preCICE's profiling data through new API functions.

New experimental features include just-in-time mappings and runtime remeshing.

For the highlights, read the blog post.
For all details, check the full list of changes in the changelog.

Happy coupling!

Dear preCICE community,

We are happy to announce a new bugfix preCICE release v3.1.2.

This is only relevant for users coupling participants with implicit and explicit schemes simultaneously.

We fixed a bug which exchanged data of the first iteration with explicitly coupled participants instead of postponing the data exchange until the implicit scheme has successfully converged.
This fix may also impact runtime performance as the aforementioned explicitly coupled participants now need to wait longer. Therefore, their runtime may not overlap the way it did before.

For all details, check the full list of changes in the changelog.

Happy coupling!

Dear preCICE community,

We are happy to announce a new bugfix preCICE release v3.1.1.

We fixed a bug which results in a hang in initialize when using non-zero initial data with data mappings using collectives on a parallel participant along with at least one rank having an empty mesh. In practice, this happens when the solver domain decomposition results in a rank not handling a coupling interface, such as the parallel fluid participant in the flow-over-heated-plate tutorial.

We also added missing checks for unknown/typoed participant names in <exchange> and <m2n> tags.

TLDR please upgrade if you are on v3.x.x

For all details, check the full list of changes in the changelog.

Happy coupling!

Dear preCICE community,

We are happy to announce a new minor preCICE release v3.1.0, which is primarily an extended bugfix release.

Most notable change is the improved numerical accuracy of time handling in preCICE. This leads to cleaner return values of getMaxTimeStepSize() as well as cleaner timestamps in log files and exports. This change prevents internal crashes of long-running simulations. Reading data at the end of a time-window is now robust to numerical inaccuracies due to time.
preCICE now allows for more combinations of valid mapping direction and constraint, when dealing with participants running in Serial.

The dependency boost.filesystem has also been replaced with std::filesystem.

For all details, check the full list of changes in the changelog.

Happy coupling!

Dear preCICE community,

We are happy to announce a new preCICE release v3.0.0. This release is the first major release of version 3 and is not backwards compatible with releases of preCICE version 2.

This version is packed with new features and improvements, too many to be listed here.
We are working on an extensive porting guide and are completely overhauling the documentation to reflect changes in v3.
Releases of bindings, adapters, and tutorials will follow soon.

For the highlights, read the blog post.
For all details, check the full list of changes in the changelog.

Happy coupling!

Dear preCICE community,

We are happy to announce a new preCICE release v2.5.1 with some fixes we backported from the upcoming preCICE version 3.0.0.

Most notable change is the ability for IQN to start from a zero state. This used to result in an error message.

There will be no blog post for this release as version 3.0.0 is around the corner.
For all details, check the full list of changes in the changelog.

Happy coupling!

Dear preCICE community,

We are happy to announce a new preCICE release v2.5.0. This release will be the last version 2.x release and we are looking forward to release preCICE version 3.0.0 throughout the next year. For this reason, the current develop branch of preCICE itself might be incompatible with existing adapters in the near future.

We decided to release version 2.5.0 as it comes with several bug fixes and an experimental version of the linear cell interpolation data mapping, which can be used for volumetric coupling.

For the highlights, read the blog post: Iceberg ahead and new preCICE release v2.5.
For all details, check the full list of changes in the changelog.

Happy coupling!