Hello Luca,
Thanks for your suggestion. I was able to figure out an issue regarding the
order of elements in the mesh. After fixing that and without using physical
groups, I am able to read the mesh, but during computation, it seems at
some point deal.ii is finding a negative volume fraction,
Gmsh is a bit arbitrary on how elements are oriented. Deal.II, on the contrary,
requires elements to be consistently ordered. If you have generated your
geometries with some elementary geometry types, by specifying the bounding
faces, make sure you list the faces always in the same order (i.e.,
Krishan,
Do you have minimal input file to share that shows your problem?
Best,
Daniel
Am Di., 2. März 2021 um 10:12 Uhr schrieb krishan...@gmail.com <
krishanu.se...@gmail.com>:
> Hi Luca,
>
> Thanks for the response. I recreated the mesh to make sure that there is
> no two physical tag for
Hi Luca,
Thanks for the response. I recreated the mesh to make sure that there is no
two physical tag for the same object. I found that if I do not set any
physical tag, my code is able to read the mesh without any issue. But when
I am setting 4 different physical tags to 4 parts of the
The error message is telling you that you specified more than one physical tag
for the same object. This is not compatible with deal.II, at the moment, as the
physical tags are used by deal.II to specify what material id (on cells) or
boundary id (on faces and possibly edges) to assign to each
I am trying to read a mesh (.msh file) generated by Gmsh (version 4.7.1),
but getting an error. I am using the following commands:
GridIn grid_in;
grid_in.attach_triangulation(triangulation);
std::ifstream input_file("ma_mesh3.msh");
