-
Notifications
You must be signed in to change notification settings - Fork 59
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
RJD-1333/previous following lanelets #1415
Merged
Merged
+97
−51
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
gmajrobotec
added
the
bump patch
If this pull request merged, bump patch version of the scenario_simulator_v2
label
Oct 9, 2024
Checklist for reviewers ☑️All references to "You" in the following text refer to the code reviewer.
|
@gmajrobotec Could you check and fix sonarcloud warnings? |
Quality Gate passedIssues Measures |
hakuturu583
approved these changes
Nov 14, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
bump patch
If this pull request merged, bump patch version of the scenario_simulator_v2
wait for regression test
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Abstract
Function
getFollowingLanelets
has confusing functionality or imprecise naming. Consider the following invocation:getFollowingLanelets(120660, {120660, <random-lanelets>}, 10000, true)
, then will be added to the returned vector unconditionally.Function
getPreviousLanelets
has a mistake. The function is supposed to process one lanelet in every iteration, but every iteration starts from the lanelet passed as the argument. The result will be the lanelet passed as the argument and many copies of the one - previous lanelet. The mistake was introduced in change 3fc8c0a#diff-da44510bdbbba766d1ba47318640cfd8bcff2e350eafe3d77d364bfbf70e25cdL745-L770. The previous implementation seems to have been right.Details
Function
getFollowingLanelets
was changed to check if candidates lanelets are actually following each other.Function
getPreviousLanelets
was rewritten to match previous implementation.References
Jira ticket: internal link
Destructive Changes
There are no destructive changes.