Z/Changes from Version 0.30.0 to Version 0.31.0
Version 0.31.0 (14.09.2017)
Bugfixes
- Simulation
- Sublane-model
- Lane changing to clear the overtaking lane (motivation keepRight) is now working properly. Issue #3106
- Fixed error that prevented violating right-of-way rules in the sublane-model. Issue #3140
- Fixed bug that was preventing speed adaptations for strategic changing. Issue #3183
- Fixed error that prevented changing for speed gain Issue #3107, Issue #3186
- Insertion with departPosLat="random" departPos="last" is now working. Issue #3191
- Fixed bug that could cause deadlocks on an intersection Issue #3189
- Fixed collisions Issue #3195, Issue #3213, Issue #3050, Issue #2837
- Fixed invalid angles when lane-changing at low speeds or low step-length. Issue #3220
- Fixed oscillation. Issue #3333
- Fixed too-late changing for speed gain when approaching a slow leader. Issue #3375
- Fixed bug that was causing sublane-changing despite speed loss. Issue #3372
- 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
- Sublane-model
- 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
- Tools
- netdiff.py now correctly handles junctions that had their radius or z attributes changed to the (unwritten) default value.
- randomTrips.py now correctly handles --trip-attributes that contain a space in the value (i.e. modes). Issue #3117
- Fixed bug that was causing insufficient flow when using flowrouter.py. Issue #3285
- Fixed flowrouter.py crash. Issue #3356
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:Issue #2434
To obtain the old behavior, calibrators must use the attribute edge. When using the attribute lane the new behavior is activated. - 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
- TraCI
- Support for multiple clients. Issue #3105
- Added function vehicle.getAccumulatedWaitingTime to retrieve the waiting time collected over the interval --waiting-time-memory. Issue #999
- Added many value retrieval functions to the C++ client. Thanks to Raphael Riebl for the patch!
- New vehicle types can be created dynamically (by duplicating existent). -> traci.vehicletype.copy() Issue #3211
- Added function person.rerouteTraveltime to reroute pedestrians. Issue #3352
- Rerouting-device period can now be set for individual vehicles. assumed edge travel times can be set globally. Issue #3097
- Rerouting-device period and assumed edge travel times can now be retrieved. Issue #3097
- DUAROUTER
- Routing with --routing-algorithm astar is now working efficiently when using traffic assignment zones. Issue #3144
- Stops on internal lanes are now supported. Issue #3174
- Pedestrian <walk>s may now be defined using attribute route. Issue #3302
- DFROUTER
- Added option --randomize-flows for randomizing the departure times of generated vehicles.
- OD2TRIPS
- Added option --pedestrians for generating pedestrian demand rather than vehicles. Issue #3331
- Added option --persontrips for generating intermodal traffic demand. Issue #3331
- Tools
- osmWebWizard.py now supports location search. Issue #2582
- osmWebWizard.py now generates scenarios with actuated traffic lights
- osmWebWizard.py now generates traffic with more realistic speed distribution
- flowrouter.py now supports specifying route restrictions to resolve ambiguities.
- When setting randomTrips.py option --vehicle-class, vType attributes from option -t are recognized and writen to the generated vType. Issue #3335
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
- Added description of automatically generated traffic light programs.
- Added Tutorial for importing public transport data from OSM.
- Extended page on Safety-related topics
- Added overview page for Geo-Coordinates
- TraCI
- TraCI version is now 16