-
Notifications
You must be signed in to change notification settings - Fork 6
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 brute-force #6
Comments
Performance improvements are not needed as long as this image has all the time in the world. |
stock == length -> add to result and skip (ignoring cut width?) |
Can't simply look for whole lenghts: stock = 300 trivial is 3x100, but that leaves 300 scrap; 100 + 200 gives perfect result |
Might also want to remove gapfill while testing around |
Even the trivial solutions will have consequences, even simple optimizations can lead to imperfect results (see above). The only optimisation is to have preferred solutions when dealing with equal results, but there is little to gain there |
brute-forcing could be improved significantly by ignoring duplicates (like 4x200mm)
The text was updated successfully, but these errors were encountered: