Repository navigation
Packvium 1.8.0
Results now say how far they can be from the best possible answer, Optimal means a proof,
and a mistyped flag is refused instead of defaulted.
Added
optimality.lower_boundand the gap under thedefaultandlowest_costobjectives,
withbounds::for_request,from_items,statementandStatement;validate_json
checks them.
Changed
- Only attaining the bound sets
Optimal; a registry solver'sOptimalis demoted to
Feasiblefirst. - An effort budget names a stop: a run that ends on exactly its budget is
complete. - A non-boolean
keep_upright,stackable,must_be_on_flooror
require_placement_coordinatesisinvalid_request/wrong_type; it was read as the
field's default.
validate_jsonreturnsMalformedResult(contract) for such a request, and readsnullas
the default. - Faster with identical answers: loading-order checks about 3x,
exact_smallabout 2x on
larger requests (the preflight answer is reused instead of solved twice), axle-limited solves
up to 25%,rebalance_weightabout 18%.
Fixed
homogeneous_blocksnamed alone packs underfastandbalanced; it stopped before
its first block and placed nothing.validatereadsunits: nullandunits.length: nullas millimetres, as the engines do,
and refuses aunitsthat is not an object, or an unknownunits.length, as acontract
MalformedResultnaming the field.units.weightis not a field and is ignored: put the unit
on each weight.