deal.II Newsletter #83
Rene Gassmoeller
Hello everyone!
This is deal.II newsletter #83.
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:
#8317: Doxygen: step 63 table newline (proposed by tjhei)
#8315: Fix typo and language inaccuracy in 9.1 changelog (proposed by kronbichler; merged)
#8314: Use LaTeX bibliography in step-14 (proposed by adam4130)
#8313: Block Compressed Sparse Row matrix/multivector usable with matrix-free framework (proposed by davydden)
#8312: Replace boost::random (proposed by masterleinad)
#8311: Avoid unused variable in dof_handler_policy.cc (proposed by kronbichler; merged)
#8310: Use std::shuffle (proposed by adam4130; merged)
#8308: Correct reading in MPIEXEC_PREFLAGS containing spaces (proposed by kronbichler)
#8307: Elementwise multiplication for Tensor (proposed by anates)
#8305: Unify coarsening properties for cell characteristics. (proposed by marcfehling)
#8304: Apply FEDomination algorithm on non-distributed SolutionTransfer. (proposed by marcfehling; merged)
#8303: Apply FEDomination algorithm on non-distributed SolutionTransfer. (proposed by marcfehling)
#8302: Changed extract_dofs so that it works in parallel (proposed by mathsen; merged)
#8298: Replace MPI_Allgather by MPI_Exscan (proposed by kronbichler; merged)
And this is a list of recently opened or closed discussions:
#8316 LineMinimization not showing up in documentation (opened and closed)
#8309 Documentation of Triangulation::set_manifold is incorrect (opened)
#8306 Replace n_..._dofs_per_processor in distribute_sparsity_pattern (opened)
#8067 Do not store IndexSet of all ranks in DoFHandler's NumberCache (closed)
#313 Provide facilities to compute the most inclusive element in an hp::FECollection (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.