Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

In order to simulate the multiple vehicle (mode) types on the network, minimally one need to:

  • set the allowed modes for each link in the network file
  • set the leg mode for each trip in the plans file
  • set the available vehicle types (for e.g. car, bicycle) and also set the vehicle id for each person in vehicles file
  • tell mobility simulation (currently only for "qsim") about main modes, and link dynamics (for e.g. FIFO, PassingQ...)
  • inform the router about network modes

In the following, these are further explained. 


Network

A list of available (allowed) modes for each link can be set as follows. The list of allowed modes could be different for different links. 

...
  <link id="1" from="1" to="2" length="10000.00" capacity="36000" freespeed="27.78" permlanes="1" modes="car,bicycle" />
<link id="2" from="2" to="3" length="10000.00" capacity="3600" freespeed="27.78" permlanes="1" modes="car,bicycle" />
...

Plans

Assign a leg mode between each pair of activities. Different modes can be set for different trips of a person.

...
<person id="1">
<plan>
<act type="h" x="-25000" y="0" link="1" end_time="06:00" />
<leg mode="car"> </leg>
<act type="w" x="10000" y="0" link="20" dur="00:10" />
<leg mode="car"> </leg>
<act type="h" x="-25000" y="0" link="1" />
</plan>
</person>

<person id="6">
<plan>
<act type="h" x="-25000" y="0" link="1" end_time="06:00" />
<leg mode="bicycle"> </leg>
<act type="w" x="10000" y="0" link="20" dur="00:30" />
<leg mode="bicycle"> </leg>
<act type="h" x="-25000" y="0" link="1" />
</plan>
</person>
...

Vehicles

This is an additional input required for mixed traffic conditions. Minimally, the maximum speed and passenger car equivalents (PCE) of a vehicle, and vehicle type for each person are set in this file.

...
<vehicleType id="car">
  <maximumVelocity meterPerSecond="16.67"/>
  <passengerCarEquivalents pce="1.0"/>
  ...
 </vehicleType>
 
<vehicleType id="bicycle">
  <maximumVelocity meterPerSecond="4.17"/>
  <passengerCarEquivalents pce="0.25"/>
  ...
 </vehicleType>

...
<vehicle id="1" type="car"/>
<vehicle id="6" type="bicycle"/>
...

Configuration

For the mixed traffic conditions, the mobility simulation (currently only "qsim") needs to be informed about the main modes, source of vehicle, link dynamics (FIFO, PassingQ, SeepageQ) and traffic dynamics (queue, withHoles).

<module name="qsim">
   ...
  <param name="vehiclesSource" value="fromVehiclesData" />
  <param name="mainMode" value="car,bicycle" />
  <param name="linkDynamics" value="PassingQ" />
  <param name="trafficDynamics" value="queue" />
</module>

 Main modes are physically simulated on the network, thus router needs to be informed about these modes as follows. 

<module name="planscalcroute" >
   ...
  <param name="networkModes" value="car,bicycle" />
</module>



In addition to the above, network router needs a travel time and travel disutility calculator for all network modes other than car. This can be set as follows. One can set own travel time calculator and travel disutility factors.

...
controler.addOverridingModule(new AbstractModule() {
   @Override
   public void install() {
     addTravelTimeBinding("bicycle").to(networkTravelTime());
     addTravelDisutilityFactoryBinding("bicycle").to(carTravelDisutilityFactoryKey());
   }
});


For illustration, minimal inputs files for "equil-network" are created, which are available matsim/examples/equil-mixedTraffic.

  • No labels