deal.II Newsletter #232

[Rene Gassmoeller]

Hello everyone!

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

#14391: Correctly handle unpacking empty objects (proposed by gassmoeller)
#14389: Document a restriction on ConsensusAlgorithms::serial(). (proposed by bangerth; merged)
#14388: Add to the documentation of the ConsensusAlgorithms functions. (proposed by bangerth)
#14387: FEEvaluation: precompile for n_q_points==2*fe_degree (proposed by peterrum)
#14386: MatrixFreeOperators::LaplaceOperator vectorization width 1 (proposed by sebproell; merged)
#14385: Fast hanging-node algorithm for FE_Q_iso_Q1 (proposed by peterrum; merged)
#14384: Add performance test showing compressible Navier-Stokes equations (proposed by kronbichler)
#14383: ShapeInfo: Implement evaluation of derivatives on faces (proposed by kronbichler; merged)
#14381: Make the error message for non-integer IDs in UNV files clearer. (proposed by drwells; merged)
#14380: Allow FEImmersedSurfaceValues to take a MappingFEField (proposed by fdrmrc; merged)
#14378: Fix some warnings. (proposed by marcfehling; merged)
#14376: fe_index: added changelog. (proposed by marcfehling; merged)
#14371: Generalize precompilation of TensorProductMatrixSymmetricSum (proposed by peterrum; merged)
#14366: TensorProductMatrix: with arbitrary number of lanes (proposed by peterrum; merged)
#14356: Report error and abort in CollectiveMutex during stack unwinding (proposed by gassmoeller; merged)

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

#14390 A tutorial on an eigensolver for linear elasticity (opened)
#14382 Does dealii support 1D problem. (opened and closed)
#14379 grid_in unv file error (opened and 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.