-
Notifications
You must be signed in to change notification settings - Fork 33
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(detection_area)!: suppression of giving up stopping #1631
Conversation
Please add the following to 'How was this PR tested?' section |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@yuki-takagi-66
Please change the base branch from beta/v0.3.19 to beta/v0.3.20.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Link your internal JIRA managed tickets to maintain traceability.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since it is difficult to understand what specific changes are being referred to by "sync latest feature", please set a PR title that mentions the specific feature.
Signed-off-by: Yuki Takagi <[email protected]>
db407e1
to
b7f9c8c
Compare
The basic design document clearly states that "please consider the detailed design," but this PR makes no mention of the detailed design. Or, if you have decided that implementing it as per the basic design document is fine, please state that in the Description field. |
Quality Gate passedIssues Measures |
Please justify all changes in the PR (show that the changes are necessary and sufficient). In the "Description" field, clearly list the features and clarify how they correspond to the implementation. |
In the "How was this PR tested?" field, please include not only the URL, but also a summary of the results and your judgement as the PR submitter as to whether the changes to this PR are appropriate. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
Description
This PR implements functionality to enable stopping when obstacles are detected within the DA (Detection Area) after passing the stop line.
The implemented code leverages existing features from autowarefoundation to meet the requirements specified in the documentation.
This PR is implemented with reference to the following PRs:
Implementation Details
The correspondence between design requirements and implementation is as follows:
Related links
Parent Issue:
How was this PR tested?
Since there are no changes to the Interface*, we determined that functional testing of this DetectionAreaModule using the following Test criteria is sufficient:
I confirm that the specified tests have passed and no critical defects were found in the specified design.
*) Topic names, Msg definitions, SceneModuleInterface
Notes for reviewers
None.
Interface changes
None.
Effects on system behavior
None.