I think the e1 type is unfit for this, since it has no real length. e2 could be used if the area you are interested in lies on a single edge. In that case the methods you mentioned should do the trick, and otherwise consult the documentation: you could also retrieve data for an edge, for example: https://sumo.dlr.de/docs/TraCI/Edge_Value_Retrieval.html
The e3 type detector might be interesting if your area of interest spans multiple edges: https://sumo.dlr.de/docs/TraCI/Multi-Entry-Exit_Detectors_Value_Retrieval.html Greets, Menno On 14-5-2021 14:05, ali mirzaei wrote: > I have had a look at it. But, as far as I know, I should ask the > simulation to get or set the vehicle data one at a time via that > module(traci.vehicle). I am looking for a facility to get the flow > data at a specific point automatically which I was thinking could be > e1 or e2 detector. > > Regards, > Ali > > > > On Fri, May 14, 2021 at 1:52 PM Menno van der Woude > <me...@codingconnected.eu <mailto:me...@codingconnected.eu>> wrote: > > the documentation provides ample info here: > > https://sumo.dlr.de/docs/TraCI/Vehicle_Value_Retrieval.html > <https://sumo.dlr.de/docs/TraCI/Vehicle_Value_Retrieval.html> > > I guess you could first determine what vehicles are in a given > area or location, and then retrieve data for those vehicles. > > Greets, Menno > > On 14-5-2021 11:20, ali mirzaei wrote: >> I get the point you said. But, my other question remains. What is >> the option to receive vehicle data at a specific point? >> Regards, >> Ali >> >> On Fri, May 14, 2021 at 12:37 PM Menno van der Woude >> <me...@codingconnected.eu <mailto:me...@codingconnected.eu>> wrote: >> >> That function should return the described value. However, if >> no vehicles were on the detector during the last step, no >> valid data can be returned, so you get -1 and (). If a >> vehicle was on the detector during the last step, the method >> will give you the data. >> >> Greets, Menno >> >> On 14-5-2021 10:04, ali mirzaei wrote: >>> Hi Menno, >>> This is what the mannaul says: >>> *getLastStepMeanSpeed(self, detID)* >>> *getLastStepMeanSpeed(string) -> double >>> >>> Returns the current mean speed in m/s of vehicles that were >>> on the named e2*. >>> >>> I am looking for a tool by which I can extract the flow >>> characteristics at the time the vehicle is on the detector. >>> So, is there any option to get more data of vehicles in >>> traci.lanearea module? >>> >>> Sincerely, >>> ALI >>> >>> >>> On Fri, May 14, 2021 at 11:33 AM Menno van der Woude >>> <me...@codingconnected.eu <mailto:me...@codingconnected.eu>> >>> wrote: >>> >>> Hello Ali, >>> >>> the e1 detector has no length, I think you should use an >>> e2 detector if >>> you want to have a detector that covers an area. >>> >>> Regarding the functions: when do you call these? I'd >>> expect -1 and () >>> when no vehicles were on the detector during the last >>> step. So at the >>> start of the simulation, you will most likely get those >>> results. And >>> afterwards if there has been no traffic. >>> >>> Greets, Menno >>> >>> On 13-5-2021 23:28, ali mirzaei wrote: >>> > Hi everyone, >>> > 1- What is the length of the induction loop(e1detector)? >>> > 2- in the case of e2detector, when I generate my >>> add.XML file consisting of: >>> > <e2Detector id="e2Detector_1" lane="e2_0" pos="15.22" >>> > length="10.00" freq="5" file="e2_det.xml" >>> friendlyPos="1"/> >>> > and call the functions: >>> > print(traci.lanearea.getLastStepMeanSpeed("e2Detector_1")) >>> > >>> print(traci.lanearea.getLastStepVehicleIDs("e2Detector_1")) >>> > the answer is "-1" and "()". >>> > Why does this happen? >>> > Any help would be appreciated. >>> > >>> > Regards, >>> > Ali >>> > _______________________________________________ >>> > sumo-user mailing list >>> > sumo-user@eclipse.org <mailto:sumo-user@eclipse.org> >>> > To unsubscribe from this list, visit >>> https://www.eclipse.org/mailman/listinfo/sumo-user >>> <https://www.eclipse.org/mailman/listinfo/sumo-user> >>> _______________________________________________ >>> sumo-user mailing list >>> sumo-user@eclipse.org <mailto:sumo-user@eclipse.org> >>> To unsubscribe from this list, visit >>> https://www.eclipse.org/mailman/listinfo/sumo-user >>> <https://www.eclipse.org/mailman/listinfo/sumo-user> >>> >>> >>> _______________________________________________ >>> sumo-user mailing list >>> sumo-user@eclipse.org <mailto:sumo-user@eclipse.org> >>> To unsubscribe from this list, visit >>> https://www.eclipse.org/mailman/listinfo/sumo-user >>> <https://www.eclipse.org/mailman/listinfo/sumo-user> >> _______________________________________________ >> sumo-user mailing list >> sumo-user@eclipse.org <mailto:sumo-user@eclipse.org> >> To unsubscribe from this list, visit >> https://www.eclipse.org/mailman/listinfo/sumo-user >> <https://www.eclipse.org/mailman/listinfo/sumo-user> >> >> >> _______________________________________________ >> sumo-user mailing list >> sumo-user@eclipse.org <mailto:sumo-user@eclipse.org> >> To unsubscribe from this list, visit >> https://www.eclipse.org/mailman/listinfo/sumo-user >> <https://www.eclipse.org/mailman/listinfo/sumo-user> > _______________________________________________ > sumo-user mailing list > sumo-user@eclipse.org <mailto:sumo-user@eclipse.org> > To unsubscribe from this list, visit > https://www.eclipse.org/mailman/listinfo/sumo-user > <https://www.eclipse.org/mailman/listinfo/sumo-user> > > > _______________________________________________ > sumo-user mailing list > sumo-user@eclipse.org > To unsubscribe from this list, visit > https://www.eclipse.org/mailman/listinfo/sumo-user
_______________________________________________ sumo-user mailing list sumo-user@eclipse.org To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/sumo-user