deal.II Newsletter #332

16 views
Skip to first unread message

Rene Gassmoeller

unread,
Oct 8, 2025, 6:00:39 AM (6 days ago) Oct 8
to dea...@googlegroups.com

Hello everyone!

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

#18922: Add support for two level transfers using device vectors via MGTwoLevelTransferCopyToHost (proposed by RyanMoulday)
#18921: Increase safety of Timer class (proposed by gassmoeller; merged)
#18920: Simplify static assertions and condition checks (proposed by mwichro)
#18919: Throw when running into errors reading gmsh files. (proposed by bangerth; merged)
#18918: CMake: fix CMake error file location in error message (proposed by tjhei; merged)
#18917: Cleanup TensorProductMatrix with compile-time checks (proposed by mwichro; merged)
#18916: step-95: require p4est (proposed by tjhei; merged)
#18915: doxygen: update mathjax URL (proposed by tjhei; merged)
#18913: Documentation improvements im Timer class (proposed by gassmoeller; merged)
#18912: Do not return CPU time in Timer::stop() (proposed by gassmoeller; merged)
#18911: MPI implementation of MatrixScaling class (proposed by PolvereUnipi)
#18910: CellDataTransfer: clean up the calls to `compress()`. (proposed by drwells; merged)
#18909: Disallow TimerOutput output while running (proposed by gassmoeller; merged)
#18908: Minor clean-up of the partitioned mesh reader. (proposed by bangerth; merged)
#18907: Step-100: Solving the Time-Harmonic Helmholtz equation with the Discontinuous Petrov Galerkin (DPG) method (proposed by blaisb)
#18906: Improve the formatting of an error message. (proposed by bangerth; merged)
#18905: Add safety factor for eigenvalue estimation in preconditioners (proposed by mwichro; merged)
#18902: MGTransferMatrixFree::initialize_dof_vector no longer checks for compatible partitioners (proposed by michelebucelli; merged)
#18901: pre-commit autoupdate (proposed by marcfehling; merged)
#18898: Add a ugrid mesh reader to GridIn. (proposed by bangerth; merged)
#18897: Add a necessary include file. (proposed by bangerth; merged)
#18896: Move documentation within the GridIn class. (proposed by bangerth; merged)
#18895: Add assembly of MGTwoLevelTransfer operations as sparse matrices (proposed by marksidoro)
#18894: DataOut: remove captured `this` to avoid dangle after copy/move (proposed by dabele; merged)
#18893: Remove unnecessary include (proposed by gassmoeller; merged)
#18890: Minor doc updates in GridIn. (proposed by bangerth; merged)
#18888: Step-80 (proposed by luca-heltai)
#18884: LowStorageRungeKutta: fix size of a (proposed by peterrum; merged)
#18883: Move logic from setup() into initialize in all petsc preconditioners. (proposed by RyanMoulday; merged)
#18882: Fix a missing check in step-7. (proposed by bangerth; merged)
#18879: Simplify handling of timer overhead in TimerOutput (proposed by gassmoeller; merged)
#18874: Read partitioned msh with ids (proposed by luca-heltai; merged)
#18866: Simplify TimerOutput storage and fix documentation (proposed by gassmoeller; merged)

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

#18914 GridIn throws runtime error when reading high-order (quadratic) Gmsh mesh (opened and closed)
#18904 Regression tester regressed b21f38 (opened and closed)
#18903 Netcdf/CF/Ugrid output (opened)
#18900 Internal error in MGTwoLevelTransferBase::restrict_and_add for p-multigrid (opened)
#18899 step-95: The object pointed to is not valid anymore. (opened)
#18892 DataOut cannot be copied/moved/returned from a function (opened and closed)
#18891 Regression tester regressed a89304 (opened)
#18889 step-93 make_hanging_node_constraints with adaptive mesh refinement (opened)
#11352 Simplex/mixed mesh-support follow up tasks (closed)
#7005 add GridGenerator for matrix-inclusion (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.

Reply all
Reply to author
Forward
0 new messages