Dear Bruno,
Sorry for the late reply. Here is flooding, I was driving home hours
before. You are right, in the linux version of gmsh, it always gives the
error message that cannot find the corresponding vertex, but actually I do
nothing on the cell. It is the 1e-7 rounding error that makes the sy
Honestly I don't know. I wonder if the terms -1e-07 are the problem. I
told you to remove SetFactory("OpenCASCADE") because it was the only
difference with my .geo files.
Bruno
Le mar. 22 sept. 2020 à 11:20, yuesu jin a écrit :
>
> Dear Bruno,
> The problem was solved after I removed the 'Set
Hmmm. Can you try without the SetFactory("OpenCASCADE"); and can you
send me your .msh
Bruno
Le mar. 22 sept. 2020 à 10:45, yuesu jin a écrit :
>
> Dear Bruno,
>I did some modification according to your suggestion :
>
> Physical Volume
Dear Bruno,
I did some modification according to your suggestion :
*Physical Volume("4") = {1};//+Physical Surface("0") = {4, 3, 2, 5, 1, 6};*
I add all external surfaces in one ph
You don't want to set the physical groups for the curves and the
points. This means nothing in deal.II. A vertex does not have a
boundary ID. You need all the external surfaces and the volume to have
a physical group. That's it.
Bruno
Le mar. 22 sept. 2020 à 10:24, yuesu jin a écrit :
>
> Dear B
Dear Bruno,
Thank you for your help! I added physical groups for volume, surfaces,
curves, and points. But the problem remains the same. The modified geo
file is attached below.
Best regards,
Yuesu
On Tue, Sep 22, 2020 at 7:55 AM Bruno Turcksin
wrote:
>
> Yuesu,
>
> I had the same problem rec
Yuesu,
I had the same problem recently. Our gmsh reader assumes that the user has
set boundary id and material id to the mesh. It looks like you don't have
those and so the file is read incorrectly.
Best,
Bruno
On Tuesday, September 22, 2020 at 2:04:17 AM UTC-4 jinyu...@gmail.com wrote:
> De
