ChangeLog

From Sumo
Jump to: navigation, search

Git master

Bugfixes

  • Simulation
    • All car-following models now respect the vType-attribute emergencyDecel as an absolute bound on deceleration. Issue #3556
    • Fixed collisions when using continous lane change. Issue #3769
    • Fixed back-and-forth changing when using continous lane change. Issue #4010
    • Fixed loading of teleporting vehicles from simulation state in .sbx format. Issue #3787
    • Fixed invalid vehicle counts by E2-detector related to lane-changing. Issue #3791
    • Fixed bug that was causing invalid slowdown while passing an intersection. Issue #3861
    • Fixed bug that was causing pedestrians on looped routes to block themselves. Issue #3888
    • Vehicle speedFactor is now included in saved state. Issue #3881
    • Fixed invalid collision events when lanes are to narrow for the vehicles. Issue #3056
    • Fixed collision between pedestrians and vehicles. Issue #3964
    • Fixed bug where option --random-depart-offset would trigger invalid warnings regarding unsorted route file. Issue #4076
  • SUMO-GUI
    • width of railway edges is now taken into account when drawing (interpreted as gauge). Issue #3748
    • window-size and position now remain unchanged when reloading the simulation. Issue #3641
    • Random vehicle and person coloring is now more random on windows. Issue #3740
    • Vehicles that were not inserted (i.e. due to option --scale or --max-depart-delay) no longer count as arrived in the simulation parameter dialog. Instead the are counted under the new item discarded vehicles. Issue #3724
    • Fixed issues related to drawing smooth corners at curving roads. Issue #3840
    • Fixed vehicle positions when using the sublane model in lefthand networks. Issue #3923
    • Fixed crashing and visualization problems when using the 3D-view. Issue #4037, Issue #4039
  • NETEDIT
    • Splitting edges, deleting individual edges and lanes or adding lanes via the duplicate menu option no longer resets connections and traffic light plans. Issue #3742
    • The viewing area and zoom loaded via option --gui-settings-file is no longer ignored
    • Fixed bug where connections on large junctions did not register clicks or were not drawn. Issue #3726
    • Fixed crash when removing inspected object via undo. Issue #3781
    • Fixed various bugs that led to re-computation of signal plans when modifying connections or tls indices. Issue #3742, Issue #3832
    • Fixed bug that could lead to the creation of invalid networks when adding and removing connections. Issue #3824, Issue #3813
    • Custom connection shape is now longer lost after delete+undo. Issue #3822
    • Splitting edges no longer introduces unnecessary custom endpoints. Issue #3895
    • Fixed inverted interpretation of lanePosLat for POIs compared to SUMO-GUI. Issue #4002
  • NETCONVERT
  • DUAROUTER
  • POLYCONVERT
    • Fixed bug when importing OSM data with objects that are marked as deleted. Issue #3786
  • TraCI
    • Fixed bug where persons would "jump" when replacing the current walking stage with a new one. Issue #3744
    • Fixed crash when trying to access empty subscription result list using the C++ client.
    • Vehicle emergencyDecel is now at least as high as decel after calling traci.vehicle.setDecel. Issue #3755
    • Fixed python client bug in traci.polygon.setShape. Issue #3762
    • Adding a route with an empty list of edges now results in an error. Issue #3845
    • Vehicles that drive outside the road network under the control of moveToXY now properly updated their speed and brake lights. Issue #3837
    • Function vehicle.getLaneChangeMode now returns correct values for the original lane change state when the state is affected by vehicle.setLaneChangeMode. Issue #3810
    • Car-following related vehicle type parameters (e.g. accel) that are changed via traci are now correctly saved when saving simulation state. Issue #3522
    • When using context subscriptions around an object, that object itself is no longer included in the result. Issue #4088

Enhancements

  • All applications
    • All time values in options and xml inputs can now be specified in the format h:m:s and d:h:m:s (where the values for days, hours and minutes are all positive integers and seconds may also be a positive floating point number).
      Note:
      This does not apply to the python tools.
    • Added option --human-readable-time (short -H) that causes all time values to be written in h:m:s (or d:h:m:s) format.
  • Simulation
    • Tripinfo-output now includes the attribute stopTime which records the time spent with intentional stopping. Issue #3693
    • A pedestrian crossings can now have different signal states for both directions. Issue #3820
    • FCD-output can now be switched on selectively for a subset of vehicles and the reporting period can be configured. Issue #1910
    • Intended departure times (attribute depart) and intended vehicle id (attribute intended) are now added to vehroute-output of public transport rides. Issue #3948
    • Stopping place names are now added as XML-comments in vehroute-output of public transport rides. Issue #3952
    • Lane-Change-Model parameter lcTurnAlignmentDistance added for the control of dynamic alignment in simulations using the sublane model, see Lane-Changing Models, Issue #4025.
  • SUMO-GUI
    • Added option to disable drawing of bicycle lane markings on intersections.
    • All laneChangeModel-related vType-parameters and all junction-model related vType-parameters are now shown in the vType-Parameter dialog.
    • The simulation view can now be rotated via the new gui-settings attribute angle in the <viewport> or via the viewport dialog. Issue #3841
    • When drawing junction shapes with exaggerated size and setting option show lane-to-lane connections, the connecting lines are now scaled up at traffic light junctions. Issue #3796
    • The simulation state can now be saved via the Simulation Menu. Issue #2513
    • Object tracking can now be aborted via double-click.
    • Person plans can now be inspected via the right-click menu. Issue #3886
    • Object name rendering size can now be toggled between constant pixel size (all visible when zoomed out) and constant network size (invisible when zoomed out). Issue #3931
  • NETEDIT
    • Added virtual attribute to identify bidirectional rail edge pairs. Issue #3720
    • Added option to modify the visualisation of bidirectional rail edge pairs (spread superposed) Issue #3720
    • Added button add states to traffic light-mode to complement the functionality of cleanup states. Issue #3846
    • Netedit now flags connection targets with incompatible permissions as conflict and only creates them with <ctrl>+<click>. Issue #3823
    • Traffic light indices are now drawn for pedestrian crossings when enabled via gui settings. Issue #3814
    • Now ParkingAreas and ParkingSpaces can be created in netedit. Issue #3104
    • When adding a new phase to a traffic light, the new phase will now have a plausible successor state depending on the selected previous phase (rather the being a copy). Issue #4041
    • Added function 'split' to junction context menu. This can be used to disaggregated joined junctions. Issue #4046
  • NETCONVERT
    • Geo-referenced networks (i.e. from OSM) can now be merged by loading them together (-s net1.net.xml,net2.net.xml). Issue #4085
    • Element <crossing> now supports attribute linkIndex2 to specify a custom signal index for the reverse direction. Issue #3820
    • When defining double connections, the right-of-way rules now take the road topology into account to differentiate between on-ramp and off-ramp situations. Issue #3834
    • Importing VISUM networks up to format version 10 is now support. Issue #3898
    • Improved heuristics for options --junctions.join. Issue #876
    • Improved computation of intermodal junctions imported from OSM. Issue #4003
    • Added option --proj.rotate <FLOAT> for rotating the network.
    • Added option --prefix <STRING> which can be used to add a prefix to the written junction and edge IDs.
    • Added options --tls.scramble.time --tls.crossing-clearance.time --tls.crossing-min.time to control the timing of pedestrian crossing phases. Issue #4078
  • NETGENERATE
    • Simplified node and edge names
      • The alphanumerical junction naming scheme now supports arbitrary grid sizes (using ids like XY23)
      • The alphanumerical junction naming scheme also extends to spider networks
      • The alphanumerical junction naming scheme is active by default (the option for enabling the old scheme was renamed from grid.alphanumerical-ids to --alphanumerical-ids).
      • When using alphanumerical junction ids, the intermediate string to is omitted from edge names because the edge ID already allows unambiguous determination of its junctions without it
    • Added option --rand.random-lanenumber to randomize lane numbers in random networks between 1 and default.lanenumber
    • Added option --rand.random-priority to edge priorities in random networks between 1 and default.priority
    • Added option --rand.grid to place generated junctions on a regular grid
    • Added option --prefix <STRING> which can be used to add a prefix to the generated junction and edge IDs.
    • Corridor networks can now be generated by using options such as -g --grid.x-number 3 --grid.y-number 1 --grid.attach-length 100


  • DUAROUTER
    • Intended departure times (attribute depart) and intended vehicle id (attribute intended) are now added to vehroute-output of public transport rides. Issue #3948
    • Stopping place names are now added as XML-comments in route-output of public transport rides. Issue #3952


  • TraCI
    • function vehicle.add now supports using the empty string ("") as a route id to insert the vehicle on an arbitrary valid edge. This makes it easier to remote-control vehicles using moveToXY without defining an initial route. Issue #3722
    • added functions simulation.getCollidingVehiclesNumber and simulation.getCollidingVehiclesIDList to track collisions. Issue #3099
    • added function edge.getLaneNumber to retrieve the number of lanes of an edge. Issue #3630
  • Tools
    • sumolib now supports lane.getWidth(). Issue #3842
    • webWizard now correctly builds regions with left-hand traffic Issue #3928

Other

  • Simulation
    • tripinfo-output attribute waitSteps which counts the number of simulation steps in which the vehicle was below a threshold speed of 0.1m/s was replaced by attribute waitingTime which measures the same time in seconds. This gives results which are independent of the --step-length simulation parameter. Issue #3749
    • The default value for option --device.rerouting.pre-period was changed from 1 to 60 to speed up simulation. Issue #3865
  • Miscellaneous
    • The space character ' ' is no longer allowed in xml option values when separating file names. Instead the comma ',' must be used. Files with space in their path are now supported.
    • NETCONVERT no longer creates an offset of 0.1m between lanes. This means the total visual width of an edge is now the sum of all lane widths. This also fixes an inconsistency between visualization and simulation as the vehicles always ignored this offset anyway. Road markings are now drawn on top of the lanes rather than between them. This causes small visual gaps in old networks (fixable by calling netconvert -s old.net.xml -o new.net.xml). Issue #3972
  • TraCI
    • TraCI Version is now 18

Version 0.32.0 (19.12.2017)

Bugfixes

  • Simulation
    • Fixed collisions in the sublane model Issue #3446, Issue #3595, Issue #3613
    • Fixed bug that was causing invalid behavior in the sublane model when used with option --step-method.ballistic. Issue #3486
    • Fixed bug that was causing deadlocks after undercutting minimum gap. Issue #3486
    • Fixed bug that was causing deadlocks at intersections. Issue #3615
    • Option --ignore-route-errors now also applies to invalid (i.e. misordered) stop definitions. Issue #3441
    • PHEMlight handles large acceleration values better Issue #3390 and has updated emission values for new Diesel cars
    • <stop> definitions using attribute until that are used within a <flow> now shift the until times according to the offset between departure and flow begin. Issue #1514
    • <chargingStation> attribute chargeDelay now accepts floating point values.
    • <chargingStation> attribute chargeDelay now works with subsecond simulation.
    • Vehicles passing a minor link with impatience 0 no longer force braking for prioritized vehicles. Issue #3494
    • Fixed bug that was causing collisions between vehicles and pedestrians Issue #3527
    • Fixed slow simulation when combining cars and ships in one simulation. Issue #3528
    • Fixed collisions on junctions between vehicles coming from the same lane. Issue #1006,Issue #3536
    • Fixed failure to change lanes for speed gain in the sublane model. Issue #3582
    • Fixed collision of a vehicle with itself. Issue #3584
    • Several fixes in regard to intermodal routing. Issue #3613, Issue #3622, Issue #3560, Issue #3561, Issue #3562
  • SUMO-GUI
    • Fixed crash when simulating pedestrians. Issue #3484
    • Coloring by selection is now working for pedestrian crossings. Issue #3396
    • Options --window-size and --window-pos are now working when set in a configuration file. Issue #3406
    • Vehicle blinkers that signal left or right turns now remain switched on while the vehicle is still on the intersection (requires networks to be rebuilt). Issue #3478
    • Fixed invalid lane-change blinkers for near-zero lateral movements in the sublane model. Issue #3612
    • Fixed invalid vehicle angle when using the sublane model. Issue #3609
    • Networks created with simple projection can now be shown. Issue #3467
    • Fixed invalid duration factor in network parameters for sub-second simulation. Issue #3600
  • POLYCONVERT
    • Fixed handling of XML special characters when exporting arbitrary text via option --all-attributes. Issue #3447
  • NETCONVERT
    • Fixed crash when importing Vissim networks.
    • Fixed bug that was causing invalid signal plans when loading a .net.xml file and removing edges from an intersection with pedestrian crossings (the link indices for crossings were re-assigned but the signal plan was left unmodified creating a mismatch).
    • No longer writing pedestrian crossings with length 0 (minimum length is 0.1m).
    • Parameters (i.e. those for actuated traffic lights) are no longer lost when importing .net.xml files or plain-xml files. Issue #3343
    • Fixed bug that was causing invalid networks to be generated when additional lanes were placed to the right of a sidewalk. Issue #3503
    • Fixed bug that was causing invalid networks to be generated when nodes without connections were part of a joined traffic light Issue #3715
    • Defining pedestrian crossings for Pedestrian Scramble is now supported. Issue #3518
    • Custom traffic light plans for pedestrian crossings are no longer modified. Issue #3534
    • Fixed invalid traffic light plans at pedestrian crossings for node type traffic_light_right_on_red. Issue #3535
    • Fixed invalid right of way rules at node type traffic_light_right_on_red that could cause deadlock. Issue #3538
    • Networks with intersections that are very close to each other can now be re-imported. Issue #3585
    • Edges that do not have connections are now correctly represented in plain-xml output. Issue #3589
    • Fixed invalid geometry in opendrive-output for lefthand networks. Issue #3678
    • Fixed invalid road markings in opendrive-output.
  • NETEDIT
    • Fixed bug that was causing pedestrian crossings to remain uncontrolled at traffic light controlled intersections. Issue #3472
      Caution:
      Regression in 0.31.0. As a workaround, networks that were saved with netedit 0.31.0 can be repaired by calling netconvert -s bugged.net.xml -o fixed.net.xml or simply reopened and saved with a fresh nightly build of NETEDIT.
    • Options --window-size and --window-pos are now working when set in a configuration file. Issue #3406
    • Fixed crash when setting linkIndex. Issue #3642
  • DUAROUTER
    • Fixed invalid public transport routing if the last vehicle departs before the person enters the simulation. Issue #3493
  • TraCI
    • Fixed bug in traci.trafficlights.setLinkState.
    • Fixed bug in traci.vehicle.getDrivingDistance related to internal edges. Issue #3553
    • Fixed bug in traci.vehicle.getDistance related to looped routes. Issue #3648
    • Fixed bug in traci.simulation.getDistance2D and traci.simulation.getDistanceRoad related to internal edges. Issue #3554
    • Command load no longer fails when there are too many arguments or long file paths. Issue #3599
    • Fixed bug in traci.vehicle.changeLane when using the sublane model. Issue #3634
  • Tools
    • Fixed bug that would trigger an infinite loop in flowrouter.py.
    • ptlines2flows.py fixes:
      • missing stops no longer result in crashing
      • fixed invalid until times when multiple lines use the same stop
    • emissionsDrivingCycle now uses the slope values from the correct time step when forward calculation of acceleration is enabled
    • generateTurnDefs.py now writes interval information. Thanks to Srishti Dhamija for the patch. Issue #3712

Enhancements

  • Simulation
    • Added option --collision.mingap-factor to control whether collisions are registered when the vehicle minGap is violated. With the default value of 1.0 minGap must always be maintained. When setting this to 0 only physical collisions are registered. Issue #1102
    • Added new junction model parameters Issue #3148:
      • jmIgnoreFoeProb, jmIgnoreFoeSpeed can be used to configure right-of-way violations.
      • jmSigmaMinor allows configuring driving imperfection (dawdling) while passing a minor link.
      • jmTimegapMinor configures the minimum time gap when passing a minor link ahead of a prioritized vehicle.
      • jmDriveAfterRedTime and jmDriveRedSpeed allow configuring red-light violations depending on the duration of the red phase.
    • Added new laneChangeModel-attribute lcLookaheadLeft to configure the asymmetry between strategic lookahead when changing to the left or to the right. Issue #3490
    • Added new laneChangeModel-attribute lcSpeedGainRight to configure the asymmetry between thrhesholds when changing for speed gain to the left or to the right. Issue #3497
    • Electric vehicles can now be used for emission-model (electricity) output by setting emissionClass="Energy/unknown"
    • Tripinfo-output for pedestrians now includes routeLength, duration and timeLoss. Issue #3305
    • duration-log.statistics-output now informs about person rides. Issue #3620
    • Vehicles that end their route with a stop on a parkingArea (arrivalPos is within the parkingArea bounds) will be assigned a new destination after rerouting to another parkingArea (previously they would drive to the original parkingArea edge after finishing their stop). Issue #3647
    • Rerouters now support the attribute timeThreshold which makes their activation dependent on on a minimum amount of accumulated waiting time. Issue #3669
    • Simulation step length has been decoupled from the action step length, which is the vehicle's interval of taking decisions. This can be configured globally via the option '--default.action-step-length', or per vehicle via the parameter 'actionStepLength'.
  • SUMO-GUI
    • Transparency is now working for all objects.
    • Junction parameters can now be inspected.
    • Upcoming stops are now shown in the vehicle parameter window and also in the network when selecting show current route. Issue #3679
  • NETCONVERT
    • When using option --numerical-ids together with option --output.original-names, the original IDs of all renamed nodes and edges are written to <param> elements with key origId. Issue #3246
    • connections now support the attribute speed to set a custom (maximum) speed on intersections. Issue #3460
    • connections now support the attribute shape to set a custom shape. Issue #2906
    • crossings now support the attribute shape to set a custom shape. Issue #2906
    • The new element <walkingArea> can now be used in con.xml files to define custom walking area shapes. Issue #2906
    • Added options --osm.stop-output.length.bus, --osm.stop-output.length.train, --osm.stop-output.length.tram to set appropriate default stop lengths for different modes of traffic (in conjunction with option --ptstop-output).
    • Added options --osm.all-attributes <BOOL> which can be used to import additional edge parameters such as bridge, tunnel and postcode.
    • Parallel lanes of connecting roads are now written as a single road in opendrive-output. Issue #2700
  • NETEDIT
    • Additional objects (i.e. detectors) as well as POIs and Polygons can now be located based on their ID. Issue #3069
    • Connection and Crossing shapes can now be edited visually. Issue #3464
    • Object types such as edges or polygons can now be locked against selection modification. Issue #3471
    • The traffic light index of controlled connections can now be edited in Inspect Mode. Issue #2627
    • Added button to traffic light mode for cleaning up unused states from a traffic light plan.
  • DUAROUTER
    • Vehicles and flows which are considered public transport (have the line attribute) are now only routed if an additional option --ptline-routing is given. Issue #2824
    • route alternative output (.rou.alt.xml) now contains costs for pedestrian stages. Issue #3491
  • TraCI
    • return value of trafficlights.getControlledLinks is now a list of lists (of links) for the C++ client as well
    • python client now supports the whole API for vehicle.setAdaptedTraveltime and vehicle.setEffort (resetting custom values or setting with default time range) by using default arguments.
      Note:
      The order of parameters had to be changed to allow this. Old code will still work but trigger a warning.

Other

  • Simulation
    • chargingstations-output now writes times as seconds rather than milliseconds.
    • Default value of option --pedestrian.striping.stripe-width changed to 0.64 (previously 0.65). This allows vehicles with default width to pass a pedestrian on a road with default width.
    • preliminary version of libsumo is available for experimental building of your own apps using SUMO as a "library" (calling its functions directly without TraCI)
  • SUMO-GUI
    • default font changed to Roboto
    • Removed OpenGL visualisation option Antialias
    • E3-Entry and -Exit detectors are now drawn in darker color to better distinguish them from traffic lights. Issue #3378
  • NETCONVERT
    • The element <customShape> is no longer supported. Instead <connection> and <crossing> support the shape attribute. To set a custom shape for walkingAreas, the new element <walkingArea> may be used.
  • TraCI
    • TraCI version is now 17

Version 0.31.0 (14.09.2017)

Bugfixes

  • Simulation
    • Sublane-model
    • Lane-changing
      • Fixed behavior problems in regard to the rule that prohibits overtaking on the right under some circumstances (by default this is prohibited in free-flowing motoroway traffic). Vehicles now avoid overtaking whenever braking is possible and they overtake on the left instead if there is a third lane. Issue #1214, Issue #2547, Issue #3115, Issue #3379
      • Fixed time loss due to late overtaking in some situations. Issue #2126
      • Fixed invalid overtaking to the left. Issue #3337}
    • Persons
      • Attribute arrivalPos is no longer ignored for person <ride> elements. Issue #2811
      • Fixed crash when pedestrian routes contain disallowed edges Issue #3248 Issue #3381
      • Fixed collision at prioritized crossings because pedestrians ignored some vehicles Issue #3393
    • Calibrators now respect the option --ignore-route-errors. Issue #3089
    • departLane="allowed" no longer selects an invalid departLane on multimodal edge. Issue #3065
    • Acquired waiting time of vehicles is now properly loaded from a simulation state. Issue #2314
    • Fixed output of meso calibrator (regression in 0.30.0). Issue #3132
    • Modified meanTimeLoss output of lane area (e2) detector. Semantics is now average time loss *per vehicle* Issue #3110
    • Fixed invalid stop state and invalid position of vehicles that cannot resume from parking due to blocking traffic. Issue #3153
    • Fixed erroneous calculation of occupancy in meandata output for vehicles being only partially on the corresponding lane. Issue #153
    • Fixed collision detection of junctions (some collisions were not registered). Issue #3171
    • Options --collision.stoptime is now working when collisions are detected on a junction (using Option --collision.check-junctions). Issue #3172
    • FCD-output now contains z-data if the network includes elevation information. Issue #3191
    • Fixed crash when loading invalid <busStop> definition with <access> element. Issue #3214
    • Fixed invalid errors on loading stops on looped routes. Issue #3231
    • Fixed crash on invalid <e2Detector> definition. Issue #3233
    • Fixed crash on saving and loading simulation state in conjunction with vehroute-output. Issue #3237,Issue #3238
    • Fixed too high density values in meandata output. Issue #3265
    • Fixed invalid routeLength in tripinfo-output. Issue #3355
  • SUMO-GUI
    • Fixed visual glitch when drawing vehicles with multiple carriages as raster images. Issue #3049
    • Fixed crash when reloading a simulation after editing the network. Issue #3059
    • Fixed crash when using invalid routes in calibrator. Issue #3060
    • The number of nodes listed in the network parameter dialog no longer includes internal nodes. Issue #3118
    • Fixed crash when multiple vehicles start and end parking on the same edge Issue #3152
    • All parking vehicles and empty parking spaces of a <parkingArea> are now accessible via right-click. Issue #3169
    • Fixed rendering position of <busStop>, <containerStop>, <chargingStation>, <parkingArea> on curved roads. Issue #3200
    • Fixed drawing position of vehicles with lateral offset and of passengers if a vehicle is on a very short lane (also affects fcd-output). Issue #3249
    • Corrected drawing of sublane borders in case the lane width is not a multiple of the lateral-resolution.
    • Fixed wrong occupancy values in Parameter Window for short lanes.
    • Pre-configured screenshots are now taken at the correct time regardless of simulation speed. Issue #1340
    • Fixed visual glitches when drawing waiting pedestrians, parking vehicles and parkingAreas in left-hand networks. Issue #3382
    • The list of additional simulation objects no longer includes POIs and polygons (they have their own locator lists). Issue #3384
  • Netconvert
    • --ptstop-output now exports stop lanes with the appropriate vClass. Issue #3075
    • --ptstop-output now exports stop lanes in the correct road direction Issue #3101, Issue #3212
    • Fixed invalid geo-reference when loading lefthand .net.xml files Issue #3198
    • Fixed bug that was causing an error when patching a .net.xml file with a .tll.xml file along with other connection-affecting patches. Issue #2868
    • Fixed insufficient precision of internal lane elevation in OpenDrive output.
    • Fixed overly long yellow duration in generated tls plans. Issue #3239
    • Fixed invalid lengths of internal turning lanes. As a side effect lane-changing is not possible any more while on these lanes. The old behavior can be enabled by setting option --junctions.join-turns <BOOL>. Issue #2082.
    • Variable phase durations are no longer lost when importing from .net.xml or .tll.xml files.
    • Information about edges without connections is no longer lost when exporting with option --plain-output-prefix. Issue #3332
    • Fixed invalid edge shape after importing a .net.xml file with custom node shape. Issue #3385
    • Fixes related to importing OpenDRIVE networks
      • Fixed error when loading <roadMark><type>-data. Issue #3163
      • Fixed crash when loading OpenDRIVE networks with attribute pRange. Issue #3164
      • Fixed invalid traffic lights. Issue #3203
      • Fixed invalid connections when importing OpenDRIVE networks
      • Fixed invalid internal-lane speed when importing OpenDRIVE networks or setting lane-specific speeds. Issue #3240
  • Netedit
    • Fixed rendering slowdown (regression in 0.30.0) Issue #3167
    • Fixed error when loading pois with attributes lane and pos (regression in 0.30.0) Issue #3199
    • Fixed crash when trying to filter selection of additionals by ID (regression in 0.30.0). Issue #3068
    • The z-Coordinate of junctions is now properly displayed again in inspect mode (regression in 0.30.00). Issue #3134
    • The z-Coordinate of junctions is no longer reset to 0 when moving them with move mode. Issue #3134
    • busStop and chargingStation elements with negative startPos or endPos can now be loaded.
    • Undo now restores the selection status of deleted additionals. Issue #3073
    • Loading color schemes is now working (only schemes saved by Netedit are valid). Issue #2936
    • Fixed invalid geo-reference when editing lefthand networks Issue #3198
    • The cycle time is now always shown for selected traffic lights in tls-mode. Issue #3206
    • Output precision set in the Options dialog now take effect. Issue #3219
    • When selecting edges (or lanes) that allow a specific vehicle class, edges (and lanes) with allow="all" are now matched. Issue #3168
    • Fixed crash when <ctrl>-clicking on invalid lanes in connection-mode.
    • Fixed invalid edge shape after setting a custom node shape. Issue #3276
    • Function replace by geometry node now preserves connections, crossings and custom geometry endpoinds. If the function is disabled, the reason is shown in the menu. Issue #3287
    • Joining junctions now always preserves edge endpoints. Issue #3257
    • Fixed invalid network after deleting traffic light and a junction with pedestrian crossings. Issue #3346
    • Fixed crash when joining tls. Issue #3365
    • The junction visualization option Show lane to lane connections now takes effect.


  • DUAROUTER
    • Fixed bugs that were causing intermodal routing failures. Issue #3119, Issue #3226
    • Fixed invalid speedFactor output when specifying both speedFactor and speedDev in the input files. Issue #3121
    • Fixed (almost) infinite loop when specifying <flow> without end. Issue #3225
    • Fixed handling of departPos and arrivalPos for persons. Issue #3246
  • MAROUTER
    • Fixed crash due to error in matrix parsing. Issue #3366
  • TraCI
    • After sending command traci.load() the simulation now keeps running until sending traci.close() instead of terminating when there are no more vehicles or the end time is reached. Issue #3048
    • Vehicle state change retrieval (simulation.getDepartedIDList, simulation.getArrivedNumber, ...) are now working after sending command traci.load(). Issue #3051
    • Vehicle commands getDistance and getDrivingDistance now return correct values when the current vehicle edge or the target edge are junction-internal edges. Issue #2321
    • Fixed invalid lane occupancy values when calling moveToXY. Issue #3185
    • traci.load() is now working if the previous simulation had errors. Issue #3204
    • Invalid edge ids in traci.vehicle.setRoute() no longer cause crashing. Issue #3205
    • Fixed moveToXY mapping failures. Issue #3263
    • Person context subscriptions are now working. Issue #3304
    • Fixed invalid behavior after canceling stop. Issue #3348
    • Fixed freeze when calling gui.screenshot Issue #3362

Enhancements

  • Simulation
    • Behavior at intersections can now be configured with new junction model parameters. Issue #3148
    • Emergency vehicles (vClass="emergency") may always overtake on the right.
    • The default car following model can now be specified on the command line with --carfollow.model. Issue #3142
    • Routing with --routing-algorithm astar is now working efficiently when using traffic assignment zones. Issue #3144
    • Lanechange-output now includes the type of the changing and the longitudinal gaps on the target lane. Issue #3156
    • Stops on internal lanes may now be defined.
    • Aggregate trip information generated via option --duration-log.statistics now includes vehicles that were still running at simulation end if the option --tripinfo-output.write-unfinished is also set. Issue #3209
    • Vehicles now react to pedestrians on the same lane. Issue #3242
    • Pedestrians now react to vehicles that are blocking their path. Issue #3138
    • Collisions between vehicles and pedestrians are now detected when setting the option --collision.check-junctions.
    • Pedestrian <walk>s may now be defined using attribute route. Issue #3302
    • Summary-output now includes mean vehicle speed (absolute and relative) as well as the number of halting vehicles. Issue #3312
    • Pedestrian statistics are now included in the aggregated traffic measures. Issue #3306
    • Tripinfo-output now includes additional attributes for persons and containers stages (depart, waitingTime, duration, vehicle, arrivalPos, actType). Issue #3305
    • Added new lanechangeModel parameter lcAccelLat to model lateral acceleration in the sublane model. Issue #3371
  • SUMO-GUI
    • All <param> values of simulation objects (i.e. TLS) can now be inspected. Issue #3098
    • Calibrators can now be defined for specific lanes not just for the whole edge.
      Caution:
      To obtain the old behavior, calibrators must use the attribute edge. When using the attribute lane the new behavior is activated.
      Issue #2434
    • When using the Sublane model, the lateral offset of left and right vehicle side as well as the rightmost and leftmost sublane are listed in the vehicle parameter dialog.
    • Added button for calibrating lane/edge colors to the current value range. Issue #2464
    • POIs which are defined using attributes lane and pos now accept the optional attribute posLat for specifying lateral offset relative to the lane. Issue #3339. These attributes are automatically added as generic parameters retrievable via TraCI.
    • Added option --tracker-interval <FLOAT> to configure the aggregation interval of value tracker windows. Previously this was fixed at 1s. Now it defaults to the --step-length value.
  • NETCONVERT
    • <split>-definitions now support the attribute id to specify the id of the newly created node. Two-way roads can be split with the same node by using the same id in two split definitions. Issue #3192
    • Variable lane widths are now taken into account when importing OpenDrive networks. The new option --opendrive.min-width <FLOAT> is used to determine which parts of a lane are not usable by the vehicles (default 1.8m). Issue #3196
    • Added option --tls.red.time <TIME> for building a red phase at traffic lights that do not have a conflicting stream (i.e. roads with a a pedestrian crossing in a network that is not meant for pedestrian simulation). The new default value is 5 seconds. Issue #1748
    • Added option --tls.allred.time <TIME> for building all-red phases after every yellow phase. Issue #573
    • Added option --walkingareas to allow generation of walkingareas in networks without pedestrian crossings. Issue #3253
    • Added option --opposites.guess.fix-lengths <BOOL> to ensure that opposite lane information can be set for curved roads. (see Simulation/OppositeDirectionDriving#Limitations).
    • Custom lane shapes can now be defined. Issue #2250
    • Added options --tls.min-dur <TIME> and --tls.max-dur <TIME> for defining the time range of non-static traffic lights. Issue #3329
    • The option --proj.scale now accepts arbitrary floats and can be used to scale the output network. Issue #3351
  • NETEDIT
    • POIs and Polygons can now be defined with a new editing mode. Issue #1667
    • Minimum and maximum phase duration for actuated traffic lights can now be defined. Issue #831
    • Added button for calibrating lane/edge colors to the current value range. Issue #2464
  • DFROUTER
    • Added option --randomize-flows for randomizing the departure times of generated vehicles.

Other

  • SUMO now uses C++11
  • specifying the car following model as nested element in a vType is now deprecated
  • trips without ids are deprecated
  • router options are now more consistent with simulation options
    • use -a for additional files
    • use -r or --route-files for all kinds of route input (trips, flows, routes, alternatives)
    • the old options --flows, --trips, -- alternatives are deprecated
    • The network argument for routeStats.py is now optional and set with option -n.
  • The option proj.shift which used to be an alias for --proj.scale is no longer supported. These option were used to set a scaling factor by negative powers of ten but now --proj.scale sets the scaling factor directly (the previous value 5 now corresponds to 1e-5)
  • default detector-gap for actuated traffic lights is now 2.0s. Issue #3340
  • default minGapLat value (used by the sublane model is now 0.6m (down from 1.0m) to better match observations.
  • Documentation
  • TraCI
    • TraCI version is now 16

Older Versions