Hi Charles, 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 Best Regards, Thomas 2010/6/22 Fotios Sioutis <sfo...@gmail.com> > Hi Charles > > Just an Idea : > > Try to create a compound object containing all the "groove" objects, and > then try to call BRepAlgoAPI_Cut only once.Maybe it will help with the speed > problem. > > Fotis > > > On Tue, Jun 22, 2010 at 12:15 AM, Dave Cowden <dave.cow...@gmail.com>wrote: > >> Hi, Charles: >> >> I have implemented a slicer here, which performs much much better than >> that: >> >> http://code.google.com/p/emcfab >> >> <http://code.google.com/p/emcfab>please feel free to steal code if it >> helps-- i have a couple of utility wraper classes for creating slices. >> >> Just looking briefly at your code, i'd guess that displaying your slices >> may be your culprit. display is very very very slow-- most of the time i >> cannot get things to run when i display lots of objects. But when i go in >> and display only a few things it is very fast. >> >> HTH >> Dave >> >> On Mon, Jun 21, 2010 at 4:39 PM, Charles McCreary < >> charles.r.mccre...@gmail.com> wrote: >> >>> This is cross-posted to the OpenCascade forum ( >>> http://www.opencascade.org/org/forum/thread_18806/): >>> >>> The attached python script demonstrates a particularly difficult problem >>> I'm trying to solve. I've tried this in SolidWorks 2009 x64 and it >>> *eventually* creates the geometry but crashes while attempting to save as a >>> STEP or STL file. I'm looking for recommendations on how I can speed up the >>> process. The transverse cuts are completed rather quickly since the only >>> intersections are with the rectangular block. The longitudinal cuts take >>> about 20 minutes each and there are 108! The longitudinal cuts cut through >>> each of the 283 transverse cuts as well as the rectangular blocks. >>> >>> >>> -- >>> Charles McCreary P.E. >>> CRM Engineering >>> 903.643.3490 - office >>> 903.224.5701 - mobile/GV >>> >>> _______________________________________________ >>> Pythonocc-users mailing list >>> Pythonocc-users@gna.org >>> https://mail.gna.org/listinfo/pythonocc-users >>> >>> >> >> _______________________________________________ >> Pythonocc-users mailing list >> Pythonocc-users@gna.org >> https://mail.gna.org/listinfo/pythonocc-users >> >> > > _______________________________________________ > Pythonocc-users mailing list > Pythonocc-users@gna.org > https://mail.gna.org/listinfo/pythonocc-users > >
_______________________________________________ Pythonocc-users mailing list Pythonocc-users@gna.org https://mail.gna.org/listinfo/pythonocc-users
