[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [sumo-user] weight update inteval
|
Yes. If device.rerouting.adaptation-interval is small, then CHRouter will spend more time updating itself and this will slow down the simulation.
So, Can I say when the interval is a small number, then the duration variable, in output, will be bigger, because of updating weights in each interval? Also, as a consequence, the real-time factor will be smaller (simulation time doesn't change that much, as I noticed)?
At the given interval, the weights are updated and those are used automatically by Astar and Dijkstra. The reason for 'myValidUntil' is the unique need to by CHRouter to perform pre-processing once the weights change.
Thanks.
So, Could we say that "myValidUntil" parameter in CHRouter.h file, is set based on the value given to the option --device.rerouting.adaptation-interval?
How this is used in Astar and Dijkstra?
--
RAZ
_______________________________________________
sumo-user mailing list
sumo-user@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/sumo-user
_______________________________________________
sumo-user mailing list
sumo-user@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/sumo-user
--
RAZ
_______________________________________________
sumo-user mailing list
sumo-user@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/sumo-user