On 3/19/19 4:17 AM, luca.heltai wrote:
> what would you think of a function in GridTools like
>
> GridTools::propagate_internal_manifold_ids(tria, disambiguation_function)
>
> that would loop over all cells, loop over all faces, check if the neighbor
> manifold id is the same of this cell, and
Nicola,
what would you think of a function in GridTools like
GridTools::propagate_internal_manifold_ids(tria, disambiguation_function)
that would loop over all cells, loop over all faces, check if the neighbor
manifold id is the same of this cell, and
i) the two ids are the same: assign the
I agree that the choice is ambiguous on the faces.
However a practical problem remains, let's assume that a user wants to
import a very big geometry with a lot of internal faces. Right now he would
need to specify all the possible faces in the input file (with an
increasing possibility of
I believe the first point is a bug of the read_ucd function.
I opened an issue for this (https://github.com/dealii/dealii/issues/7802)
The second point, however, is a feature. What should you do when two material
ids meet? I think it is the responsability of the user to make sure that the
Dear all,
PR 7775 has revealed some critical issues in the handling of manifold_id in
codim-1 domain.
-) I believe that GridIn.read_ucd appears to ignore manifold ids associated
to the cells, it seems to me that the flag
apply_all_indicators_to_manifold_ids does not affect the manifold id for
