1). You can only set one 'effort' attribute which use used for routing 'by effort'. However, you may set this value for separately for individual vehicles using vehicle.setEffort instead of edge.setEffort. Also, the effor value may vary over time (either function takes optional arguments for setting the time range).
2) traci.edge.setEffort, traci.vehicle.setEffort 3) It means, when defining a weights file you do not have to set a value for all edges. But of course, you can do it if you want. 4) via traci, use vehicle.rerouteEffort. If you use duarouter, this can be done by using option --weight-attribute and setting into to anything besides 'traveltime' regards, Jakob 2017-05-01 19:30 GMT+02:00 Ankur Sarker <[email protected]>: > Thanks for your prompt reply. > > I would like to ask some follow-up questions from your second response. > > 1. I can see that it is possible to add costume travel time using the > TraCI python interface (http://sumo.dlr.de/wiki/TraCI/Change_Edge_State). > However, is it possible to add multiple attributes for a single edge? I > can only see three functions (adaptTravelTime, setEffort, setSpeed) there. > > 2. From this description (http://www.sumo.dlr.de/ > userdoc/Demand/Shortest_or_Optimal_Path_Routing.html#Custom_edge_weights), > I guess I can add multiple edge attributes with their weights. If so. how I > can change these values runtime using TraCI interface? > > 3. Also, I am confused by the following description from the same link ( > http://www.sumo.dlr.de/userdoc/Demand/Shortest_or_ > Optimal_Path_Routing.html#Custom_edge_weights): > Weight files that only contain some of the network edges are permitted. > > Does it mean I can not set attributes for all edges? > > 4. Finally, when I try to re-route or find shortest path, how to specify > that I want to consider some other (user-defined) attributes instead of > travel time? > > > > Best, > Ankur > > > > On Mon, May 1, 2017 at 12:12 PM, Jakob Erdmann <[email protected] > > wrote: > >> Hello, >> 1) marouter can compute alternative paths but tries to find 'true >> alternatives' in the sense of avoiding too much overlap between >> alternatives. For all possible paths you need to write your own algorithm. >> For finding the shortest path you can use duarouter or traci. There are >> also some python functions in tools (grep for dijkstra). >> >> 2) >> The individual assignments of edge weights is possible. It is somewhat >> simpler to conflate costs with travel times and set custom travel times for >> each edge but it is also possible to set costs independently of travel >> times and route by costs (this makes sense if costs change over time while >> driving). >> See http://sumo.dlr.de/wiki/Simulation/Routing >> >> regards, >> Jakob >> >> 2017-05-01 17:01 GMT+02:00 Ankur Sarker <[email protected]>: >> >>> Hi, >>> >>> Is there any way I can track down all possible paths from source edge to >>> destination edge? I guess there is an option for finding the shortest >>> path. >>> >>> I have another question, is it possible to add extra metric of an edge? I >>> want to set some extra things of an edge like travelling time, travelling >>> cost, energy consumption. >>> >>> Thanks for your time! >>> >>> Best, >>> A. Sarker >>> ------------------------------------------------------------ >>> ------------------ >>> Check out the vibrant tech community on one of the world's most >>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot >>> _______________________________________________ >>> sumo-user mailing list >>> [email protected] >>> https://lists.sourceforge.net/lists/listinfo/sumo-user >>> >> >> > ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ sumo-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sumo-user
