Skip to content

Packer seems to prefer long-narrow boxes? #645

Description

@MarkBFamFour

Hi,

I have a range of different sizes of box defined that are the most common fit for our carriage system.

For each "cost band" we have 3 sizes ranging from a squarer footprint (length * width), say 800x400x400mm to a long footprint, say 1750x200x200mm. In general terms when packing BoxPacker seems to always choose a "long, thin" package size vs a "short, square" package size, even when the items would be better suited to the "short, squarer" box size, sometimes to some silly extremes where it's packing a set of items that are 1/3 the size of the box at one end, rather than picking a more appropriate box volume that I know they'd fit in.

This is a good example: https://boxpacker.io/en/stable/visualiser.html?packing=%7B%22items%22%3A%5B%5B%22FF003886_1%22%2C180%2C390%2C180%5D%2C%5B%22FF002180_1%22%2C100%2C150%2C80%5D%2C%5B%22FF002181_1%22%2C80%2C110%2C80%5D%2C%5B%22FF012622_1%22%2C80%2C90%2C50%5D%5D%2C%22boxes%22%3A%5B%5B%22Big+3%22%2C190%2C1740%2C190%2C%5B%5B0%2C0%2C0%2C0%2C180%2C390%2C180%2C2527%2C2527.2%2C%22V%22%5D%2C%5B0%2C0%2C390%2C0%2C180%2C390%2C180%2C2527%2C2527.2%2C%22V%22%5D%2C%5B1%2C0%2C780%2C0%2C100%2C80%2C150%2C2240%2C240%2C%22O%22%5D%2C%5B2%2C100%2C780%2C0%2C80%2C80%2C110%2C1110%2C140.8%2C%22O%22%5D%2C%5B3%2C0%2C860%2C0%2C90%2C50%2C80%2C450%2C72%2C%22O%22%5D%2C%5B3%2C0%2C860%2C80%2C90%2C50%2C80%2C450%2C72%2C%22O%22%5D%5D%5D%5D%7D

This example would pack easily into the 800x400x400 box but it's chosen a 1750x200x200 box instead.

Like this:
https://boxpacker.io/en/stable/visualiser.html?packing={"items"%3A[["FF003886_1"%2C180%2C390%2C180]%2C["FF002180_1"%2C100%2C150%2C80]%2C["FF002181_1"%2C80%2C110%2C80]%2C["FF012622_1"%2C80%2C90%2C50]]%2C"boxes"%3A[["Big+1"%2C390%2C790%2C390%2C[[0%2C0%2C0%2C0%2C180%2C390%2C180%2C2527%2C2527.2%2C"V"]%2C[0%2C180%2C0%2C0%2C180%2C390%2C180%2C2527%2C2527.2%2C"V"]%2C[1%2C0%2C390%2C0%2C150%2C80%2C100%2C2240%2C240%2C"O"]%2C[2%2C0%2C390%2C100%2C110%2C80%2C80%2C1110%2C140.8%2C"O"]%2C[3%2C150%2C390%2C0%2C90%2C50%2C80%2C450%2C72%2C"O"]%2C[3%2C150%2C390%2C80%2C90%2C50%2C80%2C450%2C72%2C"O"]]]]}

We can't use a single box for each cost band because we sell a very varied range of items and there is no "one size fits all" that fits in each costing.

Is there a way to customise this, or is it just the way the algorithm's best-fit?

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions