Examples
Examples
Try the starting example
- Site allocations [site,allocation weight]; enter JSON
- [["A",10],["B",20],["C",10]]
- Route distance (km)
- 80
- Measured fuel use (litres/100km)
- 8
- Fuel price (USD/litre)
- 1.5
- Total route fuel cost (USD)
- $9.60
- Site fuel allocations (JSON) (USD)
- [["A",2.4],["B",4.8],["C",2.4]]
Try another scenario
- Site allocations [site,allocation weight]; enter JSON
- [["A",15],["B",25],["C",10]]
- Route distance (km)
- 100
- Measured fuel use (litres/100km)
- 9
- Fuel price (USD/litre)
- 1.6
- Total route fuel cost (USD)
- $14.40
- Site fuel allocations (JSON) (USD)
- [["A",4.32],["B",7.2],["C",2.88]]
Calculation method
Calculation method
Total route fuel cost (USD)
Distance×litres/100km×price/100.
Site fuel allocations (JSON) (USD)
Use weighted shares of rounded route cost; largest-remainder integer-cent allocation reconciles exactly.
Symbols and units
- a
- Site allocations [site,allocation weight]; enter JSON
- b
- Route distance (km)
- c
- Measured fuel use (litres/100km)
- d
- Fuel price (USD/litre)
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
- Fuel expense allocated in proportion to user-assigned route-leg site weights; weights may represent distance or another entered policy. 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. Nonnegative weights with positive sum; positive/zero measured route values; allocation policy must be user-selected.
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.