-
Notifications
You must be signed in to change notification settings - Fork 3.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Investigate Turn Function #2918
Comments
If I copy/paste the turn function and the constants into a small test Lua script, I get:
The output I get is:
Comparing this to our old turn function, where the values would be:
The major finding from my test driving for #2849 were:
The new turn function increases the turn cost from where we had it, penalizes shallow turns less, and doesn't penalize very sharp turns as heavily. Overall, this better models actual timings from real driving than what we had. What's missing here are factors unrelated to the angle - stop signs, traffic crossing, road speeds. You've already noted that we should penalize crossing traffic. I made a start on extending the data available to the turn function with this PR: #2822. The factors that seem worth including are:
Right now, all we've got is the angle :-( |
Ok is seems like the function is behaving as expected: turn penalties are higher than they were before? Any more next actions or should we close and continue tracking on #2822 ? |
Talking about more improvements to turn functions in #2822. |
@danpat, what's the idea behind using the sigmoid function? |
Our new turn function is providing very low cost for turns. Measured in seconds, we currently see the following turn cost per angle:
All timings are in seconds, assuming 180 degree as going straight, 0-179 as right, 181-359 as left turns.
All these values are the result of our new function that we have introduced in #2849.
The resulting ways feature more turns and have a lower (unrealistic) ETA.
We need to investigate here to find better turn cost, again.
One way we could improve for left-turns is potentially considering #2912.
The text was updated successfully, but these errors were encountered: