-
Notifications
You must be signed in to change notification settings - Fork 665
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
chore: remove autoware_auto_common dependency from simple_planning_simulator and osqp_interface #2233
chore: remove autoware_auto_common dependency from simple_planning_simulator and osqp_interface #2233
Conversation
velocity.lateral_velocity = 0.0F; | ||
velocity.heading_rate = static_cast<float32_t>(vehicle_model_ptr->getWz()); | ||
velocity.heading_rate = static_cast<double>(vehicle_model_ptr->getWz()); | ||
return velocity; |
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.
I'm not sure why sometimes float32_t instead of float64_t is used
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.
It is because the module interface message was defined by float_32 (e.g. path velocity). This package implementation just followed the interface. (If I remember correctly)
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.
Got it. Thanks.
Should I revert to float?
In other planning packages, we use path velocity as double. Therefore, double can be used here as well IMO.
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.
I don't know much about the risk of using different types, but if it is working, I think it is fine. There is no need to revert your commit. I just wanted to make sure it wasn't an unintentional change.
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.
👍
Codecov ReportBase: 11.13% // Head: 11.37% // Increases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## main #2233 +/- ##
==========================================
+ Coverage 11.13% 11.37% +0.24%
==========================================
Files 1203 1202 -1
Lines 86264 82738 -3526
Branches 20827 20748 -79
==========================================
- Hits 9605 9412 -193
+ Misses 66501 63330 -3171
+ Partials 10158 9996 -162
*This pull request uses carry forward flags. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
I confirmed that planning simulator works well with this PR locally. |
@TakaHoribe @rej55 @maxime-clem @satoshi-ota Could you review? No behavior change with this PR. |
yaw += static_cast<float>((*n.rpy_dist_)(*n.rand_engine_)); | ||
odom.pose.pose.orientation = motion::motion_common::from_angle(yaw); | ||
|
||
vel.longitudinal_velocity += static_cast<float32_t>(velocity_noise); | ||
vel.longitudinal_velocity += static_cast<double>(velocity_noise); |
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.
vel.longitudinal_velocity is defined as a float.
https://github.com/tier4/autoware_auto_msgs/blob/tier4/main/autoware_auto_vehicle_msgs/msg/VelocityReport.idl#L14
Did you replace float32_t
with double
on purpose in this PR? Or just mistake?
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.
As commented here, on purpose.
I followed the other packages' implementation (= path velocity is handled as double).
#2233 (comment)
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.
Just change to use the premitive types and remove dependency.
(Note: it is decided not to use the autoware specific types in the autoware.universe. This kind of type definition is discussed in the autoware.core architecture design.)
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
…, osqp_interface Signed-off-by: Takayuki Murooka <takayuki5168@gmail.com>
3e98ca4
to
a86aa66
Compare
…mulator and osqp_interface (autowarefoundation#2233) remove autoware_auto_common dependency from simple_planning_simulator, osqp_interface Signed-off-by: Takayuki Murooka <takayuki5168@gmail.com> Signed-off-by: Takayuki Murooka <takayuki5168@gmail.com> Signed-off-by: Kotaro Yoshimoto <pythagora.yoshimoto@gmail.com>
…mulator and osqp_interface (autowarefoundation#2233) remove autoware_auto_common dependency from simple_planning_simulator, osqp_interface Signed-off-by: Takayuki Murooka <takayuki5168@gmail.com> Signed-off-by: Takayuki Murooka <takayuki5168@gmail.com> Signed-off-by: yoshiri <yoshiyoshidetteiu@gmail.com>
Signed-off-by: Takayuki Murooka takayuki5168@gmail.com
Description
related to #2229
remove autoware_auto_common from simple_planning_simulator, osqp_interface
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.
After all checkboxes are checked, anyone who has write access can merge the PR.