Browse files

updated info

  • Loading branch information...
treibi committed May 26, 2018
1 parent 08e92f7 commit ef25f28f52f3c37b51d405e18b89164ee1f3e483
Showing with 59 additions and 74 deletions.
  1. +5 −3 .gitignore
  2. +0 −39 README_floatcars
  3. +52 −2
  4. +0 −28 README_xprj_addtl
  5. +2 −2 sim/testing/Roundabout.xprj
@@ -3,8 +3,6 @@
@@ -37,4 +35,8 @@ int
# ignore intellij
# ignore tmp comments and mails

This file was deleted.

Oops, something went wrong.
@@ -173,6 +173,15 @@ derivative, see
- for each *AccelerationModelType*, the parameter can optionally vary
stochastically, see *TrafficComposition*
speed limits
Since speed limits are road network, and not vehicle-driver,
attribbutes, they are not defined in the car-following model block but
in the infrastructure (*.xodr*) file. The car-following models take
this info and decrease the models's desired speed (each model has one)
if it happens to be above the speed limit. See
defining the lane-changing models
@@ -399,13 +408,38 @@ or
These are given by the optional block *Routes* inside *Scenario*
These are given by the optional block *Routes* inside *Scenario* and
define routes as a sequence of connected links, i.e., *Road*s. In
the following example, two routes using the links 1,4, and the link 3,
are set up:
<Route label="route1">
<Road id="1" />
<Road id="4" />
<Route label="route2">
<Road id="3" />
An error is cast if the links are not connected.
- This can be used to implement traffic demands given by an OD matrix,
where each OD element uses a given (shortest) route
- see, e.g,. *sim/output/city_example.xprj*
- For output of vehicle trajectories, it is also necessary to define
routes as part of *OutputConfiguration* inside *Scenario*:
<Trajectories dt="1" route="route1" />
- Example: *sim/output/city_example.xprj*
Traffic lights
@@ -433,6 +467,22 @@ Given by the optional *OutputConfiguration* block inside *Scenario*
extension .csv (so can be easily removed since no input file has the
*.csv* ending)
- Examples of an output include *Trajectories* giving trajectories of
all vehicles on a specified route (see above) and
*FloatingCarOutput* giving xFCD for a defined set of vehicle indices
on defined routes (if you just wand the vehicles on a road segment,
just define a route with one segment). For example,
<FloatingCarOutput n_timestep="5" route="main">
<FloatingCar number="2" />
<FloatingCar number="11" />
will record Car 2 and Car 11 of the route/road segment "main" (notice
that the first car has the lowest index).

This file was deleted.

Oops, something went wrong.
@@ -91,8 +91,8 @@
<Inflow t="0" q_per_hour="200" v="13.89" />
<Route label="ws">
<Road id="2" />
<Road id="22" />

0 comments on commit ef25f28

Please sign in to comment.