Dear sir/madam
I am conducting a test for a single intersection in SUMO. I found that when
I assigned the pedestrian from the west to the south, he/she didn't follow
the crossings, instead, he/she simply moves from the northwest corner to
the southeast corner (see figure below, ped 6).
I noticed
That isn't possible at the moment.
Note, that randomTrips doesn't generate any routes, only trips. The routes
are created in the background by the duarouter application.
Code contributions are welcome (https://github.com/eclipse/sumo/issues/8643)
Am Di., 18. Mai 2021 um 17:07 Uhr schrieb Xun Liu
[cid:image003.jpg@01D74BD5.E9F1BC90]
Hello everyone,
I am using randomTrips.py to generate the route file for the network. And in my
generated rou.xml file, there is no route id for every route. Therefore, I
would like to consult if there were possible methods to assign the id for every
Thanks Dear Jakob,
After trying various methods, including the one you gave me, the difference in
estimated arrival times has been resolved!
The problem was that the exittime of the duarouter did not include the travel
time of the junction. So I set net.xml to --no-internal-links and that
There is currently no tool that supports this. As a workaround you could
- parse the intermodal routing graph written by duarouter
--intermodal-network-output and do your own exhaustive search
- run duarouter repeatedly and remove some or all used transport lines from
the input until you get no
Dear all,
is it possible to get all possible public transport routes for a person between
an origin and a destination?
So far I tried the "alternatives-output" of duarouter", which gave me merely
one trip definition for each person as alternatives, even though the options
"max-alternatives"
The speed depends on the right-of-way rules and traffic on minor roads has
to slow down before entering the intersection.
You can reduce the slow-down by setting a higher value for attribute
'visibility' of the connection elements (if vehicles can observe that the
intersecion is free of traffic
Thank you for your reply.
I changed the VType and was able to reduce the difference in arrival time a bit.
However, there is still a big difference.
After observing the simulation, there is still a deceleration of 1 to 2 m/s at
the junction and I think this is one of the reasons.
For reference, I
In the simulation, there are some random factors that affect vehicle speed.
See https://sumo.dlr.de/docs/Simulation/Randomness.html
You can eliminate them by re-configuring the vType with sigma="0"
speedDev="0".
Note, that there can still be interaction at junctions which are not
predicted by
Please update to the latest repository version which now supports all use
cases.
Am Mo., 17. Mai 2021 um 22:04 Uhr schrieb Sasan Amini :
> Dear all,
>
> since version 1.9.1 I noticed a small change in the sumolib/xml.py in
> parse_fast_nested function i.e.
>
The option --weight-priority is only compatible with Dijkstra at the
moment.
Am Mo., 17. Mai 2021 um 20:07 Uhr schrieb Sasan Amini :
> A* (astar) routing algorithm works only when I pass no options. When I
> pass the following options, it switches back to Dijsktra:
> marouter --route-files
Dear friends and users,
due to a bug in traci related to subscriptions we are releasing 1.9.2 as a
hotfix.
The download links are at https://sumo.dlr.de/wiki/Download
There are some additional fixes and even some enhancements in this release
and
the most important ones are listed below.
For a full
12 matches
Mail list logo
