Difference between revisions of "Tools/Trip"

From Sumo
Jump to navigation Jump to search
(help on using vehicle classes)
(explained using weight files)
Line 1: Line 1:
 +
__FORCETOC__
 
=randomTrips.py=
 
=randomTrips.py=
 
"randomTrips.py" generates a set of random trips for a given network (option "-n"). It does so by choosing source and destination edge either uniformly at random or weighted by length (option "-l"), by number of lanes (option "-L") or both. The resulting trips are stored in an xml file (option "-o", default trips.trips.xml) suitable for the [[DUAROUTER]] which is called automatically if the "-r" option (with a filename for the resulting route file) is given. The trips are distributed evenly in an interval defined by begin (option "-b", default 0) and end time (option "-e", default 3600) in seconds.
 
"randomTrips.py" generates a set of random trips for a given network (option "-n"). It does so by choosing source and destination edge either uniformly at random or weighted by length (option "-l"), by number of lanes (option "-L") or both. The resulting trips are stored in an xml file (option "-o", default trips.trips.xml) suitable for the [[DUAROUTER]] which is called automatically if the "-r" option (with a filename for the resulting route file) is given. The trips are distributed evenly in an interval defined by begin (option "-b", default 0) and end time (option "-e", default 3600) in seconds.
Line 26: Line 27:
  
 
Note the use of the option {{Option|--vclass}} which ensures that random start- and arrival-edges allow a specific vehicle class.
 
Note the use of the option {{Option|--vclass}} which ensures that random start- and arrival-edges allow a specific vehicle class.
 +
 +
==customized weights==
 +
Using option {{Option|weights-output-prefix foo}} will cause three files (''foo.src.xml, foo.dst.xml, foo.via.xml'') to be generated  which contain the used edge probabilities. Any of these files can be loaded in [[SUMO-GUI]] for visualization, i.e. using the options {{Option|--weight-file ''foo.src.xml''}} {{Option|--weight-attribute ''value''}}. In [[SUMO-GUI]] lane-coloring ''by loaded weight'' must be selected to make the data visible.
 +
 +
Files in this format can be loaded to specify explicit edge probabilities for being a source/destination/via edge.
 +
To obtain trips from a specific location to random destinations you may provide a modified .src.xml file which only contains a value for the desired start location. Then load that file using the option {{Option|--weights-prefix ''foo.src.xml''}}
 +
 +
When loading weights, missing edges will default to probability 0 and missing files (i.e. missing ''foo.dst.xml'') will default to normal randomization.
 +
  
 
=route2trips.py=
 
=route2trips.py=
 
This script generates a trip file from a route file by stripping all route information except for start and end edge. It has a single parameter which is the route file and prints the trip file to stdout. Example:
 
This script generates a trip file from a route file by stripping all route information except for start and end edge. It has a single parameter which is the route file and prints the trip file to stdout. Example:
 
  {{SUMO}}/tools/trip/route2trips.py input_routes.rou.xml
 
  {{SUMO}}/tools/trip/route2trips.py input_routes.rou.xml

Revision as of 10:27, 30 June 2014

randomTrips.py

"randomTrips.py" generates a set of random trips for a given network (option "-n"). It does so by choosing source and destination edge either uniformly at random or weighted by length (option "-l"), by number of lanes (option "-L") or both. The resulting trips are stored in an xml file (option "-o", default trips.trips.xml) suitable for the DUAROUTER which is called automatically if the "-r" option (with a filename for the resulting route file) is given. The trips are distributed evenly in an interval defined by begin (option "-b", default 0) and end time (option "-e", default 3600) in seconds. The number of trips is defined by the repetition rate (option "-p", default 1) in seconds. Every trip has an id consisting of a prefix (option "-t", default "t") and a running number. Example call:

<SUMO_HOME>/tools/trip/randomTrips.py -n input_net.net.xml -e 50 -l

The script does not check whether the chosen destination may be reached from the source. This task is performed by the router.

The option --min-distance <FLOAT> ensures a minimum straight-line distance (in meter) between start and end edges of a trip. The script will keep sampling from the edge distribution until enough trips with sufficient distance are found.

The option --fringe-factor <FLOAT> increases the probability that trips will start/end at the fringe of the network. If the value 10 is given, edges that have no successor or no predecessor will be 10 times more likely to be chosen as start- or endpoint of a trip. This is usefull when modelling through-traffic which starts and ends at the outside of the simulated area.

For additional ways to influence edge probabilities call

<SUMO_HOME>/tools/trip/randomTrips.py --help

generating vehicles with additional parameters

With the option --trip-parameters <STRING>, additional parameters can be given to the generated vehicles (note, usage of the quoting characters).

 <SUMO_HOME>/tools/trip/randomTrips.py -n input_net.net.xml --trip-parameters="departLane=\"best\" departSpeed=\"max\" departPos=\"random\""

This would make the random vehicles be distributed randomly on their starting edges and inserted with high speed on a reasonable lane.

If the generated vehicles should have a specific vehicle type, an additional-file needs to be prepared:

<additional>
  <vType id="myType" maxSpeed="27" vClass="passenger"/>
</additional>

Then load this file (assume it was saved as type.add.xml) with the option --additional-file

<SUMO_HOME>/tools/trip/randomTrips.py -n input_net.net.xml --trip-parameters="type=\"myType\"" --additional-file type.add.xml 
   --vclass passenger

Note the use of the option --vclass which ensures that random start- and arrival-edges allow a specific vehicle class.

customized weights

Using option weights-output-prefix foo will cause three files (foo.src.xml, foo.dst.xml, foo.via.xml) to be generated which contain the used edge probabilities. Any of these files can be loaded in SUMO-GUI for visualization, i.e. using the options --weight-file foo.src.xml --weight-attribute value. In SUMO-GUI lane-coloring by loaded weight must be selected to make the data visible.

Files in this format can be loaded to specify explicit edge probabilities for being a source/destination/via edge. To obtain trips from a specific location to random destinations you may provide a modified .src.xml file which only contains a value for the desired start location. Then load that file using the option --weights-prefix foo.src.xml

When loading weights, missing edges will default to probability 0 and missing files (i.e. missing foo.dst.xml) will default to normal randomization.


route2trips.py

This script generates a trip file from a route file by stripping all route information except for start and end edge. It has a single parameter which is the route file and prints the trip file to stdout. Example:

<SUMO_HOME>/tools/trip/route2trips.py input_routes.rou.xml