| Re: [sumo-user] Gathering parking delays info from simulations |
Hello everyone :) I'm my quest to compute the parking delays, I'm dealing with a strange output from vehroute. I used the option to have the exit time from every edge, and I was assuming that I would have found a time for each edge. In the attached file, you can see that I have 165 edges in the final route but only 127 exit times. I have no idea on how to associate them.. Any ideas? All the Best! Lara On Mon, 11 Jun 2018 23:49:52 +0200 Jakob Erdmann <namdre.sumo@xxxxxxxxx> wrote: > - arrival attribute should only ever be missing when vehicles are still > running at the end of the simulation and the option > --vehroute-output.write-unifinished is set > - parkingReroute may take place on the rerouter edge(s) and also on the > parkingArea edge (even if it is not among the rerouter edges) > - The tripinfo output includes the stopTime which lists all the time a > vehicle spend with an intentional stop (including parking). > - you could use option --stop-output which records all intentional stops ( > http://sumo.dlr.de/wiki/Simulation/Output/StopOutput) > > cheers, > Jakob > > 2018-06-11 23:39 GMT+02:00 Lara CODECA <lara.codeca@xxxxxxxxxx>: > > > Thanks for the suggestion, Jakob. > > > > I'm filtering the vehroute file looking for only the vehicles that I know > > have to stop in a > > parking area. Doing this I noticed that out of 17335 vehicles that I know > > have to stop: > > - 4262 have no arrival tag in the vehroute, > > - 6736 the edge with the rerouter was not among the replacedOnEdge edges. > > How this is possible? > > > > Given that in the tripinfo the duration includes the time they spend > > parked, I have no idea on how > > to actually isolate the time between the first larking lot full and the > > actual parking found. > > In the case of a person trip, I have the arrival, but for a normal vehicle? > > > > Thanks again for the help, > > Lara > > > > On Mon, 11 Jun 2018 12:11:09 +0200 Jakob > > Erdmann <namdre.sumo@xxxxxxxxx> wrote: > > > > > Hello, > > > I've taken up your suggestion (other reasons for rerouting could be > > initial > > > trip routing and TraCI): > > > https://github.com/eclipse/sumo/issues/4204 > > > For now you could try to distinguish between the cases based on the > > > vehicles departure time and the rerouting device period > > > > > > regards, > > > Jakob > > > > > > 2018-06-11 12:05 GMT+02:00 Lara CODECA <lara.codeca@xxxxxxxxxx>: > > > > > > > Thank you, Jakob. > > > > > > > > I'm going to try to do this, I just have many route changes because I > > use > > > > the routing devices too. > > > > Feature request: would it be hard to add (in vehroute) the reason that > > > > triggered the route change > > > > (routing device or road rerouter - or aother that I don't really know)? > > > > > > > > Regards, > > > > Lara > > > > > > > > On Mon, 11 Jun 2018 10:45:29 +0200 > > > > Jakob Erdmann <namdre.sumo@xxxxxxxxx> wrote: > > > > > > > > > Vehroute output includes information on time and place of route > > changes > > > > and > > > > > should be sufficient to figure this out. > > > > > regards, > > > > > Jakob > > > > > > > > > > 2018-06-11 9:44 GMT+02:00 Lara CODECA <lara.codeca@xxxxxxxxxx>: > > > > > > > > > > > Dear All, > > > > > > > > > > > > I have a scenario in which every parking area has rerouters in > > order to > > > > > > select other parkings if > > > > > > the selected one is full. > > > > > > > > > > > > I need to measure how long does it take from the first parking > > lot > > > > full to > > > > > > the final > > > > > > available parking lot (I'm assuming it may happen more than once). > > > > > > Given that I have 50K+ entities (pedestrian and vehicles), I > > would > > > > like to > > > > > > avoid using TraCI for > > > > > > each vehicle every timestamp. If I can have an association > > (timestamp - > > > > > > rerouter - VehID), it would > > > > > > be enough for me to do my computations, but from the rerouter I > > saw > > > > only > > > > > > counters, not vehID. > > > > > > > > > > > > Thanks for the help! > > > > > > > > > > > > Lara > > > > > > > > > > > > -- > > > > > > Lara CODECA > > > > > > Postdoc > > > > > > Tel : 04.93.00.81.51 > > > > > > > > > > > > EURECOM > > > > > > Campus SophiaTech > > > > > > http://www.eurecom.fr/ > > > > > > _______________________________________________ > > > > > > sumo-user mailing list > > > > > > sumo-user@xxxxxxxxxxx > > > > > > To change your delivery options, retrieve your password, or > > unsubscribe > > > > > > from this list, visit > > > > > > https://dev.eclipse.org/mailman/listinfo/sumo-user > > > > > > > > > > > > > > > > > > > > > > -- > > > > Lara CODECA > > > > Postdoc > > > > Tel : 04.93.00.81.51 > > > > > > > > EURECOM > > > > Campus SophiaTech > > > > http://www.eurecom.fr/ > > > > _______________________________________________ > > > > sumo-user mailing list > > > > sumo-user@xxxxxxxxxxx > > > > To change your delivery options, retrieve your password, or unsubscribe > > > > from this list, visit > > > > https://dev.eclipse.org/mailman/listinfo/sumo-user > > > > > > > > > > > > -- > > Lara CODECA > > Postdoc > > Tel : 04.93.00.81.51 > > > > EURECOM > > Campus SophiaTech > > http://www.eurecom.fr/ > > _______________________________________________ > > sumo-user mailing list > > sumo-user@xxxxxxxxxxx > > To change your delivery options, retrieve your password, or unsubscribe > > from this list, visit > > https://dev.eclipse.org/mailman/listinfo/sumo-user > > -- Lara CODECA Postdoc Tel : 04.93.00.81.51 EURECOM Campus SophiaTech http://www.eurecom.fr/
Attachment:
exitTimes.issues.xml
Description: XML document