deal.II Newsletter #336

[Rene Gassmoeller]

Hello everyone!

This is deal.II newsletter #336.
It automatically reports recently merged features and discussions about the deal.II finite element library.

Below you find a list of recently proposed or merged features:

#19011: Add vectorized approximation of exp(x) (proposed by j-brotz)
#19009: Add get_cell_iterator to P::MF (proposed by mwichro)
#19008: Allow users to edit the team_size of the Kokkos TeamPolicy objects inside Portable::MatrixFree (proposed by RyanMoulday)
#19007: tests: use angle brackets for includes (proposed by tjhei; merged)
#19006: Portable MatrixFree: cleanup test (proposed by tjhei; merged)
#19005: Portable MatrixFree: support MPI cell loop with >1 DoFHandler (proposed by tjhei)
#19004: portable MatrixFree: avoid unnecessary deep_copy() fences (proposed by tjhei; merged)
#19003: Test parsing trailing separator characters for parsed function (proposed by gassmoeller)
#19002: Rename the ROL interface class. (proposed by marcfehling)
#19001: fix Portable::MatrixFree initilization on mg level (proposed by mwichro)
#19000: Add get_dof_handler_fine() to MGTwoLevelTransferBase. (proposed by RyanMoulday)
#18999: Allow MatrixFree.initialize_dof_vector() to apply partitioner to device vectors. (proposed by RyanMoulday; merged)
#18997: CMake: make git query for revision.h work with git worktree (proposed by tjhei; merged)
#18993: Fix tria move missing member (proposed by a-reinhold; merged)
#18947: portable matrix-free: support N DoFHandler (proposed by tjhei; merged)

And this is a list of recently opened or closed discussions:

#19010 Compilation fails on Ubuntu 24.04 when PETSc is enabled: ambiguous overload for 'operator!=' in tria_accessor.h (opened)
#18998 step-3 tutorial explanation (opened)
#18992 BUG: Triangulation not properly movable (closed)
#18964 Compiling error related to boost/serialization/utility.hpp (closed)

A list of all major changes since the last release can be found at this website.

Thanks for being part of the community!

Let us know about questions, problems, bugs or just share your experience by writing to this mailing list, or by opening issues or pull requests on Github.
Additional information can be found at our official website.