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
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 ./SUMO/Demand/trips_marouter.trip.xml --net-file
./SUMO/Net/sumo_secondary_filter.net.xml -o
./SUMO/Output/marouter_outputastar.rou.xml
CHRouter currenlty doesn't work very well with marouter:
- the results are wrong because the contraction hierarchy doesn't get
rebuilt
- it works slowly since CHRouter doesn't support efficient 1-to-many
routing
try astar.
Am Mo., 17. Mai 2021 um 13:02 Uhr schrieb Sasan Amini :
> I am passing
I am passing the following command with almost all default values for the
parameters: marouter --route-files ./SUMO/Demand/trips_marouter.trip.xml
--net-file ./SUMO/Net/sumo_secondary_filter.net.xml -o
./SUMO/Output/marouter_output.rou.xml --weights.interpolate
--paths.penalty 1 --junction-taz
There is only the code:
https://github.com/eclipse/sumo/blob/64a041537ce537690f5a22edcc46ef40df8d5fa0/src/marouter/ROMAAssignments.cpp#L115-L163
astar should work fine with marouter default options. Which options are you
passing?
Am Mo., 17. Mai 2021 um 12:02 Uhr schrieb Sasan Amini :
> Thank
Thank for the explanation. Are there any documents to help me make a
realistic guesstimation of travel times? What I see in the course code
is travelTime
= capacityConstraintFunction(edge, newFlow / intervalLengthInHours);
and thought travel times are directly exportable from Marouter. What is
The issue with fromJunction and toJunction is now fixed.
The route costs in marouter are travel times multiplied with a
traffic-density dependent capacityConstraintFunction.
The actual travel time can only be guessed at at this point since it will
depend on vehicle interactions. To compute
True, the scale parameter works perfectly fine. I am not sure if I was
testing it on a nightly build version of 1.8.x, but now on 1.9.0 it works.
However, the fromJunction - toJunction option for route files is not
working, while it works perfectly fine in DUAROUTER. Moreover, for the
output of
Scaling route file input is supposed to work since 1.9.0 (and it's working
in our test). Can you send me a minimal failing example for 1.9 or later?
Am Sa., 1. Mai 2021 um 14:46 Uhr schrieb Sasan Amini :
> Dear all,
>
> I am running MAROUTER on an extremely large network and have only 1% of
>
