deal.II Newsletter #251
Rene Gassmoeller
Hello everyone!
This is deal.II newsletter #251.
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:
#15151: Allow MappingInfo::reinit_cells() to work on containers (proposed by fdrmrc)
#15150: Add getter for cell_data in RPE (proposed by fdrmrc)
#15149: Introduce `MGTwoLevelTransferBase` (proposed by fdrmrc)
#15147: MatrixFree diagonal: Avoid repeated computations and binary search (proposed by kronbichler)
#15146: Document how we deal with errors in call-backs. (proposed by bangerth)
#15145: Various changes to bibliography. (proposed by marcfehling; merged)
#15144: Clarify the documentation of a reinit() function. (proposed by bangerth)
#15143: Update bibtex entries of preprints. (proposed by marcfehling; merged)
#15142: Convert step-57 references to bibtex, with proper cross-referencing. (proposed by bangerth; merged)
#15141: Add two level transfer operator between non-nested levels (proposed by fdrmrc)
#15140: Auto merge scalar components of `DataOut_DoFData` into vectors and tensors (proposed by vovannikov)
#15139: Add necessary include files to a code snippet in the glossary. (proposed by bangerth; merged)
#15138: Implement alternative rules what quadrature/mapping object to use in FEInterfaceValues::reinit(). (proposed by bangerth)
#15137: Vectorize NonMatching::MappingInfo (proposed by bergbauer)
#15136: Remove commented assert (proposed by peterrum; merged)
#15135: MatrixFree diagonal: Avoid quadratic complexity & memory allocations (proposed by kronbichler; merged)
#15134: Make it possible to document C++20 requirements (and do so). (proposed by bangerth)
#15133: Add changelog entry for SNES and TS (proposed by stefanozampini; merged)
#15132: Add 'requires' clauses to PETSc solvers. (proposed by bangerth)
#15131: More doxygen fixes. (proposed by bangerth; merged)
#15130: Added changelog for #14866. (proposed by marcfehling; merged)
#15129: A variety of doxygen fixes. (proposed by bangerth; merged)
#15128: In step-77, also talk about the other nonlinear solver packages we support. (proposed by bangerth)
#15127: Sort terms so that the bilinear form has ...phi_i * phi_j ... in step-57. (proposed by bangerth; merged)
#15126: PETScWrappers::TimeStepper fix backward compatibility to 3.7 (proposed by stefanozampini; merged)
#15125: Remove tabulated shape functions from MappingQ (proposed by kronbichler; merged)
#15124: Implement arbitrary order derivatives for tensor-product evaluators (proposed by kronbichler; merged)
#15122: ParameterAcceptor now uses a set. (proposed by luca-heltai; merged)
#15121: CMake: Test link interface again (proposed by masterleinad)
#15120: Add an example to the documentation of GridTools::transform(). (proposed by bangerth; merged)
#15119: Update PETSc compatibility stuff for SNES and TS (proposed by stefanozampini; merged)
#15118: PETScWrappers: update KSP support (proposed by stefanozampini; merged)
#15079: More gracefully deal with Windoze line endings. (proposed by bangerth; merged)
#15065: PETScWrappers: Add support for nonlinear solver (proposed by stefanozampini; merged)
#15051: Return objects by value, rather than via a reference. (proposed by bangerth; merged)
#14969: Add a move assignment operator to LA::d::V. (proposed by drwells; merged)
#14866: Warn users about FE index mismatch instead of silently dropping them. (proposed by marcfehling; merged)
And this is a list of recently opened or closed discussions:
#15148 Multigrid for non-nested levels (opened)
#15123 gcc11 O3 warnings (opened)
#15111 ParameterAcceptor::clear() leads to use after free (closed)
#15090 Can't compile current master with PETSc 3.7.4 (closed)
#15080 Fix the spelling of Nicolson (closed)
#14841 active_dof_index out of range gives no exception when FECollection has size 1 (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.