Thanks, good to know 😊 Is there any other possibility to start the vehicle *now* without passing the simulation time?
Von: [email protected] <[email protected]> Im Auftrag von Jakob Erdmann Gesendet: Mittwoch, 13. Mai 2020 11:11 An: Sumo project User discussions <[email protected]> Betreff: Re: [sumo-user] Problem with TraCI in SUMO 1.6.0 The legacy behavior was a bug and the change is intended. The semantics of depart=triggered is to let the vehicle depart once a person rides it. Most likely you do not have such riding persons in your simulation and thus the vehicles are never inserted. See https://sumo.dlr.de/docs/Definition_of_Vehicles,_Vehicle_Types,_and_Routes.html#depart regards, Jakob Am Mi., 13. Mai 2020 um 10:59 Uhr schrieb Schrab, Karl <[email protected]<mailto:[email protected]>>: Hi, We are using the legacy command to add vehicles (0x80) and passing “-1” (triggered) as our client decides when to add the vehicle. If we are using a fixed depart time (e.g. if we just use the current simulation time), everything works fine! I had a slightly deeper look and this behavior is also true for the command (0x85) when using depart=”triggered” and also for the python function traci.vehicle.add(…, depart=”triggered”, …). Apparently, this regression is related to the commit https://github.com/eclipse/sumo/commit/4f9f5f7dc9cb2bf98ae06e736bf28cbd16fcad35 Kind regards, Karl Von: [email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>> Im Auftrag von Jakob Erdmann Gesendet: Dienstag, 12. Mai 2020 15:53 An: Sumo project User discussions <[email protected]<mailto:[email protected]>> Betreff: Re: [sumo-user] Problem with TraCI in SUMO 1.6.0 Hello Karl, nothing related to vehicle.add was changed deliberately. The problem may be related to vehicle insertion. Here are things you could try: - force the vehicle into the network using vehicle.moveTo or vehicle.moveToXY (if that works the issue is with insertion) - activate debugging code in MSLane.cpp:70 ( DEBUG_INSERTION) and activate the line /#define DEBUG_COND2(obj) ((obj != 0 && (obj)->getID() == "yourVehicleID")). This will report the reason why the vehicle 'yourVehicleID' is not being inserted regards, Jakob Am Di., 12. Mai 2020 um 15:38 Uhr schrieb Schrab, Karl <[email protected]<mailto:[email protected]>>: Hi all, We are currently facing problems with TraCI in SUMO 1.6.0. We are using our own Java client to add vehicles, perform simulation steps, and catch subscriptions via TraCI. With the current version of SUMO, the command to add a vehicle (0x80, 0x85 as well) are executed successfully (no error message is logged or returned), however, no vehicle appears in the simulation. Executing simulation steps and retrieving subscriptions for the just added vehicle returns invalid values for all subscribed parameters (-2^30). Again no error log or message that the vehicle is missing, but only those invalid values. In the GUI the vehicle seems to be in the state “loaded”, but it is not displayed or simulated at all. With previous versions, e.g. 1.5.0 or 1.4.0, everything works fine. Has there anything changed in the way to interact/initialize with the simulation using TraCI? Kind regards, Karl _______________________________________________ sumo-user mailing list [email protected]<mailto:[email protected]> To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/sumo-user _______________________________________________ sumo-user mailing list [email protected]<mailto:[email protected]> To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/sumo-user
_______________________________________________ sumo-user mailing list [email protected] To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/sumo-user
