Skip to content
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

feat: handling invalid lanelet in RTC #95

Conversation

ahmeddesokyebrahim
Copy link

@ahmeddesokyebrahim ahmeddesokyebrahim commented Mar 21, 2023

PR Type

  • New Feature

Related Links

Discussion

Issue

Relevant PRs

Description

This PR is to add the needed code for handling invalid lanelet by RTC

Review Procedure

For compiling and testing this PR, all PRs in related links section need to be taken into consideration.
Merge sequence can be found here

Remarks

Pre-Review Checklist for the PR Author

PR Author should check the checkboxes below when creating the PR.

Checklist for the PR Reviewer

Reviewers should check the checkboxes below before approval.

  • Commits are properly organized and messages are according to the guideline
  • Code follows coding guidelines
  • (Optional) Unit tests have been written for new behavior
  • PR title describes the changes

Post-Review Checklist for the PR Author

PR Author should check the checkboxes below before merging.

  • All open points are addressed and tracked via issues or tickets
  • Write release notes

CI Checks

  • Build and test for PR / build-and-test-pr: Required to pass before the merge.
  • Build and test for PR / clang-tidy-pr: NOT required to pass before the merge. It is up to the reviewer(s).
  • Check spelling: NOT required to pass before the merge. It is up to the reviewer(s). See here if you want to add some words to the spell check dictionary.

@yukkysaito
Copy link
Contributor

@isamu-takagi Can you check this PR?

@isamu-takagi isamu-takagi requested a review from tkhmy May 8, 2023 01:33
@isamu-takagi
Copy link
Collaborator

@tkhmy Can you review this PR?

@tkhmy
Copy link
Contributor

tkhmy commented May 8, 2023

@ahmeddesokyebrahim
Hi, based on your use case, the no_drivable_lane should not be approve to drive autonomously. So mean the no_drivable_lane should be keep inactive along the no drivable lane?
Do it have the case that autoware think it is safe and auto active it?

@ahmeddesokyebrahim
Copy link
Author

Thanks @tkhmy san for your comment.
Actually I was not able to understand your questions. May you please clarify or elaborate more about what you mean ?

@tkhmy
Copy link
Contributor

tkhmy commented May 8, 2023

Thanks @tkhmy san for your comment. Actually I was not able to understand your questions. May you please clarify or elaborate more about what you mean ?

@ahmeddesokyebrahim
The RTC is used for this purpose, as you can see, it does not publish the stop wall, instead, it let user to handle the stop wall behavior, user can decide whether to stop or go.

publish the decision status of behavior planning modules and receive execution command from external of an autonomous driving system.
https://autowarefoundation.github.io/autoware.universe/main/planning/rtc_interface/

In your case, you do not want the no_driving_lane stop wall to be cancel, instead you will want the user to manually drive the vehicle to pass over the no driving area. Or it is okay that user able to cancel the no_driving_lane stop wall and continue drive autonomously?

For the auto_mode, it handle in this module, if autoware think the module is safe, and the auto_mode is turn on, it will decide to continue driving in the no_driving_lane

@ahmeddesokyebrahim
Copy link
Author

Thanks for your clarification @tkhmy san.

In this module case, we want the user to manually drive the vehicle to pass over the no_driving_lane and it is not safe to drive autonomously during the no_driving_lane (i.e., any autonomous driving request should be cancelled and the vehicle shall stay in its place).

Is my implementation doing it like that or do I need to change anything ?

@mitsudome-r
Copy link
Collaborator

mitsudome-r commented May 11, 2023

@isamu-takagi @tkhmy I think the objective here is to just notify the driver to override the vehicle. Were there any interface to do that at the moment? (i.e. request to override)

@tkhmy
Copy link
Contributor

tkhmy commented May 11, 2023

In this module case, we want the user to manually drive the vehicle to pass over the no_driving_lane and it is not safe to drive autonomously during the no_driving_lane (i.e., any autonomous driving request should be cancelled and the vehicle shall stay in its place).
Is my implementation doing it like that or do I need to change anything ?

@ahmeddesokyebrahim I think it can be discuss, but for current RTC, the user can approve the no_driving_lane when the it is show

I think the objective here is to just notify the Driver to override the vehicle. Were there any interface to do that at the moment? (i.e. request to override)

@mitsudome-r I think there is no interface to show the override, @isamu-takagi how do you think?

@isamu-takagi
Copy link
Collaborator

@ahmeddesokyebrahim @mitsudome-r @tkhmy
RTC is only a support function during autonomous driving, and switching to manual driving is not covered. As @tkhmy said, I think this should be implemented as a new API for takeover request/request to intervene (TOR/RTI). This API will be classified as fail-safe.

@isamu-takagi
Copy link
Collaborator

isamu-takagi commented May 11, 2023

Created an issue autowarefoundation/autoware#3487 for new API.

@ahmeddesokyebrahim
Copy link
Author

@mitsudome-r san : Shall I wait for the new API to be implementation and reflect that in the no_drivable_lane module. Or can we proceed for now until it is implemented, tested, and merged then we can open a new issue for that on no_drivable_lane module ?

Signed-off-by: AhmedEbrahim <ahmed.a.d.ebrahim@gmail.com>
@ahmeddesokyebrahim
Copy link
Author

As RTC handling has been removed from this feature and this PR is no longer having any files changes, I am closing this PR.

@ahmeddesokyebrahim ahmeddesokyebrahim deleted the 3308-feat-handle-invalid-lanelets branch June 14, 2023 19:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants