[Gmsh] Slow opening with multiple opencascade geometries

[andrew]

The time needed for Boolean operations does grow with the opencascade
model. I have noticed that behavior with Salome too.

One solution I found was to treat the geometries with a binary tree logic.
Instead of
final_obj=cut (obj1) with obj(2,3,4,5)
to do
temp_obj1=cut obj1 with obj2,3
temp_obj2=cut obj1 with obj4,5
final_obj=cut temp_obj1 with temp_obj2

or something like that. It increases the complexity of the coding but it
gets there faster. I had done these tests with Salome but since it uses the
same geometry model I believe that the results hold with gmsh as well

kind regards

Andrew



2018-01-29 12:22 GMT+02:00 GIORGIO PALMA <giorgio.palma at uniroma3.it>:

> Dear all,
> I'm using the 3.0.6 version of Gmsh.
>
> I'm generating my geometry (attached) using multiple boolean operations
> with the OpenCascade kernel.
> When I try to increase the complexity of the geometry, adding more
> obejcts, things start to go bad:
>
> time required for opening the geo file increases exponentially, I'd say
> not acceptably.
>
> Can you suggest any workaround?
> Thank you,
>
> Giorgio Palma
>
> _______________________________________________
> gmsh mailing list
> gmsh at onelab.info
> http://onelab.info/mailman/listinfo/gmsh
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://onelab.info/pipermail/gmsh/attachments/20180129/6c627886/attachment.html>