deal.II Newsletter #129

9 views
Skip to first unread message

Rene Gassmoeller

unread,
Aug 10, 2020, 12:00:28 PM8/10/20
to dea...@googlegroups.com

Hello everyone!

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

#10811: Merge implementation of gather_evaluate and integrate_scatter (proposed by peterrum; merged)
#10810: Work on MatrixFreeFunctions::FaceToCellTopology::face_orientation (proposed by peterrum; merged)
#10809: ECL: Merge gather and adjust_for_face_orientation (proposed by peterrum)
#10808: Rename two variables in MF (proposed by peterrum; merged)
#10806: Fix another bug with DataPostprocessorTensor (proposed by bangerth; merged)
#10805: Shrink the output of a test drastically. (proposed by bangerth; merged)
#10804: Fix a changelog entry. (proposed by bangerth; merged)
#10803: Fix bug in DataPostprocessorTensor. (proposed by bangerth; merged)
#10802: Avoid a couple of places where we explicitly use 'new'. (proposed by bangerth; merged)
#10801: Add CUDA 10.2 CI build check (proposed by masterleinad)
#10800: Simplify some string handling in an error message. (proposed by bangerth; merged)
#10799: Drop cuda 9 (proposed by Rombur; merged)
#10796: Fix Warray-bounds warnings (proposed by masterleinad; merged)
#10795: Fix typo in VectorTools::interpolate (proposed by peterrum; merged)
#10794: Save face type in quad_dof_identities (proposed by peterrum)
#10793: Fix CUDA 11 build (proposed by Rombur; merged)

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

#10812 Homepage certificate expired (opened)
#10807 Can't compile p::d::T class when p4est not detected (opened)
#10798 step-49 currently fails (opened)
#10797 simplex support comments (opened)
#10749 v9.2.0 is incompatible with CUDA-11 (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