deal.II Newsletter #123

16 views
Skip to first unread message

Rene Gassmoeller

unread,
Jun 19, 2020, 3:00:35 PM6/19/20
to dea...@googlegroups.com

Hello everyone!

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

#10559: Remove DoFHandlerType from hp::FEValues templates. (proposed by drwells)
#10558: Cleanup DoFTools hp::DoFhandler (proposed by masterleinad)
#10557: Remove DoFHandlerType from FEValues templates. (proposed by drwells)
#10555: Remove DoFHandlerType from dof_handler_policy.h/.cc (proposed by peterrum)
#10554: Small generialization in tria_description.cc (proposed by peterrum; merged)
#10553: Update output of tests/grid/grid_tools_cache_04 (proposed by peterrum; merged)
#10552: Simplify CellAccessor::at_boundary() (proposed by peterrum; merged)
#10551: Remove usused internal function (proposed by peterrum; merged)
#10550: Fix detection of muParser 2.3.2. (proposed by drwells)
#10549: Use neutral terminology where possible (proposed by jppelteret)
#10547: Avoid accessing artificial cells in ParticleHandler (proposed by masterleinad; merged)
#10546: work around clang10 warnings (proposed by tjhei; merged)
#10545: introduce GridTools::cell_measure for std::vector (proposed by tjhei)
#10543: Fix missing instantiations for point_gradient (proposed by masterleinad; merged)
#10542: Pass number of vertices to CellData (proposed by peterrum; merged)
#10541: Specify std namespace (proposed by peterrum; merged)
#10540: fix bug in fast version of GridTools::find_active_cell_around_point() (proposed by nfehn)
#10539: Do not use 'black/whitelist' language. (proposed by bangerth; merged)
#10538: Remove DoFHandlerType from MatrixFree::reinit() (proposed by peterrum; merged)
#10536: Particles as indexable. (proposed by luca-heltai; merged)
#10534: [9.2] Takeover #10533: Add a missing contributor to a changelog entry (proposed by jppelteret; merged)
#10533: Add a missing contributor to a changelog entry (proposed by jppelteret; merged)
#10532: Emit warning when AppleClang < 9.0 is detected (proposed by jppelteret)
#10529: Fix number_cache.ghost_owners (proposed by peterrum)
#10528: Use active_cell_index() in KellyErrorEstimator::estimate() (proposed by peterrum; merged)
#10527: Check in GridRefinement::refine()/coarsen() if cell is locally owned (proposed by peterrum; merged)
#10526: Fix hp_choose_p_over_h test (proposed by peterrum)
#10525: Enable non-default VectorizedArrayType in read_cell_data() (proposed by DavidSCN; merged)
#10524: Remove MGCoarseGridLACIteration (proposed by masterleinad; merged)
#10523: Thread/Task: Fix Schmidt's double checking (proposed by tamiko; merged)
#10520: Clarify docu of GridTools::find_active_cell_around_point() (proposed by nfehn; merged)
#10516: Merge implementations of exchange_cell_data_to_(level)_ghosts (proposed by peterrum; merged)
#10481: MGTransferPrebuilt custom constraints test (proposed by tcclevenger; merged)
#10363: GridTools::Cache::get_locally_owned_cell_bounding_boxes_rtree() (proposed by luca-heltai; merged)
#10334: Split up MatrixFree::initialize_indices to speed up compilation (proposed by kronbichler; merged)

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

#10556 PETScVectorBase::max and ::min are currently deprecated (opened)
#10548 muParser module doesn't work any more (opened)
#10544 How to implement moving mesh (opened)
#10537 Boost signals overkill for particle_lost()? (opened and closed)
#10535 Improve design of GridTools::find_active_cell_around_point() (opened)
#10531 shared_timed_mutex not available on older versions of MacOS (opened)
#10530 Redefinition of CellAccessor::active_cell_index() (opened)
#10459 Clarify expected behavior of GridTools::find_active_cell_around_point() (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