optimize brute-force about cutsolver HOT 5 CLOSED

Performance improvements are not needed as long as this image has all the time in the world.

from cutsolver.

stock == length -> add to result and skip (ignoring cut width?)

from cutsolver.

Can't simply look for whole lenghts:

stock = 300
lengths: [100, 100, 100, 200, 200, 200]

trivial is 3x100, but that leaves 300 scrap; 100 + 200 gives perfect result

from cutsolver.

Might also want to remove gapfill while testing around

from cutsolver.

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

from cutsolver.