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(intersection): publish and visualize the reason for dangerous situation to blame past detection fault retrospectively #6143

Conversation

soblin
Copy link
Contributor

@soblin soblin commented Jan 23, 2024

Description

visualization

  • the objects that are judged as UNSAFE are visualized green
  • the objects which:
    • were not detected when ego passed the 1st pass judge line, but now detected collision on the 1st attention lanelet
    • were not detected when ego passed the 2nd pass judge line, but now detected collision while ego is driving
    • are visualized red

In the following image(at [00:30]]), the object is suddenly detected when ego just passed the 1st pass judge line, which is visualized red.
image

In the following image(at [00:38]), the closer object is red because it was not detected when ego passed the 1st pass judge line but the collision is expected on the 1st lane. The second object is green because the collision is expected on the 2nd lanelet and ego is still before the 2nd pass judge line.
image

In the following image(at [00:49]) the object is red because it was not detected when ego passed the 2nd pass judge line but now detected collision.
image

PR6143-2024-01-25_18.39.06.mp4

Objects which was once judged safe when ego passed pass judge line but after that dangerous are visualized yellow.

PR6143-2024-01-26_18.36.32.mp4

diagnosis

For red/yellow targets, following diagnosis is published.

ros2 topic echo -f /planning/scenario_planning/lane_driving/behavior_planning/behavior_velocity_planner/debug/intersection/decision_state

for red objects (objects which was safe at pass judge line passage, but after that dangerous):

data: "intersection1087 : NonOccludedCollisionStop
safety_report:object 4794efb25500b52b8fd1babef3a29715 was not detected when ego passed  \
the 1st pass judge line at 1706260630.4215639,  but now at 1706260632.1230607,  \
collision is detected after 2~3 seconds on the first attention lanelet of type FIRST. \

this object is estimated to have been at x = 89624.45066479736, y = 42268.00315728942 when ego passed  \
the 1st pass judge line(1.7014968395233154 seconds before from now) given the estimated  \
current velocity of 10.010836197709807[m/s]. ego was at x = 89605.2819746634,  \
y = 42312.67526017006 when it passed  the 1st pass judge line so it is the fault of detection side  \
that failed to detect around  48.61106311560853[m] range at that time."

data: 'intersection1087 : OverPassJudge:

  safety_report:object ac14e7d5a9a5c3bb33a0c061dd1bcba7 was not detected when ego passed  \
the 2nd pass judge line at 1706278259.2016559, but now at 1706278260.5038362, collision is detected  \
after 4.5~5.5 seconds on the lanelet of type SECOND.
  this object is estimated to have been at x = 89633.78756886403, y = 42245.2889476135 when ego passed  \
the 2nd pass judge line(1.302180290222168 seconds before from now) given the estimated current velocity \
 10.015088637725798[m/s]. ego was at x = 89604.91505923647, y = 42308.559887111674 when it passed  \
the 2nd pass judge line so it is the fault of detection side that failed to detect around  \
69.5473478802381[m]  range at that time.

  evasive_report:
  the object is expected to approach the collision point by the TTC margin in 1.0004517790830276 seconds,  \
while ego will arrive there in 2.4559680675063786 seconds, so ego needs to accelerate from current velocity \
 2.7144718357721525[m/s] to 7.055480441380711[m/s]

for yellow objects:

data: 'intersection1087 : OverPassJudge:

  safety_report:object f1728040d78dee66064090fca03a3300 was judged as SAFE at time  \
1706261296.8137178 previsouly with the estimated velocity of 3.115632923723282, but now at  \
1706261297.7148507 collision is detected after 6.5~7 seconds on the lanelet of type SECOND  \
with the estimated current velocity of 3.546198745717909

Related links

Tests performed

https://evaluation.tier4.jp/evaluation/reports/7e194bbc-c772-5bc3-bb90-b82326d5a44b?project_id=prd_jt

Notes for reviewers

Interface changes

none

Effects on system behavior

none

Pre-review checklist for the PR author

The PR author must check the checkboxes below when creating the PR.

In-review checklist for the PR reviewers

The PR reviewers must check the checkboxes below before approval.

  • The PR follows the pull request guidelines.
  • The PR has been properly tested.
  • The PR has been reviewed by the code owners.

Post-review checklist for the PR author

The PR author must check the checkboxes below before merging.

  • There are no open discussions or they are tracked via tickets.
  • The PR is ready for merge.

After all checkboxes are checked, anyone who has write access can merge the PR.

@github-actions github-actions bot added the component:planning Route planning, decision-making, and navigation. (auto-assigned) label Jan 23, 2024
@soblin soblin force-pushed the feat/intersection/formalize-safety-responsibility2 branch 2 times, most recently from 5c18236 to 719b2ac Compare January 23, 2024 00:22
@soblin soblin changed the title feat(intersection): formalize safety responsibility for perception and output diag feat(intersection): replace TargetObject with ObjectInfoManager Jan 23, 2024
@soblin soblin changed the title feat(intersection): replace TargetObject with ObjectInfoManager refactor(intersection): replace TargetObject with ObjectInfoManager Jan 23, 2024
@soblin soblin force-pushed the feat/intersection/formalize-safety-responsibility2 branch 6 times, most recently from 633f644 to 0059b83 Compare January 24, 2024 11:01
@soblin soblin force-pushed the feat/intersection/formalize-safety-responsibility2 branch from ab729db to d0c5a35 Compare January 25, 2024 06:11
@soblin soblin force-pushed the feat/intersection/formalize-safety-responsibility2 branch from d0c5a35 to 2695269 Compare January 25, 2024 06:11
@soblin soblin changed the title refactor(intersection): replace TargetObject with ObjectInfoManager feat(intersection): publish and visualize the reason for dangerous situation to blame detection fault retrospectively Jan 25, 2024
@soblin soblin changed the title feat(intersection): publish and visualize the reason for dangerous situation to blame detection fault retrospectively feat(intersection): publish and visualize the reason for dangerous situation to blame past detection fault retrospectively Jan 25, 2024
Signed-off-by: Mamoru Sobue <[email protected]>
@soblin soblin force-pushed the feat/intersection/formalize-safety-responsibility2 branch 2 times, most recently from 0bac9ab to 2962404 Compare January 26, 2024 06:06
@soblin soblin marked this pull request as ready for review January 26, 2024 06:06
@soblin soblin force-pushed the feat/intersection/formalize-safety-responsibility2 branch 2 times, most recently from d8130f6 to 037a641 Compare January 26, 2024 09:55
Signed-off-by: Mamoru Sobue <[email protected]>
@soblin soblin force-pushed the feat/intersection/formalize-safety-responsibility2 branch from 037a641 to 2385604 Compare January 27, 2024 02:09
@soblin soblin added the run:build-and-test-differential Mark to enable build-and-test-differential workflow. (used-by-ci) label Jan 28, 2024
Copy link

codecov bot commented Jan 28, 2024

Codecov Report

Attention: 549 lines in your changes are missing coverage. Please review.

Comparison is base (6bf7532) 14.58% compared to head (2385604) 14.55%.
Report is 15 commits behind head on main.

Files Patch % Lines
...ection_module/src/scene_intersection_collision.cpp 0.00% 246 Missing ⚠️
...elocity_intersection_module/src/object_manager.cpp 0.00% 126 Missing ⚠️
...ity_intersection_module/src/scene_intersection.cpp 0.00% 68 Missing ⚠️
...ehavior_velocity_intersection_module/src/debug.cpp 0.00% 23 Missing ⚠️
...locity_intersection_module/src/decision_result.cpp 0.00% 21 Missing ⚠️
...ion_module/src/scene_intersection_prepare_data.cpp 0.00% 21 Missing ⚠️
...elocity_intersection_module/src/object_manager.hpp 0.00% 20 Missing ⚠️
...tersection_module/src/scene_intersection_stuck.cpp 0.00% 8 Missing ⚠️
...ection_module/src/scene_intersection_occlusion.cpp 0.00% 7 Missing ⚠️
...havior_velocity_intersection_module/src/result.hpp 0.00% 4 Missing ⚠️
... and 3 more
Additional details and impacted files
@@            Coverage Diff             @@
##             main    #6143      +/-   ##
==========================================
- Coverage   14.58%   14.55%   -0.04%     
==========================================
  Files        1871     1874       +3     
  Lines      127545   127886     +341     
  Branches    37309    37483     +174     
==========================================
  Hits        18608    18608              
- Misses      88018    88352     +334     
- Partials    20919    20926       +7     
Flag Coverage Δ *Carryforward flag
differential 4.69% <0.00%> (?)
total 14.61% <ø> (+0.02%) ⬆️ Carriedforward from 6bf7532

*This pull request uses carry forward flags. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@soblin soblin merged commit f514bca into autowarefoundation:main Jan 29, 2024
41 of 46 checks passed
@soblin soblin deleted the feat/intersection/formalize-safety-responsibility2 branch January 29, 2024 01:04
anhnv3991 pushed a commit to anhnv3991/autoware.universe that referenced this pull request Jan 29, 2024
…tuation to blame past detection fault retrospectively (autowarefoundation#6143)

Signed-off-by: Mamoru Sobue <[email protected]>
Signed-off-by: anhnv3991 <[email protected]>
soblin added a commit to tier4/autoware.universe that referenced this pull request Jan 29, 2024
…tuation to blame past detection fault retrospectively (autowarefoundation#6143)

Signed-off-by: Mamoru Sobue <[email protected]>
kyoichi-sugahara pushed a commit to kyoichi-sugahara/autoware.universe that referenced this pull request Jan 29, 2024
…tuation to blame past detection fault retrospectively (autowarefoundation#6143)

Signed-off-by: Mamoru Sobue <[email protected]>
soblin added a commit to tier4/autoware.universe that referenced this pull request Feb 6, 2024
…tuation to blame past detection fault retrospectively (autowarefoundation#6143)

Signed-off-by: Mamoru Sobue <[email protected]>
karishma1911 pushed a commit to Interplai/autoware.universe that referenced this pull request Jun 3, 2024
…tuation to blame past detection fault retrospectively (autowarefoundation#6143)

Signed-off-by: Mamoru Sobue <[email protected]>
soblin added a commit to tier4/autoware.universe that referenced this pull request Oct 23, 2024
…tuation to blame past detection fault retrospectively (autowarefoundation#6143)

Signed-off-by: Mamoru Sobue <[email protected]>
soblin added a commit to tier4/autoware.universe that referenced this pull request Oct 23, 2024
…tuation to blame past detection fault retrospectively (autowarefoundation#6143)

Signed-off-by: Mamoru Sobue <[email protected]>
saka1-s pushed a commit to saka1-s/autoware.universe that referenced this pull request Nov 9, 2024
…tuation to blame past detection fault retrospectively (autowarefoundation#6143)

Signed-off-by: Mamoru Sobue <[email protected]>
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) run:build-and-test-differential Mark to enable build-and-test-differential workflow. (used-by-ci)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants