> You can also speedup the slicing process by distributing the computation over
> many cores (with the help of the multiprocess python module). Have a look to
> the slides 17 and 18 of this slideshow:
> http://www.pythonocc.org/resources/presentations_events/product-data-exchange-2009-conference-pde2009/.
> This multiprocess slicing is enabled by the shared serialization of
> TopoDS_Shape objects.
>
> The source code is available at:
> http://code.google.com/p/pythonocc/source/browse/trunk/src/examples/Level2/Concurrency/parallel_slicer.py
True, for computing slices the multi-core approach works.
However -and I think this is the case we're dealing with- if you change the
object than of course using several processes doesn't speed things up, since
the processes will simple be waiting for another process to finish. Fotios
advice on constructing a compound object and than performing the boolean
operation is most likely the way to go. I also used that trick a number of
times with success.
A note on display speed; by default, the display.DisplayShape method updates
the viewer. If you use the display.DisplayShape( someShape, update=False ) the
viewer will not redraw, which results in a considerable speed up. Note that you
can also supply a list of TopoDS_* instances as argument.
-jelle
_______________________________________________
Pythonocc-users mailing list
Pythonocc-users@gna.org
https://mail.gna.org/listinfo/pythonocc-users
