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(bvp): don't use numeric limits for start/finish distance #6960

Closed

Conversation

satoshi-ota
Copy link
Contributor

@satoshi-ota satoshi-ota commented May 9, 2024

Description

Tests performed

Effects on system behavior

Nothing.

Interface changes

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.

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.

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 May 9, 2024
Signed-off-by: satoshi-ota <satoshi.ota928@gmail.com>
@@ -72,8 +72,6 @@ void BlindSpotModuleManager::launchNewModules(
module_id, lane_id, planner_data_, planner_param_, logger_.get_child("blind_spot_module"),
clock_));
generateUUID(module_id);
updateRTCStatus(
getUUID(module_id), true, std::numeric_limits<double>::lowest(), path.header.stamp);
Copy link
Contributor

Choose a reason for hiding this comment

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

If this line is removed, RTC status does not contain this information.
To check the existence of a module with module_id, status should contain this information, so I think this information including distance as -10000.0 is required.

@satoshi-ota
Copy link
Contributor Author

@rej55 Thanks. I think there is no problem since updateRTCStatus is always called in sendRTC function per every planning cycle.

On the other hand, I found it was able to echo topics that include nan or inf. Then, I close this PR.

@satoshi-ota satoshi-ota deleted the fix/dont-use-numeric-limits branch May 10, 2024 04:04
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)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants