Difference between revisions of "Demand/Automatic Routing"

From Sumo
Jump to navigation Jump to search
(Created page with 'There is another approach to vezhicle routing which may be adequate in the following situations: * there is not enough time / computing power to wait for the dynamic user equili…')
 
Line 1: Line 1:
 
There is another approach to vezhicle routing which may be adequate in the following situations:
 
There is another approach to vezhicle routing which may be adequate in the following situations:
* there is not enough time / computing power to wait for the dynamic user equilibrium
+
* there is not enough time / computing power to wait for the dynamic user equilibrium
* changes to the net occur while the simulation is running
+
* changes to the net occur while the simulation is running
* vehicles need to adapt their route while running
+
* vehicles need to adapt their route while running
  
 
In this case [[SUMO]] may be used directly for routing with either routes or trip files (or a mix) as input.
 
In this case [[SUMO]] may be used directly for routing with either routes or trip files (or a mix) as input.
Line 18: Line 18:
 
| valign="top" | {{Option|--device.routing.knownveh {{DT_String}}}}
 
| valign="top" | {{Option|--device.routing.knownveh {{DT_String}}}}
 
|  
 
|  
| valign="top" |       Assign a device to named vehicles
+
| valign="top" | Assign a device to named vehicles
 
|-
 
|-
 
| valign="top" | {{Option|--device.routing.deterministic}}
 
| valign="top" | {{Option|--device.routing.deterministic}}
 
|  
 
|  
| valign="top" |     The devices are set deterministic using a fraction of 1000
+
| valign="top" | The devices are set deterministic using a fraction of 1000
 
|-
 
|-
 
| valign="top" | {{Option|--device.routing.period {{DT_String}}}}
 
| valign="top" | {{Option|--device.routing.period {{DT_String}}}}
 
|  
 
|  
| valign="top" |         The period with which the vehicle shall be rerouted
+
| valign="top" | The period with which the vehicle shall be rerouted
 
|-
 
|-
 
| valign="top" | {{Option|--device.routing.pre-period {{DT_String}}}}
 
| valign="top" | {{Option|--device.routing.pre-period {{DT_String}}}}
 
|  
 
|  
| valign="top" |     The rerouting period before emit
+
| valign="top" | The rerouting period before emit
 
|-
 
|-
 
| valign="top" | {{Option|--device.routing.adaptation-weight {{DT_Float}}}}
 
| valign="top" | {{Option|--device.routing.adaptation-weight {{DT_Float}}}}
Line 42: Line 42:
 
| valign="top" | {{Option|--device.routing.with-taz}}
 
| valign="top" | {{Option|--device.routing.with-taz}}
 
|  
 
|  
| valign="top" |           Use zones (districts) as routing end points
+
| valign="top" | Use zones (districts) as routing end points
 
|-
 
|-
 
|}
 
|}
 +
If the routing is enabled for selected vehicles (either with the ".probability" or the ".knownveh" option), the average travel times in the net are collected for all edges. If a vehicle needs to be routed (either because it gets inserted or because a repeated route choice was enabled via the ".period" option) it chooses the shortest route to its destination edge (or district) according to the present edge weights (travel times). The update of the edge weights does not simply overwrite the old value but gives it a certain weight which may be modified with the ".adaption-weight" option. Since updating the weights of all edges in each simulation step means a major slowdown for the simulation this interval may be altered using the ".adaption-interval" option.

Revision as of 08:15, 3 May 2010

There is another approach to vezhicle routing which may be adequate in the following situations:

  • there is not enough time / computing power to wait for the dynamic user equilibrium
  • changes to the net occur while the simulation is running
  • vehicles need to adapt their route while running

In this case SUMO may be used directly for routing with either routes or trip files (or a mix) as input. The options related to this routing are:

Option Mandatory y/n Description
--device.routing.probability <FLOAT> The probability for a vehicle to have a routing device
--device.routing.knownveh <STRING> Assign a device to named vehicles
--device.routing.deterministic The devices are set deterministic using a fraction of 1000
--device.routing.period <STRING> The period with which the vehicle shall be rerouted
--device.routing.pre-period <STRING> The rerouting period before emit
--device.routing.adaptation-weight <FLOAT> The weight of prior edge weights.
--device.routing.adaptation-interval <STRING> The interval for updating the edge weights.
--device.routing.with-taz Use zones (districts) as routing end points

If the routing is enabled for selected vehicles (either with the ".probability" or the ".knownveh" option), the average travel times in the net are collected for all edges. If a vehicle needs to be routed (either because it gets inserted or because a repeated route choice was enabled via the ".period" option) it chooses the shortest route to its destination edge (or district) according to the present edge weights (travel times). The update of the edge weights does not simply overwrite the old value but gives it a certain weight which may be modified with the ".adaption-weight" option. Since updating the weights of all edges in each simulation step means a major slowdown for the simulation this interval may be altered using the ".adaption-interval" option.