-
Notifications
You must be signed in to change notification settings - Fork 682
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
Interface to human-machine cooperation #891
Labels
component:planning
Route planning, decision-making, and navigation. (auto-assigned)
type:new-feature
New functionalities or additions, feature requests.
Comments
rej55
added
the
component:planning
Route planning, decision-making, and navigation. (auto-assigned)
label
May 12, 2022
BonoloAWF
added
the
type:new-feature
New functionalities or additions, feature requests.
label
May 18, 2022
This was referenced May 27, 2022
7 tasks
7 tasks
This pull request has been automatically marked as stale because it has not had recent activity. |
@rej55 Are there anything to do for this issue? |
9 tasks
kminoda
pushed a commit
to kminoda/autoware.universe
that referenced
this issue
Oct 2, 2023
feat(intersection): use planned velocity from upstream modules (autowarefoundation#5156)
iwatake2222
pushed a commit
to iwatake2222/autoware.universe
that referenced
this issue
Jan 17, 2025
… length threshold (autowarefoundation#891) * feat(avoidance): wait next shift approval until the ego reaches shift length threshold Signed-off-by: satoshi-ota <satoshi.ota928@gmail.com> * fix(avoidance): param description Signed-off-by: satoshi-ota <satoshi.ota928@gmail.com> --------- Signed-off-by: satoshi-ota <satoshi.ota928@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
component:planning
Route planning, decision-making, and navigation. (auto-assigned)
type:new-feature
New functionalities or additions, feature requests.
Checklist
Description
Develop an interface to compensate decisions from Autoware.
Purpose
Operating an autonomous driving system, it often happens that the perception results are unreliable.
This causes a unsafe planning.
However, it is difficult to get perfect perception results.
So, some ways to compensate decisions are needed.
To achieve a safety operation under the uncertain perception, approving for decisions is one of the way.
Possible approaches
Develop an interface class to cooperation.
There are many situations to need decisions with perception results.
So, it is difficult to develop interfaces individually.
In this task, we aim to achieve the purpose by developing an interface class to cooperation.
After developing, we can integrate individual scenes to request a cooperation for compensate decisions.
Definition of done
The text was updated successfully, but these errors were encountered: