Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Path optimization #82

Closed
SMG2383 opened this issue Aug 24, 2017 · 1 comment
Closed

Path optimization #82

SMG2383 opened this issue Aug 24, 2017 · 1 comment

Comments

@SMG2383
Copy link

SMG2383 commented Aug 24, 2017

Excuse me, my English is poor,I prepared a picture
aaa
Can you increase this mode? This saves time and saves time of line scanning,
23

@arkypita
Copy link
Owner

arkypita commented Aug 24, 2017

Optimizing VECTOR engraving sequence is a really interesting feature. Of course, it can only be done for the gcode generated by LaserGRBL itself (vectorization of raster import) where we can have the original vector path (optimizing gcode is more complex and require rebuilding vector path). It is already in the development roadmap, but it is a particularly complex function to develop (but some alghorithm already exists).

With raster/picture/image engraving is hundred time more complex, I'm pretty sure no professional software implement that. Complex does not mean impossible, but you have to consider not only the time for develop a good alghoritm (that is my time) but also the computational time of your computer to analyze the image and compute the best path that exponentially grow with the complexity of the image.

A "follow non white" could be a good basepoint, but have to deal with "do not forget nothing" when take a direction that exclude following another direction and with "I have already done this pixel". It sound very complex and noone can finally ensure it will be faster than linear scanning.

This was referenced Sep 11, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants