Open 1010617348 opened 2 months ago
@robertalms ?
Hi @1010617348, I think you asked a fairly similar question in #13920.
Would it be an option for you to simply set the d0 = 0
in line 177 of the ACC and compile SUMO locally yourself?:
https://github.com/eclipse-sumo/sumo/blob/d313ef5340596673194e97d50f39f8d1b8f19310/src/microsim/cfmodels/MSCFModel_ACC.cpp#L177
I'm not sure the spacing margin is even implemented or tested for the CACC.
Regarding the different gaps based on vTypes: That seems to be the case only for CACC. The CACC is designed for connected platooning, therefore vehicles of the similar vType CACC allow for smaller gaps, whereas gaps to different, non-connected vTypes are larger.
Again, the standstill/approaching behavior of the ACC/CACC is not solidly validated, and the minGap concept of SUMO is not necessarily considered in those models. Due to limited resources, we haven't explored these issues further, but help is always welcome. ;)
Thank you for your reply and attention. I observe that the param "caccVehicleMode" will change from "CC" to “ACC” when CACC follows non-CACC. I would like to know how the gap control is carried out (literatures, codes or rules) after the “caccVehicleMode” change. Because unlike ACC, the gap (gap to front vehicle if halting) of CACC following other types of vehicles seems to be irregular?
Add your issue description here.
If possible, upload an example that shows your problem.
**SUMO-version:1.20.0
**operating system:Windows 10
When vehicles are queuing up, I have noticed that the gap maintained by ACC and CACC to the front vehicle always does not match the set “MinGap” and the gap changes with the type of front vehicle. Is this caused by the "Dynamic Spacing Margin"? If so, is there a way to disable the "Dynamic Spacing Margin" control?