<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div><span></span></div><div><div><br></div><div><br>Le 3 avr. 2019 à 21:51, Gavin Ridley <<a href="mailto:gavin.keith.ridley@gmail.com">gavin.keith.ridley@gmail.com</a>> a écrit :<br><br></div><blockquote type="cite"><div><div dir="ltr"><div>Hi Dr. Geuzaine,</div><div><br></div><div>Thanks for your response. I see the problem here now. It doesn't work after meshing, although the geometry seems to load to the GUI. Unfortunately, I need to split a surface into two surfaces, and it seems there's no way to do that to the STEP file using what's available under the OpenCASCADE kernel right now.</div></div></div></blockquote><div><br></div><div>Can you share the STEP file? It should be possible to do what you want directly in Gmsh. </div><div><br></div><br><blockquote type="cite"><div><div dir="ltr"><div> I was hoping to be able to convert the STEP to gmsh-style geometry, then delete a surface (and its dependent volumes) and replace it with a new, split one. I'll just have to change the CAD then re-export, I suppose.</div><div><br></div><div>Thanks again!<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Apr 3, 2019 at 3:11 PM Christophe Geuzaine <<a href="mailto:cgeuzaine@uliege.be">cgeuzaine@uliege.be</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br>
<br>
> On 3 Apr 2019, at 18:23, Gavin Ridley <<a href="mailto:gavin.keith.ridley@gmail.com" target="_blank">gavin.keith.ridley@gmail.com</a>> wrote:<br>
> <br>
> Hi,<br>
> <br>
> I would just like to note something to the developers regarding a perhaps unnecessary skipping of surfaces in the code.<br>
> <br>
> I recently have had to convert a STEP file with fairly complicated geometry to a GEO.<br>
<br>
Don't do that. By design, Gmsh never translates from one CAD format to another. The "unrolled GEO" feature is there for unrolling complex GEO scripts. It can indeed export a limited subset of geometrical entities created by other CAD kernels, but it's there only for debugging.<br>
<br>
If you want to modify a STEP model, set<br>
<br>
SetFactory("OpenCASCADE");<br>
<br>
at the beginning of your script. Since we import STEP models with OpenCASCADE, this will allow you to modify the file directly with OpenCASCADE. See <a href="https://gitlab.onelab.info/gmsh/gmsh/blob/master/demos/boolean/import.geo" rel="noreferrer" target="_blank">https://gitlab.onelab.info/gmsh/gmsh/blob/master/demos/boolean/import.geo</a> for an example.<br>
<br>
Christophe<br>
<br>
<br>
<br>
<br>
> This is done so that I can split one of the surfaces in the STEP file to set different BCs on different parts of the surface. At the moment, it appears that gmsh will skip several surfaces in the conversion from STEP to geo_unrolled unnecessarily: surfaces were left out from the gmsh file. A warning message comes with this.<br>
> <br>
> It seems, however, that the skipped surfaces work fine if you just go back in and add surfaces manually. Gmsh now reads the geo file correctly.<br>
> <br>
> So, why are these surfaces being skipped? Is there some ambiguity about their interpretation from STEP? It would be nice to not have to manually go in and add the surfaces.<br>
> <br>
> -- <br>
> Thanks,<br>
> Gavin Ridley<br>
> _______________________________________________<br>
> gmsh mailing list<br>
> <a href="mailto:gmsh@onelab.info" target="_blank">gmsh@onelab.info</a><br>
> <a href="http://onelab.info/mailman/listinfo/gmsh" rel="noreferrer" target="_blank">http://onelab.info/mailman/listinfo/gmsh</a><br>
<br>
— <br>
Prof. Christophe Geuzaine<br>
University of Liege, Electrical Engineering and Computer Science <br>
<a href="http://www.montefiore.ulg.ac.be/~geuzaine" rel="noreferrer" target="_blank">http://www.montefiore.ulg.ac.be/~geuzaine</a><br>
<br>
<br>
<br>
</blockquote></div><br clear="all"><br>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr">Thanks,<div>Gavin Ridley</div></div></div>
</div></blockquote></div></body></html>