Skip to content

Packvium 1.9.0

Choose a tag to compare

@github-actions github-actions released this 01 Nov 19:19
· 2 commits to main since this release
f58d145

A rebuild on the 1.9.0 Rust core: the centre of gravity is checked, and answers agree with the
other engines where 1.8 found them apart.

Changed

  • Under a clearance a compressible item bears its load on its own footprint, so its crush
    check is stricter and validate measures its own compressed volume.
  • Breaking for weights past 2^53 - 1 ticks: a weight's ticks, and a shipping_cost
    score position, are a BigInt past it, so JSON.stringify refuses such a result; the new
    stringifyExact and parseExact carry it through JSON exactly. Below it nothing changes.
  • A weight is at most 2^63 - 1 ticks, 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 past 2^53 - 1 is invalid_value and must be a string.
  • The centre of gravity is checked under a minimum_support_ratio above 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 past 2^53 - 1 ticks or
    a box past 10^30 cubic ticks is invalid_request / above_maximum; a side that reads as zero
    ticks is invalid_value / must be positive; an obstacle box outside its container is
    invalid_value / lies outside inner_dimensions, each at its own pointer.
  • validate checks 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.
  • Accepts null obstacle coordinates as zero, including additional boxes,
    consistently with request admission.