Examples
Examples
Try the starting example
- Cases [width mm,depth mm,segregation code]; enter JSON
- [[300,400,"A"],[400,400,"B"],[300,400,"A"]]
- Slots [width mm,depth mm,allowed segregation code]; enter JSON
- [[350,450,"A"],[450,450,"B"]]
- Case-slot allocation (JSON)
- [1,2,null]
- Unallocated cases (count)
- 1
Try another scenario
- Cases [width mm,depth mm,segregation code]; enter JSON
- [[350,400,"A"],[400,450,"B"]]
- Slots [width mm,depth mm,allowed segregation code]; enter JSON
- [[400,450,"A"],[450,450,"A"]]
- Case-slot allocation (JSON)
- [1,null]
- Unallocated cases (count)
- 1
Calculation method
Calculation method
Case-slot allocation (JSON)
Maximum-cardinality matching using compatible dimensions and exact segregation code.
Unallocated cases (count)
Count unmatched case requests.
Symbols and units
- a
- Cases [width mm,depth mm,segregation code]; enter JSON
- b
- Slots [width mm,depth mm,allowed segregation code]; enter JSON
Use the units shown. A list keeps the order in which you enter its values. The symbol ^ means “raised to the power of”.
Assumptions & limits
Assumptions & limits
- One case per rack slot; horizontal 90-degree rotation allowed, exact user segregation code matching. No thermal performance or rack-rating assessment. Supported limits: All numeric inputs and computed intermediates must remain finite. Supported numeric input magnitude is zero or 1e-12 through 1e12 in absolute value; reject values outside this bounded range. All lists/JSON record tables are limited to 100 records unless a stricter bound is stated; reject malformed record arity and wrong member types. Positive dimensions; <=50 cases and slots; depth/height/load constraints must already be reflected in user slot inventory.
Are these inputs private?
These calculations run in your browser. A shared link contains the values you choose to share. Only questions submitted to the separate AI finder are sent to OpenAI.