deal.II Newsletter #128

17 views
Skip to first unread message

Rene Gassmoeller

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

Hello everyone!

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

#10792: fix tests/simplex/data_out_write_vtk_01 (proposed by tjhei; merged)
#10791: Update an outdated code comment (proposed by kronbichler; merged)
#10790: Debug (proposed by peterrum)
#10789: Simplex action: load metis and be verbose on failure (proposed by peterrum; merged)
#10788: fix dof_accessor warning (proposed by tjhei; merged)
#10787: Jenkinsfile: convert tabs to spaces (proposed by tjhei; merged)
#10786: jenkins: use Og on tester (proposed by tjhei)
#10785: Fix MPIEXEC detection again. (proposed by drwells; merged)
#10784: Use face_no in FE (proposed by peterrum)
#10783: Pass face_no to FE functions (proposed by peterrum)
#10782: Fix step-18. (proposed by adamqc; merged)
#10781: Simplify some code. (proposed by bangerth)
#10780: Convert all face-related data structures of FiniteElement to vectors (proposed by peterrum; merged)
#10779: Add face_no to methods of FiniteElements (proposed by peterrum; merged)
#10778: Generalize FiniteElementData s.t. faces can different nr. of dofs (proposed by peterrum)
#10777: Introduce FiniteElementData::max_dofs_per_quad() (proposed by peterrum; merged)
#10776: Refactor DoFHandlerImplementation::reserve_space for 3D (proposed by peterrum; merged)
#10775: Simplify the usage of ensure_existence_of_dof_identities (proposed by peterrum; merged)
#10774: suppress boost warnings (proposed by tjhei; merged)
#10773: CI: change git depth for indent worker (proposed by tjhei; merged)
#10772: Update an error text. (proposed by bangerth; merged)
#10771: fix typos in step 47 (proposed by zjiaqi2018; merged)
#10770: Enable VectorTools::interpolate for hp::MappingCollection (proposed by peterrum; merged)
#10769: Fix conflict with Simplex::GridGenerator (proposed by peterrum; merged)
#10768: Improve DataOutDoFData error message ExcInvalidVectorSize (proposed by masterleinad; merged)
#10766: Non local dofs (inside FE) (proposed by luca-heltai)
#10764: Assign faces different quadrature rules (proposed by peterrum)
#10762: MF mapping info: Avoid invalid access of some face-data-by-cells (proposed by kronbichler)
#10761: [step-67] Close a brace in introduction (proposed by kronbichler; merged)
#10760: Do not update ghost values in MGTransferMatrixFree::prolongate (proposed by kronbichler; merged)
#10759: delete a word in step-47 (proposed by tjhei; merged)
#10758: Add mini simplex application tests (proposed by peterrum)
#10757: CI: add tester for simplex tests (proposed by peterrum; merged)
#10752: Improve memory behavior of the BiCGStab solver. (proposed by bangerth; merged)
#10748: GridIn::read_vtk() for simplex meshes (proposed by peterrum; merged)
#10734: Check that MPIEXEC_EXECUTABLE is available in the test suite. (proposed by drwells; merged)
#10727: GridIn::read_msh() now supports triangular and tetrahedral elements (proposed by DanielPaukner; merged)
#10701: Generalize DataOut::write_vtk for simplex mesh (proposed by peterrum; merged)
#10659: Introduce MappingFE (proposed by peterrum; merged)
#10653: Remove unused tests (proposed by dangars; merged)
#9973: make ARKode ODE solver use DiscreteTime internally (proposed by rezarastak; merged)

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

#10767 Misleading error message in add_data_vector() function. (opened and closed)
#10765 doxygen is confused by simplex namespace (opened and closed)
#10763 Geometry compression for face data by cells in MappingInfo (opened)
#10331 Configuration, make setup_tests etc. succeed even if MPIEXEC_EXECUTABLE is not found (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