From: Quentin B. <que...@uc...> - 2015-06-04 11:04:12
|
Hi Jakob, Thanks for you help. There is no more crash when moveTo follows a add command. However is this normal behaviour that moveTo set the speed of the vehicle to 0 instead of keep the original speed ? I tried to set back the speed of the vehicle with setSpeed, modify the SpeedMode so that it won't check for the acceleration and set the speed to -1 after the simulation step so that the vehicle would follow the driver model again. However, it forces me to input to setSpeed the speed that the vehicle should normally have at the next step which is context dependant and cannot be done accurately. Is there a way to prevent moveTo from setting the speed to 0 ? Thanks again, Regards, Quentin 2015-06-03 22:36 GMT+01:00 Jakob Erdmann <nam...@go...>: > This crash is fixed in the latest svn revision [18473]. > regards, > Jakob > > 2015-06-03 13:26 GMT+02:00 Quentin Bragard <que...@uc...> > : > >> Hi Jakob, >> >> Thanks for your quick answer. >> I tried your solution on a small example but unfortunately, following a >> "add" directly by a "moveTo" makes SUMO crash. It looks strongly related to >> the ghost-like vehicles email I sent recently and the defect you reported ( >> http://sumo.dlr.de/trac.wsgi/ticket/1809). >> Right after calling the function "add" the vehicle is in the ghost-state >> and calling the function "moveTo" makes SUMO crash. The vehicle is only >> added properly on the road after the call of "simulationStep" function, >> which again creates the gap that I try to avoid. >> >> I've joined the simple scenario I used to test the function. It's based >> on the Hello tutorial, I just remove the running vehicle then try to add it >> again without position gap. >> >> Regards, >> Quentin >> >> 2015-06-03 10:28 GMT+01:00 Jakob Erdmann <nam...@go...>: >> >>> Hello, >>> it should be possible to accomplish what you want be following up the >>> 'add' command with a 'move to' (0x5c). This should instantly insert the >>> vehicle at the given lane and position and it would then do regular >>> movements in the same simulation step. >>> regards, >>> Jakob >>> >>> 2015-06-02 14:34 GMT+02:00 Quentin Bragard < >>> que...@uc...>: >>> >>>> Hi everyone, >>>> >>>> I'm currently working on a distributed version of SUMO and when I >>>> transfer >>>> a vehicle from one sumo instance to another, it takes one step to be >>>> inserted with TraCI "add vehicle" function which leads to a gap if I >>>> compare SUMO and my distributed version. As I cannot add a vehicle in >>>> the >>>> past nor accurately predict it's future position and speed, I was >>>> thinking >>>> of a specific function which add the vehicle and directly makes it drive >>>> within the same function. How hard would it be to modify SUMO to >>>> implement >>>> this specific "add vehicle" function, pushing the vehicle in the SUMO >>>> list >>>> of existing vehicles? Would you have any advices on how to do that >>>> properly >>>> ? >>>> I remember that I implemented it on SUMO 0.16 for the paper I presented >>>> at >>>> the SUMO conference but it seems that many changes happened in the code >>>> since and it was more tinkering that anything. >>>> >>>> Thanks everyone, >>>> Regards, >>>> Quentin >>>> >>>> -- >>>> Quentin Bragard >>>> Diplômé de l'INSA de Lyon, Département Informatique. >>>> >>>> Ph.D Student in PEL, >>>> University College Dublin >>>> >>>> ------------------------------------------------------------------------------ >>>> _______________________________________________ >>>> sumo-devel mailing list >>>> sum...@li... >>>> https://lists.sourceforge.net/lists/listinfo/sumo-devel >>>> >>> >>> >> >> >> -- >> Quentin Bragard >> Diplômé de l'INSA de Lyon, Département Informatique. >> >> Ph.D Student in PEL, >> University College Dublin >> > > -- Quentin Bragard Diplômé de l'INSA de Lyon, Département Informatique. Ph.D Student in PEL, University College Dublin |