https://github.com/eclipse/sumo/blob/1fd856dfd8db8d6379215a4be06579b7c3cffdc8/src/microsim/devices/MSRoutingEngine.cpp#L179-L181

Am Di., 8. Sept. 2020 um 05:40 Uhr schrieb Jane Cheung <
[email protected]>:

> Jakob,
> thanks for your reply.
>  As described in the document, the function of -*-weights.random-factor
> FLOAT*  is  "   Edge weights for routing are dynamically  disturbed by a
> random factor drawn  uniformly from [1,FLOAT)"
> Where could I find some mathematical formulation or the function describe
> the dynamically disturbed process?
>
>
> Best regards,
>
> Jane
>
>
>
> On Mon, Sep 7, 2020 at 6:27 PM Jakob Erdmann <[email protected]>
> wrote:
>
>> 1) "normal" vehicle was meant in contrast to trips (which already imply
>> some routing)
>> 2) random roll of the dice (unrelated to traffic situation). Think of
>> this as the set of vehicles equipped with a live-traffic route finding
>> software
>> 3) option --verbose
>> 4) it depends. We often use 300s in our projects
>> 5) duarouter -r trips.xml -o routes.xml --weights.random-factor FLOAT
>> 6) The "current traffic condition" is an average over past traffic states
>> as explained at https://sumo.dlr.de/docs/Demand/Automatic_Routing.html.
>> No equilibrium iteration is done for this.
>>
>> Am Fr., 4. Sept. 2020 um 05:54 Uhr schrieb Jane Cheung <
>> [email protected]>:
>>
>>> Jakob,
>>>
>>> Thanks for your reply.
>>>
>>>  More questions about the previous email.
>>>
>>> 1) the probability could be set in the range of (0,1], and <00 value
>>> means *normal vehicles* will not perform rerouting.
>>>
>>>    - What kind of vehicle is not the *normal vehicle*?  The the only
>>>    scenario I know is to use Traci to reroute in the simulation.
>>>    - If I set  <device.rerouting.probability value="*0.5*"/> and the s
>>>    log.txt is printed as below:
>>>
>>>
>>>
>>> Performance:
>>>
>>>  Duration: 297822ms
>>>
>>>  Real time factor: 18.1316
>>>
>>>  UPS: 32080.783152
>>>
>>> Vehicles:
>>>
>>> * Inserted: 14158 (Loaded: 17538)*
>>>
>>> * Running: 2061*
>>>
>>> * Waiting: 3356*
>>>
>>>
>>>
>>> Does it mean SUMO would choose 50% of *vehicles* to have the ability of
>>> rerouting?
>>>
>>>    - The *vehicles* are in terms of the *inserted vehicles(14158)* or
>>>    the *loaded ones(17538)*?
>>>    - How does SUMO *decide which vehicle* can reroute?
>>>
>>>
>>>    - For example, edge A1B1 and edge B1A1  are *100m*, the number of
>>>    vehicles on edgeA1B1 is *18*(edge *A1B1* most in congestion), the
>>>    number of vehicles on edge *B1A1  is 6*. The Sumo would choose 10
>>>    vehicles among  20 vehicles on edge A1B1 and 3 vehicles among 6 vehicles 
>>> on
>>>    edgeB1A1. Is that right? Obviously, traffic conditions in the two edges 
>>> are
>>>    different. Edge A1B1 is mostly in congestion, and vehicles on edge B1A1 
>>> can
>>>    run in free-flow speed. More rerouting devices are assigned to vehicles 
>>> on
>>>    edge A1B1 might be a better choice. Could SUMO assign rerouting devices
>>>    like that, or SUMO uses other more realistic strategies to choose which
>>>    vehicle can reroute?
>>>    - As explained in
>>>    https://sumo.dlr.de/docs/Simulation/Output.html#timing_data
>>>    - How to let output printed the total time spend routing and average
>>>    time per routing call?
>>>    - According to your experience, the suitable frequency of calling
>>>    rerouting is?
>>>
>>>
>>>
>>>
>>>
>>> 2) as you explained *in 2),* “all vehicles   <route-files
>>> value="casemy.trips.xml"/>when entering the simulation (pre-insertion
>>> rerouting uses the departure as the first routing time)  but no further
>>> rerouting takes place due to the high period.”
>>>
>>> In my understanding,
>>>
>>>    - if I use the *trips   <route-files value="casemy.trips.xml"/> *in
>>>    *.sumocfg* file, the “*reroute once*” means *route* or generating
>>>    the route    file firstly for inserted vehicles to let vehicles know 
>>> edges
>>>    they are scheduled to drive, and then, during the simulation the inserted
>>>    vehicle will not reroute due to the high period;
>>>    - if I have the *trips file*, how could I generate the *route file 
>>> *randomly?
>>>
>>>    - if I use the routes   *<route-files value="casemy.rou.xml"/>* in
>>>    *.sumocfg* file, the “*reroute once*”  means *reroute. *In other
>>>    words, , SUMO will assign the fastest routes to all inserted
>>>    vehicles according to the traffic condition at the inserted time point of
>>>    vehicles.
>>>    - Which algorithm does SUMO use to find the fastest routes when
>>>    vehicles are going to enter into the simulation? The user equilibrium
>>>    model, such as call *duarouter.exe* run in 50 interaction or other
>>>    ones?
>>>
>>>
>>> Appreciated in advance!
>>>
>>> Best regards,
>>>
>>> Jane Cheung
>>>
>>> _______________________________________________
>>> sumo-user mailing list
>>> [email protected]
>>> To unsubscribe from this list, visit
>>> https://www.eclipse.org/mailman/listinfo/sumo-user
>>>
>> _______________________________________________
>> sumo-user mailing list
>> [email protected]
>> To unsubscribe from this list, visit
>> https://www.eclipse.org/mailman/listinfo/sumo-user
>>
> _______________________________________________
> sumo-user mailing list
> [email protected]
> To unsubscribe from this list, visit
> https://www.eclipse.org/mailman/listinfo/sumo-user
>
_______________________________________________
sumo-user mailing list
[email protected]
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/sumo-user

Reply via email to