deal.II Newsletter #271
Rene Gassmoeller
Hello everyone!
This is deal.II newsletter #271.
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:
#16385: Test examples (proposed by tjhei)
#16382: FEPointEvaluation::integrate(): Only zero out relevant DoFs (proposed by jh66637)
#16381: Fix spelling in a CI step. (proposed by bangerth; merged)
#16380: Add reinit_faces() for Quadrature<dim> (proposed by jh66637)
#16379: Use combined_orientation in two more FiniteElement functions. (proposed by drwells; merged)
#16378: Prohibit calling compress() on vectors with ghost elements. (proposed by bangerth)
#16377: More small updates to tria_description.cc. (proposed by bangerth)
#16375: Fix an unused variable warning. (proposed by drwells; merged)
#16374: Convert CreateDescriptionFromTriangulationHelper into a function. (proposed by bangerth)
#16373: Use face_orientation to encode 2D orientation information. (proposed by drwells; merged)
#16371: Introduce a function Utilities::MPI::partial_and_total_sum(). (proposed by bangerth; merged)
#16370: Improve documentation of TriangulationDescription and members. (proposed by bangerth; merged)
#16369: Some cleanups to create_description_from_triangulation(). (proposed by bangerth; merged)
#16368: Better document create_description_from_triangulation(). (proposed by bangerth; merged)
#16367: Choose a better name for a template argument. (proposed by bangerth; merged)
#16365: Fix the names of functions in the documentation of step-42. (proposed by bangerth; merged)
#16363: github-actions: simplify oneAPI setup with external action. (proposed by marcfehling)
#16362: Bump actions/upload-artifact from 3 to 4 (proposed by dependabot[bot]; merged)
#16361: Some more FEValuesBase cleanups (proposed by bangerth; merged)
#16359: Introduce FEFacePointEvaluation with optimized FCL path (proposed by bergbauer)
#16358: Minor update to the introduction of step-41. (proposed by bangerth; merged)
#16357: Choose a more efficient algorithm. (proposed by bangerth; merged)
#16355: Use std::variant instead of a hand-rolled version. (proposed by bangerth; merged)
#16354: Use a C++17 feature to make code more readable. (proposed by bangerth; merged)
#16352: Correct a condition. (proposed by bangerth; merged)
#16351: Do not create arrays we do not use. (proposed by bangerth; merged)
#16350: Use std::optional instead of a hand-rolled version of it. (proposed by bangerth; merged)
#16349: Disallow using direction flags for spacedim>dim+1. (proposed by bangerth; merged)
#16347: Add a test for a recent patch. (proposed by bangerth; merged)
#16239: KINSOL: option to select QR orthogonalization strategy (proposed by sebproell; merged)
#16237: Actually fix Triangulation copydocs (proposed by jpthiele; merged)
And this is a list of recently opened or closed discussions:
#16386 Regression tester regressed e7f6e8 (opened)
#16384 step-14 segfaults in release mode (opened)
#16383 step-9 crash in cycle 5 in release mode (opened)
#16376 Communicator equality: same object vs. MPI_Comm_compare() (opened)
#16372 Regression tester regressed 494449 (opened and closed)
#16366 deal.ii vector and block_vector interaction (opened and closed)
#16364 Difficulties with complex matrices (opened)
#16360 Regression tester regressed 83805c (opened and closed)
#16356 Merge triangulation duplicate_vertex_tolerance (opened and closed)
#16353 Regression tester regressed a87a96 (opened and closed)
#16346 Use std::optional in fe_values_base.h/cc. (closed)
#16343 Disallow direction flags for lines in 3d. (closed)
#16326 GridGenerator::merge_triangulation() and GridGenerator::replicate_triangulation() error (closed)
#16144 Fix wrong comparison in compute_prefix_sum(). (closed)
#16008 The step-42 documentation references functions no longer named that way. (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.