deal.II Newsletter #266

[Rene Gassmoeller]

Hello everyone!

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

#15960: Update shasum for clang-format mac. (proposed by luca-heltai)
#15959: MatrixFree: do not update ghost values of a ghosted src vector (proposed by peterrum)
#15958: Simplify some GridTools functions. (proposed by drwells; merged)
#15956: Unify headers of tutorials (proposed by peterrum; merged)
#15955: fix check_compiler_setup failed build issue mentioned in #1921 (proposed by RoadToDream)
#15954: Another attempt to fix compile warning (proposed by kronbichler)
#15953: Add an assertion to IndexSet::compress(). (proposed by bangerth; merged)
#15952: Added another test for limit_p_level_difference(). (proposed by marcfehling)
#15951: Matrix-free evaluation of Raviart-Thomas: major restructuring (proposed by kronbichler)
#15950: FEEvaluation for Raviart-Thomas: use fewer multiplications (proposed by kronbichler; merged)
#15949: Also run check for symmetry for fe_degree = 0 (proposed by kronbichler; merged)
#15948: Add matrix-free interpolation test for Raviart-Thomas case (proposed by kronbichler; merged)
#15947: Added one assertion to setup_line_to_cell. (proposed by marcfehling; merged)
#15945: Add code to serialize PETSc vectors. (proposed by drwells)
#15943: Make the p::s::T serialization test use zorder. (proposed by drwells; merged)
#15932: Add Functions::RayleighKotheVortex (proposed by peterrum; merged)
#15865: reset ghost state in MG_transfer_global_coarsening interpolate (proposed by richardschu; merged)

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

#15957 Tracking deal.ii in downstream package repositories (opened)
#15946 CMake: use pkgconfig information when available (opened)

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.