Examples
Examples
Try the starting example
- Allowed zero-based fully suitable session indices per visitor; enter JSON
- [[0],[0,1],[1]]
- Available accommodation places per session (counts)
- 1,2
- Session booking matches (JSON)
- [1,2,2]
- Visitors lacking a suitable place (count)
- 0
Try another scenario
- Allowed zero-based fully suitable session indices per visitor; enter JSON
- [[0],[0],[1],[1]]
- Available accommodation places per session (counts)
- 1,2
- Session booking matches (JSON)
- [1,null,2,2]
- Visitors lacking a suitable place (count)
- 1
Calculation method
Calculation method
Session booking matches (JSON)
Maximum-cardinality matching on supplied fully suitable session edges.
Visitors lacking a suitable place (count)
Count unmatched requests.
Symbols and units
- a
- Allowed zero-based fully suitable session indices per visitor; enter JSON
- b
- Available accommodation places per session (counts)
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
- Accommodation compatibility is user-provided; each request consumes one fixed session place, with no medical or accessibility certification. 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. At most 100 requests/places; compatible indices valid; user verifies every required resource before listing an allowed edge.
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.