That is my fault, sorry. I have been wondering if anyone would notice this bug. See my message below
https://mail.gnu.org/archive/html/getfem-commits/2021-05/msg00000.html If you have the possibility to contribute a fix it would be great. Otherwise, a workaround is to export to the older gmsh format v2, where our implementation for reading physical regions works correctly. Best regards Kostas On Tue, Jun 8, 2021 at 5:11 PM BLANCKAERT Benjamin < benjamin.blancka...@entpe.fr> wrote: > Dear Getfem-users, > > I am working on a problem in which I have to define different materials. > To simplify the creation of the regions, I use GMSH. > > In GMSH I define physical elements. These objects are suppposed to be > recognised by getfem as regions, but in my case it does not work and I > don't understand why. > > Has anyone already met this kind of problem. > > I transmit my .py file in which I create the mesh and then I try to > recognise my region on getfem. > > I hope you would be able to help me. > > Thank you, > > Best regards. > > > > *Blanckaert Benjamin* > > > >
