Repository navigation
Packvium 1.6.0
Boxes cut to measure, flat bags, stacking groups and a volume-first objective in the request.
A request that uses none of them keeps its meaning; fast and balanced may now answer better.
Added
made_to_measureon a container: an on-demand box machine (largest box, minimum, cut
step, board price and weight per m²); each packed box is the load's extent rounded up onto
the machine grid and priced as cut, reported withachieved_dimensions.deformable_boundary: {kind: 'flat_bag'}on a container: a poly mailer that admits a load
when length plus thickness and width plus thickness fit.stacking_groupandaccepts_stacking_groupson an item: which classes may rest directly
on which.objective: 'maximum_volume', ranking the volume left behind ahead of the piece count.- A warning for items resting on nothing when
minimum_support_ratiois 0. No answer
changes. TypeScript types cover every new field.
Changed
- An unpacked item names the limit that left it out, the same in every engine.
Where the search used to fall back tono_feasible_placementorsearch_exhausted, an item a
fresh container would take but none is left reportscontainer_inventory_exhausted, and one
that overloads an axle wherever it stands alone reportsaxle_overloaded; both are
inferred. Code that matched the old reason for these cases must match the new one. balancedandqualitytry eight orderings by default, as the other engines
do;multi_start_ordersdefaulted to 1. Answers can improve, and these profiles take longer:
on our benchmarkbalanced2-25 times as long,quality1.7-2.8 times.fastkeeps one
ordering, and now ignores a largermulti_start_orders, as the other engines do. Set
multi_start_orders: 1for the 1.5 speed. The candidate search allocates about 80% less, so
eight orderings peak within about 13% of the memory one ordering took in 1.5.0.- Equal-volume items are ordered longest edge first, then heavier first, as in the other engines
, and the layer start keeps its own order in every profile, soqualityno longer
packs a simple pallet/carton/drum load worse thanbalanced. qualityorders its beam by aconvex_hullitem's own solid, not its box, so
it no longer assumes a second wedge cannot fit when it can.- The container plan counts a
convex_hullitem by its own solid too, so
qualityno longer ranks a plan as if wedges that share a container each needed their own. fastandbalancedadd the block solver as one more start on multi-type loads and keep
its answer only when strictly better.
Fixed
effort_budgetcaps the whole request, not each start. With several orderings or the
qualityportfolio every start got the full budget, somax_search_nodes: 5could spend 40.- A restart keeps item priority. A shuffled ordering could put a low-priority item ahead of
a high-priority one; it now keeps priority, value undermaximum_valueand stop order first. - Exact search with a
convex_hullitem. It bounded a hull by its box volume: two wedges
that share one crate went into two, and a small order with a jar spent most of its time limit.
It now finishes in a handful of search nodes.