Difference between revisions of "Simulation/Output/FullOutput"

From Sumo
Jump to navigation Jump to search
(Notes)
Line 1: Line 1:
 
The idea behind this option is to improve the capabilities of the existing netstate-dump option.
 
The idea behind this option is to improve the capabilities of the existing netstate-dump option.
 
The produced XML Structure contains information about the edges, lanes, vehicles and traffic lights. The intention for this option was to  
 
The produced XML Structure contains information about the edges, lanes, vehicles and traffic lights. The intention for this option was to  
check the simulation results without having recorded all the simulation commands e.g. traci.  
+
check the simulation results without having to record all the simulation commands e.g. traci.  
  
 
==Instantiating within the Simulation==
 
==Instantiating within the Simulation==
To force SUMO to build a file that contains the full dump, extend your command line parameter by {{Option|--full-output {{DT_FILE}}}}. {{DT_FILE}} is hereby the name of the file the output will be written to. Any other file with this name will be overwritten, the destination folder must exist.
+
To force SUMO to build a file that contains the full dump, extend your command line parameter by {{Option|--full-output {{DT_FILE}}}}. {{DT_FILE}} is the name of the file the output will be written to. Any other file with this name will be overwritten, the destination folder must exist.
  
 
==Generated Output==
 
==Generated Output==
Line 120: Line 120:
 
| class="inlxml" | waiting
 
| class="inlxml" | waiting
 
| seconds
 
| seconds
| The total number of seconds a vehicle is waiting
+
| The total time a vehicle is waiting
 
|-
 
|-
 
| class="inlxml" | lane
 
| class="inlxml" | lane
Line 148: Line 148:
 
| class="inlxml" | traveltime
 
| class="inlxml" | traveltime
 
| seconds
 
| seconds
| The mean time of travel on the specific lane
+
| The mean travel time on the specific lane
 
|-
 
|-
 
| class="inlxml" | fuel@lane
 
| class="inlxml" | fuel@lane
Line 174: Line 174:
 
==Notes==
 
==Notes==
  
Equally to the raw dump this output is also verbose. The generated files will be very large, you may pipe this output directly to a compression tool like bzip2. The advantage of this large file is that you can write some nice XML Stylesheets to export everything whats important to you, for example the states of the traffic lights and the travelling times for the lanes.
+
The generated files will be very large, you may pipe this output directly to a compression tool like bzip2. The advantage of this large file is that you can write some nice XML Stylesheets to export everything what is important to you, for example the states of the traffic lights and the travel times for the lanes.

Revision as of 07:04, 15 June 2012

The idea behind this option is to improve the capabilities of the existing netstate-dump option. The produced XML Structure contains information about the edges, lanes, vehicles and traffic lights. The intention for this option was to check the simulation results without having to record all the simulation commands e.g. traci.

Instantiating within the Simulation

To force SUMO to build a file that contains the full dump, extend your command line parameter by --full-output <FILE>. <FILE> is the name of the file the output will be written to. Any other file with this name will be overwritten, the destination folder must exist.

Generated Output

The full dump is a xml-file containing informtation about every edge, lane, vehicle and traffic light for each time step. A full dump-file looks like this:

<full-export>
   <data timestep="<TIME_STEP>">
     
    <vehicles>
      <vehicle id="<VEHICLE_ID>" eclass="<VEHICLE_ECLASS>" co2="<VEHICLE_CO2>" co="<VEHICLE_CO>" hc="<VEHICLE_HC>" 
      nox="<VEHICLE_NOX>" pmx="<VEHICLE_PMX>" noise="<VEHICLE_NOISE>" route="<VEHICLE_ROUTE>" type="<VEHICLE_TYPE>" 
      waiting="<VEHICLE_WAITING>" lane="<VEHICLE_LANE>" pos_lane="<VEHICLE_POS_LANE>" speed="<VEHICLE_SPEED>" 
      angle="<VEHICLE_ANGLE>" x="<VEHICLE_POS_X>" y="<VEHICLE_POS_Y>"/>
    
        ... more vehicles ...
 
    </vehicles>

   <edges>
     
      <edge id="<EDGE_ID>" traveltime="<EDGE_TRAVELTIME>">
       
       <lane id="<LANE_ID>" co="<LANE_CO>" co2="<LANE_CO2>" nox="<LANE_NOX>" pmx="<LANE_CO>" 
       hc="<LANE_HC>" noise="<LANE_NOISE>" fuel="<LANE_FUEL>" maxspeed="<LANE_MAXSPEED>" meanspeed="<LANE_MEANSPEED>" 
       occupancy="<LANE_OCCUPANCY>" vehicle_count="<LANE_VEHICLES_COUNT>"/>

            ... more lanes of the edge if exists

      </edge>
      
            ... more edges of the network

   </edges>

</data>

... the next timestep ...

</full-export>

The meanings of the written values are given in the following table.

Name Type Description
time_step (simulation) seconds The time step described by the values within this timestep-element
id id The id of the vehicle/lane/edge
eclass id The id of the specific emission class of the vehicle
co2@vehicle mg/s The amount of CO2 emitted by the vehicle in the actual simulation step
co2@lane mg/s The complete amount of CO2 emitted by the vehicles on this lane during the actual simulation step
co@vehicle mg/s The amount of CO emitted by the vehicle in the actual simulation step
co@lane mg/s The complete amount of CO emitted by the vehicles on this lane during the actual simulation step
hc@vehicle mg/s The amount of HC emitted by the vehicle in the actual simulation step
hc@lane mg/s The complete amount of HC emitted by the vehicles on this lane during the actual simulation step
nox@vehicle mg/s The amount of NOX emitted by the vehicle in the actual simulation step
nox@lane mg/s The complete amount of NOX emitted by the vehicles on this lane during the actual simulation step
pmx@vehicle mg/s The amount of PMX emitted by the vehicle in the actual simulation step
pmx@lane mg/s The complete amount of PMX emitted by the vehicles on this lane during the actual simulation step
noise@lane dB The noise emitted by the vehicles on the specific lane
route id The name of the route
type id The name of the vehicle type
waiting seconds The total time a vehicle is waiting
lane id The name of the lane
pos meters The position of the vehicle on a specific lane
speed km/h The actual speed of the vehicle
angle degree The angle of the vehicle
pos_x --- The absolut X coordinate of the vehicle. The value depends on the given geographic projection.
pos_y --- The absolut Y coordinate of the vehicle. The value depends on the given geographic projection
traveltime seconds The mean travel time on the specific lane
fuel@lane l/km/h The fuel consumption on the specific lane
maxspeed km/h The maximum speed of the vehicles on the specific lane
meanspeed km/h The mean speed of the vehicles on the specific lane
occupancy % The occupancy of the lane in %
vehicles_count #veh The number of vehicles on the lane

Notes

The generated files will be very large, you may pipe this output directly to a compression tool like bzip2. The advantage of this large file is that you can write some nice XML Stylesheets to export everything what is important to you, for example the states of the traffic lights and the travel times for the lanes.