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

Optimize fast movement in vectorized job #305

Merged
merged 1 commit into from
Mar 19, 2018
Merged

Optimize fast movement in vectorized job #305

merged 1 commit into from
Mar 19, 2018

Conversation

HomineLudens
Copy link
Contributor

This should optimize travel distance when executing
quite extreme example:

10 minutes
image

to
4 minutes
image

I'm using VS2017 and to avoid upgrading the solution I've made all changes by hand (designer and resx files). So I've not modified the resources files for multi-language, that should be easy to fix.

Also the name for the option is ambiguous with other "optimizations"

image

please feel free to refactor the way you prefer

@arkypita arkypita merged commit 1840712 into arkypita:master Mar 19, 2018
@arkypita
Copy link
Owner

I really like your submit!

@arkypita
Copy link
Owner

Look like it doesn't work if you have only one path. Fixed adding

private List<List<CsPotrace.Curve>> OptimizePaths(List<List<CsPotrace.Curve>> list)
{
    if (list.Count == 1) return list; //mange single path
    [...]
}

@arkypita
Copy link
Owner

arkypita commented Mar 19, 2018

Benchmarking your algorithm I see that can really speed up engraving, but at cost of waiting some minutes to optimization computing. Optimizing the attached image (2200 point/path) require more than 2 minutes:

c8a3387e38465e99432eeb5e0e4de231

Could be some way to speed up the computation?

@arkypita
Copy link
Owner

i.e using this algorithm that look faster: http://parano.github.io/GeneticAlgorithm-TSP/

@HomineLudens
Copy link
Contributor Author

HomineLudens commented Mar 20, 2018 via email

@HomineLudens HomineLudens deleted the OptimizeFast branch October 23, 2018 17:25
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

Successfully merging this pull request may close these issues.

2 participants