By setting the sumo option --verbose there will be output for each routing algorithm instance recording the total computation time, number of queries, running time per query and explored edges per query.
Am Fr., 1. März 2019 um 10:28 Uhr schrieb tobycannon <[email protected] >: > Hi Sumo users, > I'm currently trying to analyse the different routing methods used within > SUMO with regards to their computation time and memory requirements. > > I'm using python and TraCI currently and I understand how to monitor these > metrics within python. My issue is as I'm just calling the SUMO command > from > within Python I don't understand how to monitor the computation time of the > algorithms for each individual vehicle. > > Could someone possibly point me in the right direction of how best to do > this as from reading a few papers I understand this has been done before. > > Many thanks, > Toby Cannon > > > > -- > Sent from: http://sumo-user-mailing-list.90755.n8.nabble.com/ > _______________________________________________ > sumo-user mailing list > [email protected] > To change your delivery options, retrieve your password, or unsubscribe > from this list, visit > https://www.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://www.eclipse.org/mailman/listinfo/sumo-user
