Wykres commitów

94 Commity (9d91ecafd560bc9ba9cc134ac55d12d6cb2f1e72)

Autor SHA1 Wiadomość Data
palain ba1c2ab24c cleaning up code 2021-12-17 16:20:12 -04:00
Alain Pelletier d10f5b67bc
Update chunk.py 2021-05-21 16:16:05 -03:00
abosafia 84ed175b1f
Add files via upload 2021-05-21 20:50:13 +02:00
Alain Pelletier cea8d08340
add test for path direction 2021-05-18 16:24:09 -03:00
Alain Pelletier 5ccb38b98e
added comments and print for children parents 2021-05-17 10:46:38 -03:00
Alain Pelletier 9b61043900
automatically set lead in to first segment split 2021-05-17 08:40:39 -03:00
Alain Pelletier 61eec902ef
split at the middle of segment 2021-05-15 12:01:48 -03:00
Alain Pelletier 8bd117ce2e
brake segments for leadin 2021-05-15 10:11:59 -03:00
abosafia 3705c83ecf
Add files via upload 2021-05-15 15:03:55 +02:00
Alain Pelletier 670ef45a02
fixed start point 2021-05-13 10:34:42 -03:00
Alain Pelletier 7c800622f6
added start point to profile 2021-05-13 10:29:47 -03:00
Alain Pelletier 9b87df04be
added debug info for lead in 2021-05-13 08:26:08 -03:00
Alain Pelletier b4358fa9b0
fixed lead in lead out
lead in lead out now work with layers
2021-05-12 09:07:44 -03:00
Alain Pelletier 9a9016d4d8
added leadin and lead out
profile now has a lead in and lead out option for profile cutting Useful for torch plasma and some cutter operation.
2021-05-12 08:37:33 -03:00
Alain Pelletier b33730821a
added lead in for plasma 2021-05-11 17:50:23 -03:00
Alain Pelletier f8c92f0b8b
split curvecamtools.py
removed equation curve generation from curve cam tools and created curvecamequation.py
it is the only file dependant on equations
2021-04-08 14:52:50 -03:00
Alain Pelletier a75d186a07
CURVE strategy
modified things to work with curve strategy, put protection for maximum, minimum travel using path as following a path can plunge beyond the depth if one is not careful
2021-03-28 11:24:50 -03:00
Alain Pelletier 9bccae037b
added offsetZ
Added offsetZ to make layers in experimental curve to path
2021-03-27 12:38:43 -03:00
TurBoss f07848e1ff Fix #126 2020-10-12 18:45:08 +02:00
Adam Goldsmith 0094eae66e Convert line endings to LF and strip trailing whitespace in .py files 2019-11-15 13:13:09 -05:00
ksuprynowicz 4a77d255b0 More fixes due to 2.80 API changes 2019-08-16 14:50:57 +02:00
TurBoss b688f6f67c fix text minz 2019-03-03 23:02:43 +01:00
TurBoss edb54312a8 Fix curve tools 2019-02-21 22:47:26 +01:00
TurBoss 7b25c6ea98 Fix curve op 2019-02-20 00:28:32 +01:00
TurBoss 9b24469cfb 2.80_BETA 2019-01-25 23:48:11 +01:00
vilemnovak a348a651e0 minor offset algorithm optimization
for image based method, gives me about 8% speedup on my test here.
I did test of several ways to access numpy arrays...
2016-07-28 18:35:30 +02:00
Jeff Doyle (nfz) 179e16d04d BugFix: forgot to clear modifiers after object copy and using to_mesh()
not clearing modifiers after assigning the new higher density mesh will
cause excessive memory usage.
2016-06-05 21:47:58 -03:00
Jeff Doyle (nfz) 4e91a652d6 Oops: mesh modifiers has to be after mesh conversion 2016-06-05 15:58:34 -03:00
Jeff Doyle (nfz) 91872ccf2d Merge branch 'master' of https://github.com/vilemnovak/blendercam 2016-06-05 15:14:33 -03:00
Jeff Doyle (nfz) a24891e1a0 Bridges now support modifiers but there are still some bugs to fix 2016-06-05 15:14:14 -03:00
vilemnovak ed96067f94 Merge pull request #68 from MadDogJroc/master
Simplified datapoints in a chunk to avoid Shapely error by MadDogJroc
thanks for this patch.
I don't have a time to check this properly , but will commit it, we can remove it in future. Shapely has a simplify operator that works quite nicely. Only drawback of your solution might be some performance loss in some cases I think?
2016-06-05 17:47:31 +02:00
Jeff Doyle (nfz) d0c9f2123c meshFromCurve() function now can work with meshes with modifiers
- Online cutout needs this functionality
2016-06-05 03:26:13 -03:00
Jeff Doyle (nfz) c88597fea4 clean up unused variables 2016-06-03 22:41:39 -03:00
Jroc cd4a931002 Simplified datapoints in a chunk to avoid Shapely error - shapely.geos.TopologicalError: The operation 'GEOSDifference_r' produced a null geometry. Likely cause is invalidity of the geometry - should fix problems like this: https://github.com/vilemnovak/blendercam/issues/24 2016-06-03 14:20:50 -04:00
vilemnovak 41feb4fc2e several small changes
-more poll function improvements
- suggested threshold by nfz for pockets detection
- small warnings cleanups
2016-06-02 21:54:44 +02:00
vilemnovak 423a75ad23 ParentChildDist fix suggested by nfz
getting poly boundary actually ate performance
2016-06-02 15:20:23 +02:00
vilemnovak 4163b8d879 fix parentchilddist
I think shapely didn't measure distance to boundary, but to any point in
the chunk, which could lead to wrong sorting in outliefill. Now it
measures the distance to boundary.
2016-06-01 15:25:02 +02:00
vilemnovak 9906db02ab sorting was broken for some strategies
this was for parallel and similar, because I added extra sort for
outline fill, but that broke relationships for other strategies...
2016-05-28 14:43:09 +02:00
Jeff Doyle (nfz) 6e4ffe6f41 commented out pchunk variable which is never used 2016-05-28 00:43:37 -03:00
Jeff Doyle (nfz) 24a7dfcfb2 BugFix: ramZigZag() was using y axis value instead of z axis value for calculating new z axis value 2016-05-25 23:19:57 -03:00
vilemnovak d58b9e7392 Outlinefill sorting now works properly
Also when paths are trimmed due to depth or limit curve. Similar
approach could be used for other non-sorted 3d strategies.
Especially good with ZigZag - Meander movements.
2016-05-25 18:49:34 +02:00
vilemnovak 8e75d108de speedup Parent child distance finding probably by several orders.
This speeds up greatly finding of parent/child in pockets, outlinefill,
and probably more.
Pockets with many independent shapes were ultra-slow, not really
measurable, now should be usable....
2016-05-25 11:25:41 +02:00
vilemnovak 840bc5cab0 several changes
-revert new parallel pattern algo, isn't finished yet(parallel stepback
problem)
-curves, text, can now be used also if parented
-scan tools remove small parts tool.
2016-05-24 11:28:45 +02:00
Jeff Doyle (nfz) e1b588a1ee BugFix: firstdown for pocket operation did some strange things when sorted
Resorting a collection of chunks would yield different results than the
first sort.  This was caused by adaptdist changing the order of the
points on a chunk that had already been sorted earlier.
2016-04-10 01:36:08 -03:00
Jeff Doyle (nfz) 4ef3cacb82 Medial Axis now supports layering and first down
- added Chunk methods: isbelowZ and clampZ to assist layering
- moved medial axis strategy into its on function
2016-03-29 01:31:36 -03:00
Jeff Doyle (nfz) 0ea9ae2480 add GPL 2 license block
- fixes #36 issue - license unclear
2016-03-24 16:20:51 -03:00
vilemnovak e5c81c14d3 Overcuts operator
Generates overcuts on a curve.
- inner, or also outer polygons.
-has threshold for angles to consider

the overcuts are optimal - done so that the radius of the cutter only
touches the corner, but doesn't go behind it.
2016-01-15 00:20:30 +01:00
vilemnovak d9f29028ad optimize chunk sorting
this optimizes chunk sorting a bit, by not iterating over too many
children - some chunks could be checked many times.
For parallel operations with layers, this fixes something that was
rather a bug - because too many relations were created and this could
lead to exponential computation times relative to count of layers.
2016-01-14 08:54:57 +01:00
vilemnovak d662996752 Big Polygon library massacre + memory limit for non exact mode
the memory limit is a new feature, preventing crashes when ppl. e.g.
compute path on the default size obects, and also any other cases with
non-exact mode.

otherwise, big, happy removal of polygon library residues. This library
is NO logner a dependency of blender CAM. Shapely library works far
better in most cases. Sometimes it's slower but this can be compensated
with optimizations almost always quite easily.
2016-01-02 17:37:25 +01:00
vilemnovak 752a41629e optimize bridges code - a LOT
bridges code had some really stupid redoing - it was getting the bridges
polygon for EACH chunk which was supposed to be computed...  this proves
again my old rule - if I write something very badly , I can then enjoy
optimizations by several hundred percent :)
2015-12-30 21:25:25 +01:00