Repository navigation
Packvium 1.9.0
The fallback now checks what the addon checks, spends an effort budget the same way and reports
its time.
Changed
- Under a clearance a compressible item bears its load on its own footprint, so its crush
check is stricter andvalidatemeasures its own compressed volume. - Breaking for weights past
2^53 - 1ticks: a weight'sticks, and ashipping_cost
score position, are aBigIntpast it, soJSON.stringifyrefuses such a result; the new
stringifyExactandparseExactcarry it through JSON exactly. Below it nothing changes. - A weight is at most
2^63 - 1ticks, and so is every item's weight times its quantity plus
the heaviest tare: past it,invalid_request/above_maximum; a weight written as a JSON
number past2^53 - 1isinvalid_valueand must be a string. - The centre of gravity is checked under a
minimum_support_ratioabove 0: a placement
covering at most half its base with the centroid outside the contact hull is refused.
A request without a ratio packs as before. - Agrees with the other engines where 1.8 did not: nesting under a clearance shares the
items' own overlap and a deep nesting column nests in pairs; a length past2^53 - 1ticks or
a box past10^30cubic ticks isinvalid_request/above_maximum; a side that reads as zero
ticks isinvalid_value/must be positive; an obstacle box outside its container is
invalid_value/lies outside inner_dimensions, each at its own pointer. validatechecks the centroid (centre_of_gravity_unsupported) and the whole stack's load
(top_load_exceeded), an item on several bearers shared by contact area. It no longer
holds that item's whole weight against every bearer, so it accepts some results 1.8 rejected
and names the overloaded bearer.- A plan beam wider than 1 compares every container type, whatever the node limit.
- The JavaScript fallback spends
effort_budgetas the other engines do, and itsquality
beam refines its best order once instead of its first two: about 1.6x faster, no score changed. algorithm.duration_msreports the milliseconds the fallback took; it was always 0.- The native backend accepts null obstacle coordinates as zero, including additional boxes,
consistently with request admission.
Fixed
- The fallback no longer slides an item under a
ground_contact_rule: singleitem that already
rests on one supporter.