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

Fix/lanelet matching distance #1208

Merged
merged 4 commits into from
Mar 13, 2024
Merged

Conversation

TauTheLepton
Copy link
Contributor

@TauTheLepton TauTheLepton commented Mar 6, 2024

Description

This fix adds the usage of default matching distance of each entity for setEntityStatus functions that are run by teleport action in open scenario.

Abstract

Default lane matching distance depends on entity type and is used in various places in the code. The default distance was not used in all possible situations.

Background

The default lane matching distance was added to the scenario simulator in PR #1194. However, the distance usage was not applied to all possible situations.

Details

Default lane matching distance of each entity was not used in open scenario teleport action and the default distance of 1.0 was used. This fix adds the default lane matching distance to the API::setEntityStatus function, which is used in the open scenario teleport action.

References

See #1194 for first default matching distance implementation.
INTERNAL ISSUE LINK

Destructive Changes

Known Limitations

The same limitations to the lane matching as before apply. The difference is that the default lane matching distance in teleport action is used, so it is slightly bigger than before (which was 1.0)

Copy link

github-actions bot commented Mar 6, 2024

Checklist for reviewers ☑️

All references to "You" in the following text refer to the code reviewer.

  • Is this pull request written in a way that is easy to read from a third-party perspective?
  • Is there sufficient information (background, purpose, specification, algorithm description, list of disruptive changes, and migration guide) in the description of this pull request?
  • If this pull request contains a destructive change, does this pull request contain the migration guide?
  • Labels of this pull request are valid?
  • All unit tests/integration tests are included in this pull request? If you think adding test cases is unnecessary, please describe why and cross out this line.
  • The documentation for this pull request is enough? If you think adding documents for this pull request is unnecessary, please describe why and cross out this line.

@TauTheLepton TauTheLepton marked this pull request as ready for review March 11, 2024 12:38
@@ -331,6 +331,7 @@ class API
FORWARD_TO_ENTITY_MANAGER(getRelativePose);
FORWARD_TO_ENTITY_MANAGER(getStandStillDuration);
FORWARD_TO_ENTITY_MANAGER(getTraveledDistance);
FORWARD_TO_ENTITY_MANAGER(getDefaultMatchingDistanceForLaneletPoseCalculation);
FORWARD_TO_ENTITY_MANAGER(getV2ITrafficLight);
FORWARD_TO_ENTITY_MANAGER(getV2ITrafficLights);
FORWARD_TO_ENTITY_MANAGER(isEgoSpawned);
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It is a very small change, so it is unnecessary to retry Autoware Evaluator.

@hakuturu583 hakuturu583 merged commit 404cdde into master Mar 13, 2024
10 checks passed
@hakuturu583 hakuturu583 deleted the fix/lanelet-matching-distance branch March 13, 2024 20:52
@github-actions github-actions bot restored the fix/lanelet-matching-distance branch March 13, 2024 20:53
@hakuturu583 hakuturu583 deleted the fix/lanelet-matching-distance branch June 19, 2024 00:59
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.

2 participants