Demand/Automatic Routing

From Sumo
Revision as of 08:07, 3 May 2010 by Behrisch (talk | contribs) (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…')
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

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