Z/Changes from Version 0.28.0 to Version 0.29.0

generated on 2019-05-23 00:18:59.345937 from the wiki page for Z/Changes_from_Version_0.28.0_to_Version_0.29.0 for SUMO git

Version 0.29.0 (16.02.2017)

Bugfixes

  • NETEDIT
    • Fixed crash when doing undo/redo connection changes at a newly created junction. Issue #2662
    • Fixed slow operation when switching between move-mode and other modes in a large network.
    • Fixed slow operation when move junctions in large networks. Issue #2699
    • Selecting objects by matching against attributes now works on windows. Issue #2675
    • Fixed crash when setting custom geometry endpoinds. Issue #2693
    • Fixed shortcuts Issue #2694
    • Fixed crash when using option --numerical-ids.
    • Fixed visualization errors when using --offset.disable-normalizaton false
    • When adding sidewalks to selected lanes, pedestrians are now automatically forbidden on the other lanes. Issue #2708
    • Fixed an inconsistency with the definition of SUMO Time in Inspector mode. Issue #2625
  • SUMO-GUI
    • Fixed bug that was causing interface lag when right-clicking in networks with detailed geometry.
    • Configuring the visualisation of generated induction loops for actuated traffic lights is now working. Issue #2639
    • Fixed crash when coloring lanes by occupancy. Issue #2850
  • MESO
    • when using option --meso-tls-penalty the maximum flow at controlled intersections is now scaled according to fraction of available green time. Issue #2753
    • Fixed various issues related to inconsistent handling of net and gross time gaps. This was causing exaggerated speeds. The option --meso-taujf <TIME> now corresponds to the net time-gap (as do --meso-taufj, --meso-tauff). It's default value has been reduced from 2.0 to 1.73 correspondingly (reproducing the old behavior at 100km/h).
  • MESO-GUI
    • Fixed invalid coloring of the gap between lanes. Issue #1428
  • DUAROUTER
    • The default vehicle class is now passenger (as in the simulation). Note, that non-passenger classes such as trains now need an explicit type definition to be able to use rail edges. Issue #2829
    • The last vehicle from a flow is no longer missing if the flow duration is not a multiple of the period parameter. Issue #2864
    • Various fixes to intermodal routing functionality. Issue #2852,Issue #2857
  • TraCI
    • Fixed crash when trying to reroute vehicles before their departure.
    • Fixed inefficiency when calling vehicle.rerouteTravelTime() multiple times per simulation step (edge weights are now updated at most once per step).
    • Various fixes to vehicle.moveToXY mapping behavior.
    • unsubscribing now works in the python client. Issue #2704
    • The C++ client now properly closes the simulation when calling close()
    • Subscriptions to 2D-Positions are now working in the C++ client
    • Deleting vehicles that have not yet departed is now working. Issue #2803
    • Brake lights and blinkers can now be set for the current simulation step. Issue #2804
    • Vehicle function move to XY now works for edges with custom length. Issue #2809
    • Vehicle function move to XY now actually uses the 'edgeID' and 'lane index' parameters to resolve ambiguities. It uses the 'origID' parameter if set and the lane id otherwise.
    • Function edge.adaptTravelTime(begin=... end=...) is now working as expected with times in seconds. Issue #2808
  • Tools
    • netdiff.py now correctly handles changes to spreadType and other optional attributes. Issue #2722
    • sumolib.net now returns consistent values for edge.getShape(): the center-line of all lanes. Previously, the raw edge shape used in netconvert was returned.
    • randomTrips.py now works correctly when giving the options --via, --validate at the same time. Issue #2821

Enhancements

  • SUMO-GUI
    • Added new option --window-pos <INT>,<INT> for specifying the initial window placement.
    • Added new button to the object locator dialog that allows toggling selection status. Issue #2687
    • Parking vehicles are now listed in the vehicle locator dialog. This can be disabled using a new menu option. Teleporting vehicles can optionally be listed as well Issue #2750
    • Vehicles can now be colored by time loss (accumulated over the whole route). The time loss is also shown in the vehicle parameter dialog.
  • MESO
    • Added new option --meso-minor-penalty <TIME> for applying a time penalty when passing a minor link. This may be used to model slow down on approach or even intersection delays when running without --meso-junction-control. Issue #2640
    • When using the option --meso-tls-penalty <FLOAT> to model mesoscopic traffic lights, the maximum capacity of edges is now reduced according to the proportion of green-time and cycle time at controlled intersection. Issue #2753
  • MESO-GUI
    • The number of queues for the current segment is now shown in the edge parameter dialog
    • The latest headway for the current segment is now shown in the edge parameter dialog
  • NETCONVERT
    • Pedestrian rail crossings are now working. Issue #2654
    • Added new option --geometry.check-overlap <FLOAT> for finding edges with overlapping lanes. This is typically a sign of faulty inputs. The accompanying option --geometry.check-overlap.vertical-threshold <FLOAT> filters out edges that are separated vertically by at least the given value (default 4.0). Issue #2648
    • The options --keep-edges.explicit, --keep-edges.input-file now allow for white-listing in combination with other removal options (edges are kept if listed explicitly or if any other keep-condition is met). Issue #2680
    • Added new option --osm.oneway-spread-right <BOOL> for setting the default spreadType to right for one-way edges (i.e. motorways).
    • The <split>-element now supports the new attributes idBefore, idAfter to determine the ids of the newly created edges. Issue #2731
    • Added new option --reserved-ids <FILE> for loading a selecting of node and edge ids that shall be avoided in the output network.
    • When importing networks from DlrNavteq format, the new option --construction-date YYYY-MM-DD can now be used to interpret the readiness of roads under construction.
    • Networks exported to DlrNavteq format now contain additional information: bridge/tunnel information, form of way, ZIP code, prohibited_manoeuvres, connected_lanes
    • Warnings are now issued when steep grades are present in the road network. The warning threshold can be configured using the new option geometry.max-grade <FLOAT>.
    • <laneOffset> data is now imported from OpenDrive networks
  • NETEDIT
    • Added new option --window-pos <INT>,<INT> for specifying the initial window placement.
    • new hotkeys implemented. Issue #2694
    • New icons for edit modes. Issue #2612
    • Added new button to the object locator dialog that allows toggling selection status. Issue #2687
  • OD2TRIPS
    • Added new option --flow-output.probability <BOOL> for generating probabilistic flows instead of evenly spaced flows. Thanks to Dominik Buse for the patch.
  • TraCI
    • Added functions person.getStage, person.getRemainingStages, person.getVehicle and person.getEdges to the API, the python client and the C++ client. Issue #1595
    • Added functions person.add, person.appendWalkingStage, person.appendDrivingStage, person.appendWaitingStage, person.removeStage, person.removeStages, person.setColor, person.setLength, person.setHeight, person.setWidth, person.setMinGap, person.setType and person.setSpeed to the API, the python client and the C++ client. Issue #2688
    • The python client now supports vehicle.getPosition3D.
    • Added the functions vehicle.getLine and vehicle.setLine to the python client and the C++ client (to be used for public transport) Issue #2719
    • Added the functions vehicle.getVia and vehicle.setVia to the python client and the C++ client (affects subsequent rerouting calls) Issue #2729
    • Added the functions polygon.getFilled and polygon.setFilled to the python client
  • Miscellaneous
    • All applications now support the option --precision <INT> to specify the output precision as number of decimal places for floating point output. For lon/lat values this is configured separately using option --precision.geo <INT>.

Other

  • Simulation
    • A warning is now issued when trying to define a vehicle with vClass=pedestrian as this vClass should only be used for persons. Issue #2830
  • TraCI
    • TraCI version is now 14