Jakob, thanks so much!!
After reading the links you attached, I still would like to ask a few quesitons and Thanks in advance:
Q2, Q4: no. Sumo will load vehicles that depart within the next 300 seconds. This will probably not be noticable in execution time unless you have very many vehicles. Then after having simulation ~300 seconds it will load vehicles for the next 300 seconds.
This is faster than loading new vehicles in every simulation step and conserves memory compared to loading all at once.
I got it!!
Question:
Does it mean that traffic lights are also an indirect factor that affects the rerouting route choice, in other word, the traffic lights control model are considered in the rerouting algorithm by SUMO. Because the traffic light control model affects the edge travel time?
if the command "-device.rerouting.probability=xx" was NOT defined in xx.sumocfg
Will SUMO defaults that "--device.rerouting.pre-period =60" even though we did not write this command in the xx.
Yes. The default is always active. There are other ways of giving vehicles the device (via other options, xml parametesr or traci calls)
I got it ! Thanks!
-device.rerouting.adaptation-steps
Question:
--device.rerouting.adaptation-interval <INT> | 1 | The interval for updating the edge weights. |
--device.rerouting.adaptation-weight <FLOAT> | 0.5 | The weight of prior edge weights for exponential averaging from [0, 1]. |
--device.rerouting.adaptation-steps <INT> | 0 | The number of adaptation steps for averaging (enable for values > 0). |
in my understanding, the weight is associated the edge speed , what's more, the weight or the edge speed is affected by the steps (which affect the previous average speed value) and the interval(affect the current speed)
for example, one simulation will last about 900s, if we defined these commands,
--device.rerouting.adaptation-interval = 1(means1 second )
--device.rerouting.adaptation-weight =0
--device.rerouting.adaptation-steps=3
When the simulation is running at the time of 600s,
For the formulation
1) Float=0 (-device. rerouting. adaptation-weight =0) which means DO NOT take the previous speed information into the consideration
2) Prior value=the last three (--device.rerouting.adaptation-steps=((meanspeed in 599s-600s) +(,meanspeed in 598s-599s)+(meanspeed in 597s-598s))/3
For 599s-600s, 598s-599s, 597s-598s is determined by the --device.rerouting.adaptation-interval = 1
If we set --device. rerouting. adaptation-interval = 2 we need the mean speed of 598s-600s 596s-598s 594s-596s
Q2, Q4: no. Sumo will load vehicles that depart within the next 300 seconds. This will probably not be noticable in execution time unless you have very many vehicles. Then after having simulation ~300 seconds it will load vehicles for the next 300 seconds.
This is faster than loading new vehicles in every simulation step and conserves memory compared to loading all at once.
if the command "-device.rerouting.probability=xx" was NOT defined in xx.sumocfg
Will SUMO defaults that "--device.rerouting.pre-period =60" even though we did not write this command in the xx.
Yes. The default is always active. There are other ways of giving vehicles the device (via other options, xml parametesr or traci calls)
-device.rerouting.adaptation-steps