Re: [deal.II] Facilities for computing the "goodness" of a mesh (i.e. something like a mesh-quality indicator)

On 1/15/20 10:42 AM, Krishnakumar Gopalakrishnan wrote: > > Thank you. This is certainly looking useful.  Do we have any example usage of > this function? For example, how do we re-compute the mesh based on the return > value from this aspect_ratio function or something? Other than the

Re: [deal.II] Facilities for computing the "goodness" of a mesh (i.e. something like a mesh-quality indicator)

Dear Krishna, There is also this long-standing pull request https://github.com/dealii/dealii/pull/8196 that hooks into the Verdict library to do mesh quality assessment. One day, hopefully in the not too distant future, I’ll get back to integrating

Re: [deal.II] Facilities for computing the "goodness" of a mesh (i.e. something like a mesh-quality indicator)

Hi Martin, Thank you. This is certainly looking useful. Do we have any example usage of this function? For example, how do we re-compute the mesh based on the return value from this aspect_ratio function or something? Krishna On Wednesday, January 15, 2020 at 5:31:34 PM UTC, Martin

Re: [deal.II] Facilities for computing the "goodness" of a mesh (i.e. something like a mesh-quality indicator)

Dear Krishna, We have recently added one such function, namely GridTools::compute_aspect_ratio_of_cells(), https://dealii.org/developer/doxygen/deal.II/namespaceGridTools.html#a2a9d8801d952ea8afa9ec1573229a329 Best, Martin On 15.01.20 18:26, Krishnakumar Gopalakrishnan wrote: In the

[deal.II] Facilities for computing the "goodness" of a mesh (i.e. something like a mesh-quality indicator)

In the results/extension section of Step-6 as well in Step-49, there is a great deal of discussion about obtaining good meshes are for a problem, with the caveat that this is a highly specialized topic. Step-49 is full of warnings about things that can go wrong when applying certain