-
Notifications
You must be signed in to change notification settings - Fork 1
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
retune the planner using new human-aware cost functions #92
Labels
expedite
Required for the planner article
Comments
Standard tuning guide: https://kaiyuzheng.me/documents/navguide.pdf |
rayvburn
added a commit
that referenced
this issue
Sep 22, 2023
rayvburn
added a commit
that referenced
this issue
Sep 24, 2023
This issue will remain opened until the final tuning for tests will be established. |
rayvburn
added a commit
that referenced
this issue
Dec 29, 2023
rayvburn
added a commit
that referenced
this issue
Dec 29, 2023
…asonable performance [#92] - tested in, e.g., crossing, overtaking scenarios
rayvburn
added a commit
that referenced
this issue
Dec 29, 2023
…our and reasonable performance [#92]
rayvburn
added a commit
that referenced
this issue
Jan 15, 2024
rayvburn
added a commit
that referenced
this issue
Jan 15, 2024
…asonable performance [#92] - tested in, e.g., crossing, overtaking scenarios
rayvburn
added a commit
that referenced
this issue
Jan 15, 2024
- too high forced the robot to turn very late in the hall eval. scenario
rayvburn
added a commit
that referenced
this issue
Jan 17, 2024
…asonable performance [#92] - tested in, e.g., crossing, overtaking scenarios
rayvburn
added a commit
that referenced
this issue
Jan 17, 2024
- too high forced the robot to turn very late in the hall eval. scenario
rayvburn
added a commit
that referenced
this issue
Jan 17, 2024
…asonable performance [#92] - tested in "passing in front" scenario (TIAGo simulation)
rayvburn
added a commit
that referenced
this issue
Jan 17, 2024
…asonable performance [#92] - reduced the `equisampled_vth` back to 10 as 4% of control loops violated the maximum time for a 4 Hz controller
rayvburn
added a commit
that referenced
this issue
Jan 18, 2024
…asonable performance [#92] - tested in, e.g., crossing, overtaking scenarios
rayvburn
added a commit
that referenced
this issue
Jan 18, 2024
- too high forced the robot to turn very late in the hall eval. scenario
rayvburn
added a commit
that referenced
this issue
Jan 18, 2024
…asonable performance [#92] - tested in "passing in front" scenario (TIAGo simulation)
rayvburn
added a commit
that referenced
this issue
Jan 18, 2024
…asonable performance [#92] - reduced the `equisampled_vth` back to 10 as 4% of control loops violated the maximum time for a 4 Hz controller
rayvburn
added a commit
that referenced
this issue
Jan 19, 2024
…asonable performance [#92] - tested in, e.g., crossing, overtaking scenarios
rayvburn
added a commit
that referenced
this issue
Jan 19, 2024
- too high forced the robot to turn very late in the hall eval. scenario
rayvburn
added a commit
that referenced
this issue
Jan 19, 2024
…asonable performance [#92] - tested in "passing in front" scenario (TIAGo simulation)
rayvburn
added a commit
that referenced
this issue
Jan 19, 2024
…asonable performance [#92] - reduced the `equisampled_vth` back to 10 as 4% of control loops violated the maximum time for a 4 Hz controller
rayvburn
added a commit
that referenced
this issue
Jan 19, 2024
…asonable performance [#92] - reduced the `equisampled_vth` back to 10 as 4% of control loops violated the maximum time for a 4 Hz controller
rayvburn
added a commit
that referenced
this issue
Jan 19, 2024
…asonable performance [#92] - tested in the `crossing` scenario
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
No description provided.
The text was updated successfully, but these errors were encountered: