[sumo-user] Error: Answered with error to command 0xa4: Vehicle 'XXXX' is not known.

Hi there, I am using the Flow toolbox and SUMO for the purposes of reinforcement learning driving policies. Previous users have published the same error message of a vehicle not being known but I am unsure if we have the same root cause. Context: I am navigating an RL vehicle through intersecti

Re: [sumo-user] Regarding Sumo with jupedsim running

I had same problem I solved that installing the development version. The binaries and the sources are in: https://sumo.dlr.de/docs/Downloads.php in the middle of the page. Regards Manuel De: sumo-user En nombre de Aligeti, Divya via sumo-user Enviado el: viernes, 9 de febrero de 2024 09:34 a. m

[sumo-user] Loading the sumo files

TCS Confidential Hi Team, Can we run the config file after running in the cmd. I want to extract more information using traci at the end of the simulation, where i don't want to run the config file in traci which causes delay. My question is I want to run sumo file initially using command prom

Re: [sumo-user] Change values for W99 carFollowingModel

Dear Parisa, just add attributes of the same names to the vType declaration (see docs ). Something like this: Best regards Mirko -Original-Nachricht- Betreff: [sumo-u

[sumo-user] Change values for W99 carFollowingModel

Dear Community, I have a model the "W99" car follow model. I want to change the default values for the parameters like cc1 and cc2. Can you guide me on how to do that? Best regards, Parisa ___ sumo-user mailing list sumo-user@eclipse.org To unsubscribe

Re: [sumo-user] Assing device parameters per vehicle type

Excellent! thank you very much! From: Mirko Barthauer Sent: Friday, February 9, 2024 11:54 AM To: Ivan Postigo ; Sumo project User discussions Subject: AW: [sumo-user] Assing device parameters per vehicle type Hi Ivan, in the general case just add a param ch

Re: [sumo-user] Assing device parameters per vehicle type

Hi Ivan, in the general case just add a param child tag with attributes key="" ("device.driverstate.headwayErrorCoefficient" in your example) and value="" ("0.5" in your case). The general rule is that more specific definitions prevail: vehicle types override global options and vehicles overri

Re: [sumo-user] Assing device parameters per vehicle type

Thanks Mirko, How about the driver state device? I would like for example vehicle 1 to have a "headwayErrorCoefficient = 0.5" and vehicle 2 to have "headwayErrorCoefficient=0.75" just as an example. the global option is : --device.driverstate.headwayErrorCoefficient in the route file the, what

Re: [sumo-user] Assing device parameters per vehicle type

Hi Ivan, while it is possible for other devices to define them like you showed below, the FCD device is implemented differently. You can restrict output only by the global options you can find in the options list . Best regards Mirko ---