<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from text --><style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<meta content="text/html; charset=UTF-8">
<style type="text/css" style="">
<!--
p
{margin-top:0;
margin-bottom:0}
-->
</style>
<div dir="ltr">
<div id="x_divtagdefaultwrapper" dir="ltr" style="font-size:12pt; color:#000000; font-family:Calibri,Helvetica,sans-serif">
<p>Hello,</p>
<p><br>
</p>
<p>ok this makes sense. In the meantime i tried the procedure with</p>
<p>a tet-mesh and this works as intended.</p>
<p><br>
</p>
<p>So thanks again Carsten and Andreas.</p>
<p><br>
</p>
<p>Best regards,</p>
<p>Max<br>
</p>
</div>
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="x_divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><b>Von:</b> Carsten Gräser <graeser@mi.fu-berlin.de><br>
<b>Gesendet:</b> Montag, 24. August 2020 16:24:04<br>
<b>An:</b> dune@lists.dune-project.org<br>
<b>Cc:</b> Firmbach, Max<br>
<b>Betreff:</b> Re: [Dune] Boundary conditions, segments and indexing</font>
<div> </div>
</div>
</div>
<font size="2"><span style="font-size:10pt;">
<div class="PlainText">[This accidentally went into a private reply. I'm sending<br>
it to the list, too, for completeness.]<br>
<br>
Hi Max,<br>
<br>
Am 24.08.20 um 14:29 schrieb Firmbach, Max:<br>
[...]> I don't insert the boundary segments "specifically by myself", the<br>
> gmsh reader does that. I only use the factory that is given back,<br>
> in terms of the insertion index of the intersections<br>
> (like i only call the read function from the gmsh parser in DUNE,<br>
> everything there is a blackbox for me). I just specified everything<br>
> in the .msh file, I dont know in which order DUNE inserts them.this<br>
iswhat I was looking for. Now it's clear that the<br>
ordering of boundary segments in the .msh is not consistent<br>
with the generated mesh, according to the output of your<br>
program.<br>
<br>
Looking at the gmsh reader code it seems that it simply does not<br>
insert boundary segments of type 3, a.k. "4-node quadrilateral".<br>
Unfortunately there's also no error message or warning printed.<br>
Maybe it's easy to fix this - I'll have a look. I opened a bug<br>
report to document the issue and track the discussion:<br>
<br>
<a href="https://gitlab.dune-project.org/core/dune-grid/-/issues/115">https://gitlab.dune-project.org/core/dune-grid/-/issues/115</a><br>
<br>
Best,<br>
Carsten<br>
<br>
<br>
<br>
<br>
</div>
</span></font>
</body>
</html>