<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7652.24">
<TITLE>Re: [Gmsh] howto import STEP/IGES/BREP file?</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=2>Hello to all,<BR>
<BR>
On the same topic, the use of IGES/STEP/BREP files, I also have a<BR>
question. I could import correctly the geometry .iges, but when asking<BR>
to mesh in 3D a fatal error forced Gmsh to abort and quit. This occur<BR>
when Gmsh try to mesh in 2D (no error for meshing in 1D) due to<BR>
"Segmentation violation (invalid memory reference)".<BR>
<BR>
<BR>
I work with the executable file Gmsh (not compiled on my own system) on<BR>
a labtop ACER under GNU/Linux Suse 10.3. I have attached the error file<BR>
.gmsh-errors.<BR>
<BR>
Thank you for any advises on how to proceed to mesh in 3D an imported<BR>
.iges file.<BR>
<BR>
Mireille<BR>
<BR>
Christophe Geuzaine a écrit :<BR>
> Edgar Last wrote:<BR>
>> Thanks for the solutions how to configure gmsh with opencascade support<BR>
>> and how to import a STEP file.<BR>
>><BR>
>> Now I wonder how I can set the characteristic lengths in an imported<BR>
>> geometry. Is there no documentation how to use the import feature? I<BR>
>> will probably have many more questions about what shapes can be meshed,<BR>
>> mesh control etc. Do I need to take the source code for the only<BR>
>> "documentation"?<BR>
><BR>
> Using a nightly snapshot, you have many options:<BR>
><BR>
> 1) Specify a global scaling factor (using e.g. "-clscale" on the command<BR>
> line). When no char. lengths are provided (which is the case when you<BR>
> load a normal STEP file), a default length of "object_size/10" is used.<BR>
> Using "-clscale 0.1" will divide this default length by 10.<BR>
><BR>
> 2) Specify a min and/or a max char. length, using the "-clmin" and<BR>
> "-clmax" command line options.<BR>
><BR>
> 3) Compute the char. length automatically from the curvatures, using<BR>
> "-clcurv".<BR>
><BR>
> 4) Use a background mesh (see tutorial/t7.geo).<BR>
><BR>
> 5) Merge your STEP file in a GEO file, and use all the char. length<BR>
> modification options available in the .geo language. In addition to the<BR>
> options given above (for example,<BR>
> "Mesh.CharacteristicLengthFactor=0.1;" in a GEO file is the same as<BR>
> "-clscale 0.1" on the command line), you have also full access to char.<BR>
> lengths associated with points, function-based size fields, etc.<BR>
><BR>
><BR>
><BR>
>> Btw, I am now using the precompiled gmsh version from the gmsh website,<BR>
>> which is fine for the moment. The configure options you suggested didn't<BR>
>> have any effect. I used:<BR>
>> ./configure --enable-occ --with-occ-prefix=/opt/local/opencascade<BR>
>> Configure produced no output at all mentioning occ, is this to be<BR>
>> expected? Compilation was successful, but no import possible. This is<BR>
>> not a severe problem right now, because I can use the precompiled<BR>
>> binary. However, I'd like to be able to compile with occ support. How<BR>
>> can I find out why configure doesn't recognize occ?<BR>
>><BR>
>> Edgar<BR>
>><BR>
>> ------------------------------------------------------------------------<BR>
>> Express yourself instantly with MSN Messenger! MSN Messenger<BR>
>> <<A HREF="http://clk.atdmt.com/AVE/go/onm00200471ave/direct/01/">http://clk.atdmt.com/AVE/go/onm00200471ave/direct/01/</A>><BR>
>><BR>
>><BR>
>> ------------------------------------------------------------------------<BR>
>><BR>
>> _______________________________________________<BR>
>> gmsh mailing list<BR>
>> gmsh@geuz.org<BR>
>> <A HREF="http://www.geuz.org/mailman/listinfo/gmsh">http://www.geuz.org/mailman/listinfo/gmsh</A><BR>
><BR>
><BR>
</FONT>
</P>
</BODY>
</HTML>