deal.II Newsletter #337

[Rene Gassmoeller]

Hello everyone!

This is deal.II newsletter #337.
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:

#19024: VTKWrappers utilities -- part II -- read_cell_data (proposed by luca-heltai)
#19023: VTKWrappers utilities -- part I -- read_vtk (proposed by luca-heltai)
#19022: Bump actions/checkout from 5 to 6 (proposed by dependabot[bot]; merged)
#19021: Get the type of a call to std::accumulate() right. (proposed by bangerth; merged)
#19020: PETSc: support multithreaded read of ghosted vector (proposed by tjhei; merged)
#19019: Implementation of grid uniform_channel_with_sphere (proposed by a412h)
#19017: Shorten documentation of ParsedFunction. (proposed by luca-heltai; merged)
#19016: write CF/UGRID output (proposed by dabele)
#19015: Added mask to ROL Wrapper. (proposed by marcfehling)
#19013: Pass constraints to the Chebyshev smoother in step64 (proposed by iprusak; merged)
#19012: Add parallel reduction to ROL Wrapper. (proposed by marcfehling)
#19008: Allow users to edit the team_size of the Kokkos TeamPolicy objects inside Portable::MatrixFree (proposed by RyanMoulday; merged)
#19005: Portable MatrixFree: support MPI cell loop with >1 DoFHandler (proposed by tjhei; merged)
#19003: Test parsing trailing separator characters for parsed function (proposed by gassmoeller; merged)

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

#19025 Regression tester regressed 2357df (opened)
#19018 Regression tester regressed 46b943 (opened)
#19014 Regression tester regressed cca3db (opened)
#19010 Compilation fails on Ubuntu 24.04 when PETSc is enabled: ambiguous overload for 'operator!=' in tria_accessor.h (closed)
#18886 PETSc and thread-safety (closed)
#18856 Eagerly construct PETSc preconditioners? (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.