Thanks Jakob, for your explanation. Things are becoming more clear now. Just a follow up question - is Accel2Speed (underlined in the attached image) the change in speed (deceleration/acceleration) for the next timestamp? So that v would be the next timestamp speed?
Also, as you mentioned in the previous email, if accelerationAdvices are present when a vehicle is blocked or blocking someone from lane changing, does this mean that the vehicle that is trying to merge will also change its speed (not only the vehicle that is allowing the merge)? Thank you so much again! ________________________________ From: sumo-user <[email protected]> on behalf of Jakob Erdmann <[email protected]> Sent: Wednesday, November 3, 2021 4:23 AM To: Sumo project User discussions <[email protected]> Subject: Re: [sumo-user] Understanding lcCooperativeSpeed Parameter 1) this function is called in every simulation step (but accelerationAdvices are only present if the vehicle is blocked from changing lanes or is itself blocking someones lane change) 2) Yes. 5. - MAGIC_offset increases the space reserved for a blocked vehicle and thereby reduces the likelyhood of a failed merge - the first red block relates to simulations with option --step-method.ballistic: https://sumo.dlr.de/docs/Simulation/Basic_Definition.html#defining_the_integration_method - the second red block is optional debug output which doesn't influence the simulation regards, Jakob Am Di., 2. Nov. 2021 um 20:15 Uhr schrieb Bae, Jong In <[email protected]<mailto:[email protected]>>: Jakob, Thank you so much for the links. Based on the links provided, it seems like the lcCooperativeSpeed gives a coopWeight that reduces the desired speed (wanted variable). 1. When is this function called? Based on the simulation, it seems like this function is called if the merging vehicle is adjacent lane and between the subject vehicle and the leading vehicle? 2. Am I understanding these variables correctly? * wanted = desired speed * safe = stopping speed to allow merge * nVsafe = final speed with lcCooperativeSpeed considered * gotOne = indicates a condition where lcCooperativeSpeed is affecting the vehicle speed 3. What are the roles of MAGIC_offset and the highlighted sections in the screenshots? (there is a mention of possible failure in lane change) Also, I'm using an older version (1.8.0). This is to have consistency in the version I used for my previous experiments in my project. So that my model doesn't behave differently due to different versions of SUMO. Thank you! ________________________________ From: sumo-user <[email protected]<mailto:[email protected]>> on behalf of Jakob Erdmann <[email protected]<mailto:[email protected]>> Sent: Tuesday, November 2, 2021 3:28 AM To: Sumo project User discussions <[email protected]<mailto:[email protected]>> Subject: Re: [sumo-user] Understanding lcCooperativeSpeed Parameter Hello, the code for lcCooperativeSpeed is at https://github.com/eclipse/sumo/blob/c16317561f2844d18dca1d0e14d96ce94b96c544/src/microsim/lcmodels/MSLCM_LC2013.cpp#L265-L277 However, the code that handles the situation in the screenshot is at https://github.com/eclipse/sumo/blob/c16317561f2844d18dca1d0e14d96ce94b96c544/src/microsim/lcmodels/MSLCM_LC2013.cpp#L240-L263 Basically, vehicle 2 should leave enough space so vehicle 1 can merge regardless of lcCooperative. In my own test with the stated parameters I was unable to replicate the situation from your screenshot. Which version of SUMO are you using? regards, Jakob Am Mo., 1. Nov. 2021 um 16:23 Uhr schrieb Bae, Jong In <[email protected]<mailto:[email protected]>>: Hello, I'm trying to understand how different values of lcCooperativeSpeed affects the vehicle behavior. I'm having a hard time locating the source code for lcCooperativeSpeed. Could you please point me to a link of the source code? Also, I'm trying to understand one behavior that I saw in the simulation. In this simulation, only one vehicle type is used - and they all have lcCooperative=0 and lcCooperativeSpeed=0.75. In the attached screenshot, vehicle #2 slows down to let vehicle#1 merge but vehicle#1 fails to. This behavior repeatedly occurs with the following vehicles on the exit lane. I'm assuming vehicle#1 is unable to make the merge due to a small gap. I'm just trying to understand how different lcCooperativeSpeed values affect this decision process. Any explanation or help to understand would be appreciated! Thanks! _______________________________________________ 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
