- the easiest way to modify the vehicle type in your case is to load an additional xml file that modifies the default vehicle type ( http://sumo.dlr.de/wiki/Definition_of_Vehicles,_Vehicle_Types,_and_Routes#Default_Vehicle_Type ) - to check the right of way at junctions, load your network with NETEDIT and check/correct the node types in proximity to the vehicles that could not depart. What the error message means is basically: the vehicle needs to be able to stop at one of the next intersections so it cannot depart safely with the given speed. If the vehicle had the right-of-way it would be able to depart.
2015-12-15 21:23 GMT+01:00 Nguyen Nguyen <[email protected]>: > Hi Jakob, > > Thank you so much for your reply. I have some following questions: > > 1) regarding the 'cannot close' warning: I can only try --routes-for-all > --keep-unfinished-routes, the option --all-end-follower is not allowed(No > option with the name 'all-end-follower' exists), and it still generates > the warning.. > 2) regarding the 'not be able to depart' warning: because I want to keep > the sensor input as most correctly as possible, so I will not touch the > option 2 and 3 (lower the speed at the detectors that are located very > close to an unprioritized intersection, increase the distance between > detector and intersection). > - For option 4: add a speed distribution (attribute speedDev) to the > vehicle type , the route file is generated by dfrouter. I only use the > default vehicle type without specifying vType. For example, if I want to > add *speedFactor*=1, *speedDev*=0.1 to the file, how can I set these > values? > - For option 1: make sure that junctions have the correct right-of-way. > Currently I only use netconvert to convert osm map into file net.xml. How > can I specify the type of junction for the whole network? > > Thank you. > > Best regards, > > Tran > > > > > > On Monday, December 14, 2015 11:34 PM, Jakob Erdmann < > [email protected]> wrote: > > > Hello, > thanks for reporting this contradiction in the documentation. It is now > fixed. > > 1) regarding the 'cannot close' warning. See > http://sumo.dlr.de/wiki/Demand/Routes_from_Observation_Points#Computing_Routes > 2) regarding the 'not be able to depart' warning you may either > - make sure that junctions have the correct right-of-way ( > http://sumo.dlr.de/wiki/Networks/Building_Networks_from_own_XML-descriptions#Node_types > ) > - lower the speed at the detectors that are located very close to an > unprioritized intersection > - increase the distance between detector and intersection > - add a speed distribution (attribute speedDev) to the vehicle type ( > http://sumo.dlr.de/wiki/Definition_of_Vehicles,_Vehicle_Types,_and_Routes#Default_Vehicle_Type > ) > > > regards, > Jakob > > 2015-12-14 18:10 GMT+01:00 Nguyen Nguyen <[email protected]>: > > Hi Jakob, > > Thanks to your link, I created both routes.rou.xml and emitters.rou.xml > and the simulation. However, I got a lot of warnings "Warning: Could not > close route for...", and then when I run the simulation, I got a lot of > errors "Error: Vehicle 'emitter_...' will not be able to depart using the > given velocity (junction too close)!". Is there anything that I can do > regarding this? > > Thank you. > > Best, > > Tran > > > > On Monday, December 14, 2015 7:14 AM, Nguyen Nguyen < > [email protected]> wrote: > > > Hi Jakob, > > Thanks for your reply. In the flow part, it is mentioned that "Since > version 0.12.3, vehicles are generated as part of the route definitions as > is standard in the rest of the SUMO suite of applications. In future > releases, the use of emitters will not be supported at all.". So do I not > need to generate emitter output file? > > I did use -a to generate the fcd file: > > sumo -n LA_Arterial.net.xml -a routes.rou.xml --fcd-output.geo true > --fcd-output LA_Arterial.xml > > Thank you for your clarification. > > Best, > > Tran > > > > On Monday, December 14, 2015 3:49 AM, Jakob Erdmann < > [email protected]> wrote: > > > You need to use additional options to generate vehicles along with the > routes. > See > http://sumo.dlr.de/wiki/Demand/Routes_from_Observation_Points#Saving_Flows_and_other_Values > and > http://sumo.dlr.de/wiki/Demand/Routes_from_Observation_Points#How_to_include_the_files > regards, > Jakob > > 2015-12-14 8:02 GMT+01:00 Nguyen Nguyen <[email protected]>: > > Hello All, > I used dfrouter to generate a route file, the route file was generated > with ~ 10000 trips, however, when I used the route file to generate the fcd > output, there is no information generated (it stopped at time step 0.00). I > attached the route file. Would you please give me some advices? > Thank you. > Best regards, > Tran > > ------------------------------------------------------------------------------ > > _______________________________________________ > sumo-user mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/sumo-user > > > > > > > > > > ------------------------------------------------------------------------------ _______________________________________________ sumo-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sumo-user
