<html>
<head>
<meta name="generator" content="Windows Mail 17.5.9600.20689">
<style type="text/css"><!--html { font-family: "Color Emoji", "Calibri", "Segoe UI", "Meiryo", "Microsoft YaHei UI", "Microsoft JhengHei UI", "Malgun Gothic", "sans-serif"; }--></style><style data-externalstyle="true"><!--
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph {
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
}
p.MsoNormal, li.MsoNormal, div.MsoNormal {
margin:0in;
margin-bottom:.0001pt;
}
p.MsoListParagraphCxSpFirst, li.MsoListParagraphCxSpFirst, div.MsoListParagraphCxSpFirst,
p.MsoListParagraphCxSpMiddle, li.MsoListParagraphCxSpMiddle, div.MsoListParagraphCxSpMiddle,
p.MsoListParagraphCxSpLast, li.MsoListParagraphCxSpLast, div.MsoListParagraphCxSpLast {
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
line-height:115%;
}
--></style></head>
<body dir="ltr">
<div data-externalstyle="false" dir="ltr" style="font-family: 'Calibri', 'Segoe UI', 'Meiryo', 'Microsoft YaHei UI', 'Microsoft JhengHei UI', 'Malgun Gothic', 'sans-serif';font-size:12pt;"><div>Thanks for your reply.<br>Yes, the problem also occurs with today’s nightly build.</div><div><br></div><div data-signatureblock="true"><br></div><div style="padding-top: 5px; border-top-color: rgb(229, 229, 229); border-top-width: 1px; border-top-style: solid;"><div><font face=" 'Calibri', 'Segoe UI', 'Meiryo', 'Microsoft YaHei UI', 'Microsoft JhengHei UI', 'Malgun Gothic', 'sans-serif'" style='line-height: 15pt; letter-spacing: 0.02em; font-family: "Calibri", "Segoe UI", "Meiryo", "Microsoft YaHei UI", "Microsoft JhengHei UI", "Malgun Gothic", "sans-serif"; font-size: 12pt;'><b>Von:</b> <a href="mailto:cgeuzaine@ulg.ac.be" target="_parent">Christophe Geuzaine</a><br><b>Gesendet:</b> Mittwoch, 28. Januar 2015 20:26<br><b>An:</b> <a href="mailto:guido.schmid@nmtec.ch" target="_parent">guido.schmid@nmtec.ch</a><br><b>Cc:</b> <a href="mailto:gmsh@geuz.org" target="_parent">gmsh@geuz.org</a></font></div></div><div><br></div><div dir=""><div id="readingPaneBodyContent"><br>> On 23 Jan 2015, at 15:39, guido.schmid@nmtec.ch wrote:<br>> <br>> Hi,<br>> <br>> I have a problem defining physical surfaces in gmsh. The attached geo file consists of two lines. The first line merges a step file which consists of two cubes. The other defines a simple physical surface. <br>> <br>> As soon as the option “cut and merge faces” (Geometry.OCCConnectFaces = 1) is turned on, the physical surface randomly changes its position every time the geo file is reloaded. This behaviour makes it impossible to define physical surfaces for merged step files, if the option “cut and merge faces” is used.<br>> <br>> Is there a way to avoid this behaviour or is this a gmsh bug?<br>> <br><br>"Cut and merge faces" is definitely "beta quality"; the code should be checked to see if there is no pointer dependent ordering which would explain the behaviour you see. (Do you see this with the latest nightly builds?)<br><br>> Best regards<br>> Guido<br>> <br>> <2cube.geo><2cube.step>_______________________________________________<br>> gmsh mailing list<br>> gmsh@geuz.org<br>> http://www.geuz.org/mailman/listinfo/gmsh<br><br>-- <br>Prof. Christophe Geuzaine<br>University of Liege, Electrical Engineering and Computer Science <br>http://www.montefiore.ulg.ac.be/~geuzaine<br><br><br><br></div></div></div>
</body>
</html>