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 guessed.
Added
optimality.lower_boundand the gap under thedefaultandlowest_costobjectives.
packvium.validatechecks them;packvium.result_validation.objective_lower_bound(request)
computes the bound.
Changed
- Attaining the bound, not search exhaustion, sets
optimal(proven_optimal). - An effort budget names a stop: a run that ends on exactly its budget is
complete, and
time_limit_msis no longer split across starts. Checktermination.any_start_truncated. keep_upright,stackable,must_be_on_floorandrequire_placement_coordinatesmust
be booleans."no"or1isinvalid_request/wrong_type;ItemandPackingConfig
refuse it when built.
validaterefuses such a request asMalformedResultnaming the field, and readsnullas
the default.- Faster, identical answers: loading-order check about 30%,
validateabout 20%. - Each measure is parsed once per request: the request check hands its parsed values to
deserialisation, whether a measure is written as a string, a number or a{value, unit}object.
The measured macOS unpackable-request paired wall-time median improved about 8%. - Placement under axle limits is about 4x faster: each candidate's axle check is O(1).
Fixed
solvers=["homogeneous_blocks"]packs underfastandbalanced, and a node-limit
stop is no longer reported astime_limit.units.length: nullandoutput.*_unit: nullmean the default instead of raising
AttributeError;Length.of/Weight.ofrefuse a unit that is not a string asinvalid_unit.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.