Jakob Erdmann
Jakob Erdmann
> I thought the double-calculation of freeSpeed and stopSpeed may be changed to one function call like in ... The current code is the result of a recognized issue: https://github.com/eclipse/sumo/issues/1560...
> This would solve this issue and https://github.com/eclipse/sumo/issues/11461. I can do the work. Excellent! Please do. After discussing with @behrisch we concluded that MSCFModel should get a new enum type...
Yes. This way we only need to actively set the new parameter in the context of the adaptLeaveSpeed computations.
I suggest CURRENT_WAIT for the vLinkWait computation. I think the default should still be CURRENT: Calls related to stopping at lane-end or planned stops are always applied. I think adding...
The `followSpeed` call from 9533f3912f8f7446432400a3fd50e961c0d6979f also requires the flag `FUTURE`
I don't like the idea of calling the method a third time, just to signal the 'correct' call. I'd rather invent another flag (CURRENT_LOWER_BOUND) which signals that the call establishes...
I was thinking that your model could save all the calls with the new CURRENT_LOWER_BOUND_FLAG and then integrate them in a different manner. Or maybe even just ignore them (and...
As far as I see it, the new context parameter should not make things worse than the old situation where the context is lacking. and with the new CURRENT_WAIT context...
@behrisch apologies if this is a duplicate
RHEL 7.9 