Hello, teleporting is usually done to mitigate scenario problems. Raising this value can be useful it the scenario is intentionally jammed and vehicles should be forced to stand around rather than teleport to resolve deadlocks. Teleporting can also be used to model the fact that vehicles typically find a way around blockages in ways that is not explicitly handled by the simulation (e.g. driving over curbs and sidewalks). If you want to model the jamming that occurs due to the accident then you could use a higher value for time-to-teleport in the accident. But this also depends on your assumptions on whether vehicles can find a way around the blockage or not.
regards, Jakob teleporting are usually an indicator of scenario problems and - when there are problems with the scenario - when you are modell 2018-09-14 7:43 GMT+02:00 Ei Ei Mon <[email protected]>: > Dear, > > In my case,I create an accident by stopping the vehicle for 10 minutes. I > use '--time-to-teleport',"650" for both with accident case and without > accident case. Is it consistent? Can effect of this parameter may be > different or not for two cases? Could you tell me some suggestions? > > Thank you in advance. > > with best regards, > > On Tue, Sep 11, 2018 at 11:16 PM Ei Ei Mon <[email protected]> > wrote: > >> Dear, >> >> Now, I can create the accident case by stopping the vehicle. Thank you >> very much. Another I would like to know is that I want to get the data by >> using traci in every minute not every second. Can I use the --step-length? >> Could you give me some suggestion? >> >> with best regards, >> >> On Tue, Sep 11, 2018 at 9:32 PM Ei Ei Mon <[email protected]> >> wrote: >> >>> Noted. I will try again. Thank you for your reply. >>> >>> On Tue, Sep 11, 2018 at 9:26 PM Jakob Erdmann <[email protected]> >>> wrote: >>> >>>> Right-click the stopping vehicle in sumo-gui and select 'show current >>>> route'. This will cause stop duration info to be shown in the GUI. Is the >>>> duration value correct? Does it decrease as expected? What happens after >>>> the time is up? >>>> >>>> >>>> 2018-09-11 14:42 GMT+02:00 Ei Ei Mon <[email protected]>: >>>> >>>>> Dear, >>>>> >>>>> Vehicle always stop on the specified lane even duration is over. >>>>> >>>>> On Tue, Sep 11, 2018 at 7:28 PM Jakob Erdmann <[email protected]> >>>>> wrote: >>>>> >>>>>> What are the symptoms of "not working"? >>>>>> >>>>>> 2018-09-10 13:58 GMT+02:00 Ei Ei Mon <[email protected]>: >>>>>> >>>>>>> Dear, >>>>>>> >>>>>>> Thank you for your time. >>>>>>> >>>>>>> Now I use sumo 1.0.0 version. When I try to create accident case as the >>>>>>> following: >>>>>>> >>>>>>> if(step>=21600 and step<=22000): >>>>>>> >>>>>>> >>>>>>> traci.vehicle.setStop('43.0',edgeID='L10189',laneIndex=1,pos=90,duration=600,flags=0,startPos=50); >>>>>>> >>>>>>> *duration *is not still working. Something wrong in my code? >>>>>>> >>>>>>> >>>>>>> with best regards, >>>>>>> >>>>>>> >>>>>>> On Mon, Sep 10, 2018 at 6:09 PM Jakob Erdmann <[email protected]> >>>>>>> wrote: >>>>>>> >>>>>>>> Answers below: >>>>>>>> >>>>>>>> Now I would like to know about the difference between the outputs >>>>>>>>> of edge-based measures and using lane area detectors. I want to get >>>>>>>>> the >>>>>>>>> information related with edge like density, occupancy , speed. For >>>>>>>>> this >>>>>>>>> purpose, which of the following approaches is suitable? >>>>>>>>> >>>>>>>>> 1) edge-based measures >>>>>>>>> 2)using lane-area detectors >>>>>>>>> >>>>>>>> >>>>>>>> The main difference is that edge based measures always count the >>>>>>>> whole edge whereas detectors only count a lane section. >>>>>>>> Both approaches are possible but edge based measures require less >>>>>>>> aggregation if you need the data for the whole edge. >>>>>>>> >>>>>>>> >>>>>>>> traci.vehicle.setStop('43.0',edgeID='L10189',laneIndex=1,pos=90,duration=600,flags=0,startPos=50); >>>>>>>>>> >>>>>>>>>> but in this case, *duration *attribute is not working. >>>>>>>>>> >>>>>>>>>> In older versions of SUMO, setStop requires a duration in >>>>>>>> milliseconds. since 1.0.0 duration is in seconds. >>>>>>>> >>>>>>>> >>>>>>>>> >>>>>>>>>>> In my case, I want queue length of each edge. For this case, now >>>>>>>>>>> I compute the average value from queue length of each lane by using >>>>>>>>>>> lane >>>>>>>>>>> area detector. Is it possible by using this way? Or are there any >>>>>>>>>>> other >>>>>>>>>>> methods to get queue length directly from each edge? >>>>>>>>>>> >>>>>>>>>>> No, the queue length is only available for each lane. You have >>>>>>>> to aggregate the edge data yourself. >>>>>>>> >>>>>>>> regards, >>>>>>>> Jakob >>>>>>>> _______________________________________________ >>>>>>>> sumo-user mailing list >>>>>>>> [email protected] >>>>>>>> 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 >>>>>>> [email protected] >>>>>>> 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 >>>>>> [email protected] >>>>>> 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 >>>>> [email protected] >>>>> 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 >>>> [email protected] >>>> 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 > [email protected] > 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 [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/sumo-user
