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.
The route computation only depends on edge length and edge travel time. There multiple algorithsm/options for estimating this travel time: http://sumo.dlr.de/wiki/Simulation/Routing#Travel-time_values_for_routing 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 > This option actives an alternative algorithm for averaging travel times: http://sumo.dlr.de/wiki/Demand/Automatic_Routing#Adapting_by_moving_average 2018-09-13 1:31 GMT+02:00 Jane Cheung <cheung180...@gmail.com>: > --device.rerouting.adaptation-steps *<INT>* > <http://sumo.dlr.de/wiki/Basics/Notation#Referenced_Data_Types> 0 The > number of adaptation steps for averaging (enable for values > 0). > for example > --device.rerouting.adaptation-steps *=3* > Does this command is used to limit the frequency (or number of times) > that one vehicle could choose to reroute the route for itself, even though ( > *--device*. *rerouting*. *Period* */probability/deterministic/pre-period) > *have been defined? > In example, it means one or all vehicles could only choose to reroute 3 > times at most? > Jakob, Thanks a lot! > > Looking forward for your reply! > > > Best! > > > Jane > > On Wed, Sep 12, 2018 at 3:58 PM Jakob Erdmann <namdre.s...@gmail.com> > wrote: > >> Q1: they are moved forward along their route but they take up no space in >> the road network. >> Q2: no, vehicles are loaded in chunks of ~300 seconds and every bernoulli >> experiment is done only when the vehicle is loaded >> Q3: correct >> Q4: no, see Q2. >> Q5: yes. after insertion, the option device.rerouting.period determines >> the rerouting period and pre-period is no longer relevant. >> >> 2018-09-12 22:52 GMT+02:00 Jane Cheung <cheung180...@gmail.com>: >> >>> Jakob, >>> Thanks for your detail expression to my question. >>> After your explanation, I would like to make sure that I really >>> understand what you explained to me. >>> for --teleported >>> * Q1*:Dose it mean that >>> even though we could not see the vehicle which is teleported ,this >>> vehicle still driving in the network . >>> Just like 'Stealth' ? >>> >>> for --device.rerouting.xxxx commands >>> >>> 1) device.rerouting.deterministic is a boolean option >>> Example. You have set device.rerouting.probability to 0.33333333 and >>> there are 10000 vehicles in your simulation. >>> Without option device.rerouting.deterministic, you will have an >>> expected number of 3333 vehicles with rerouting device but the actual >>> number will vary according to a binomial distribution >>> *Q2*:(Does it mean that it will do a sequence of 10000 dependent >>> experiments with p=0.33333333 as soon as we start to simulate our >>> simulation?,like Bernoulli experiment?) >>> >>> >>> 2) Every vehicle that is driving in the network will check for a faster >>> route and adapt it's route if the current one isn't fastest once per minute >>> *Q3*:(Every vehicle that is loaded, but has not yet entered the network >>> will not be controlled by this command) >>> >>> 3) Every vehicle that is loaded but has not yet entered the network >>> will l check for a faster route and adapt it's route if the current one >>> isn't fastest once per minute >>> *Q4*:(all the vehicles will be loaded that the beginning of the >>> simulation if they are pre-defined in the rou.xml) >>> *Q5*:(the command could not be used to control these vehicles once >>> they entered the network) >>> >>> >>> Thanks at all! >>> >>> Best! >>> Jane >>> >>> >>> On Wed, Sep 12, 2018 at 3:09 PM Jakob Erdmann <namdre.s...@gmail.com> >>> wrote: >>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> 2018-09-12 21:57 GMT+02:00 Jane Cheung <cheung180...@gmail.com>: >>>> >>>>> One more question, >>>>> in http://sumo.dlr.de/wiki/Demand/Automatic_Routing >>>>> >>>>> --device.rerouting.deterministic false The devices are set >>>>> deterministic using a fraction of 1000 (with the defined *probability* >>>>> ) >>>>> --device.rerouting.period *<STRING>* >>>>> <http://sumo.dlr.de/wiki/Basics/Notation#Referenced_Data_Types> 0 The >>>>> period with which the vehicle shall be rerouted >>>>> --device.rerouting.pre-period *<STRING>* >>>>> <http://sumo.dlr.de/wiki/Basics/Notation#Referenced_Data_Types> 60 The >>>>> rerouting period before insertion/departmy understanding are listed >>>>> below, are they correct? >>>>> for example: >>>>> 1) >>>>> --device.rerouting.deterministic=0.07 >>>>> 0.07 equals to 0.7(in a fraction of 100) >>>>> >>>>> 2) >>>>> --device.rerouting.period =60 For every vehicle, not matter is >>>>> loaded into the network or not, it means this vehicle will reroute >>>>> its route every *MINUTE* (using the specified rerouting algorithm, like >>>>> Dijkstra) >>>>> until this vehicle arrives at the destination. >>>>> >>>>> It >>>>> --device.rerouting.pre-period =60for very vehicle which has not been >>>>> loaded into the network, it means that vehicle will reroute its >>>>> route every *MINUTE* according to the current traffic condition >>>>> until it is going to depart from the departure position. >>>>> >>>>> Thanks at all! >>>>> >>>>> >>>>> Best! >>>>> >>>>> Jane >>>>> >>>>> On Wed, Sep 12, 2018 at 1:37 PM Jane Cheung <cheung180...@gmail.com> >>>>> wrote: >>>>> >>>>>> Deal all, >>>>>> Could someone help me to understand the meaning of >>>>>> *teleport/teleported* ? >>>>>> “http://sumo.dlr.de/wiki/SUMO” >>>>>> >>>>>> Thanks in advance >>>>>> >>>>>> Best regards! >>>>>> >>>>>> Jane >>>>>> >>>>> >>>>> _______________________________________________ >>>>> sumo-user mailing list >>>>> sumo-user@eclipse.org >>>>> To change your delivery options, retrieve your password, or >>>>> unsubscribe from this list, visit >>>>> https://dev.eclipse.org/mailman/listinfo/sumo-user >>>>> >>>>> >>>> _______________________________________________ >>>> sumo-user mailing list >>>> sumo-user@eclipse.org >>>> To change your delivery options, retrieve your password, or unsubscribe >>>> from this list, visit >>>> https://dev.eclipse.org/mailman/listinfo/sumo-user >>>> >>> >>> _______________________________________________ >>> sumo-user mailing list >>> sumo-user@eclipse.org >>> To change your delivery options, retrieve your password, or unsubscribe >>> from this list, visit >>> https://dev.eclipse.org/mailman/listinfo/sumo-user >>> >>> >> _______________________________________________ >> sumo-user mailing list >> sumo-user@eclipse.org >> To change your delivery options, retrieve your password, or unsubscribe >> from this list, visit >> https://dev.eclipse.org/mailman/listinfo/sumo-user >> > > _______________________________________________ > sumo-user mailing list > sumo-user@eclipse.org > To change your delivery options, retrieve your password, or unsubscribe > from this list, visit > https://dev.eclipse.org/mailman/listinfo/sumo-user > >
_______________________________________________ sumo-user mailing list sumo-user@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/sumo-user
