This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
|
en:sidebar:remoteapi:apiref:order:optimize [07/05/2020 14:01] shmi [Optimize order execution] |
en:sidebar:remoteapi:apiref:order:optimize [07/05/2020 14:02] (current) shmi [Parameters] |
||
|---|---|---|---|
| Line 61: | Line 61: | ||
| | priority | order of orders: {unit index:{order index:expected index of order in a route}} (index equal to -1 will fix this order as last in a route)| | | priority | order of orders: {unit index:{order index:expected index of order in a route}} (index equal to -1 will fix this order as last in a route)| | ||
| | criterions | route completion criterions: \\ max_mileage - maximum mileage, m;\\ max_duration - maximum duration, sec;\\ max_order_count - maximum orders count;\\ max_idling - maximum idle time between orders, sec;\\ split_intervals - if 1, then split based on intervals \\ (if the execution time of the order with unloading and moving, misses the next order time interval) | | | criterions | route completion criterions: \\ max_mileage - maximum mileage, m;\\ max_duration - maximum duration, sec;\\ max_order_count - maximum orders count;\\ max_idling - maximum idle time between orders, sec;\\ split_intervals - if 1, then split based on intervals \\ (if the execution time of the order with unloading and moving, misses the next order time interval) | | ||
| - | | preference | order priority in route | | + | | preference | DEPRECATED: order priority in route | |
| :!: JSON format is the same as in [[update]] request. | :!: JSON format is the same as in [[update]] request. | ||
|
