-
Notifications
You must be signed in to change notification settings - Fork 676
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
refactor(radar_tracks_msgs_converter): rework parameters #4911
refactor(radar_tracks_msgs_converter): rework parameters #4911
Conversation
Signed-off-by: PhoebeWu21 <[email protected]>
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.
Looks good, but need more input.
perception/radar_tracks_msgs_converter/schema/radar_tracks_msgs_converter.schema.json
Show resolved
Hide resolved
perception/radar_tracks_msgs_converter/config/config-radar_tracks_msgs_converter.param.yaml
Outdated
Show resolved
Hide resolved
...cks_msgs_converter/src/radar_tracks_msgs_converter_node/radar_tracks_msgs_converter_node.cpp
Outdated
Show resolved
Hide resolved
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## main #4911 +/- ##
==========================================
- Coverage 15.32% 0.00% -15.33%
==========================================
Files 1721 2 -1719
Lines 118559 138 -118421
Branches 37995 0 -37995
==========================================
- Hits 18169 0 -18169
+ Misses 79657 138 -79519
+ Partials 20733 0 -20733
☔ View full report in Codecov by Sentry. |
perception/radar_tracks_msgs_converter/config/config-radar_tracks_msgs_converter.param.yaml
Show resolved
Hide resolved
Signed-off-by: PhoebeWu21 <[email protected]>
- Default parameter is "base_link" | ||
- `use_twist_compensation` (bool): If the parameter is true, then the twist of output objects' topic is compensated by ego vehicle motion. | ||
- Default parameter is "false" | ||
{{ json_to_markdown("perception/radar_tracks_msgs_converter/schema/radar_tracks_msgs_converter.schema.json") }} |
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.
[MUST]
This change is very inconvenience because we cannot see parameters description at github.
I think the parameter description should be written by markdown like this PR.
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.
(Sorry for confusing with my comment above 🙇 )
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.
@scepter914 This is an implementation of the goal described in https://autowarefoundation.github.io/autoware-documentation/main/contributing/coding-guidelines/ros-nodes/parameters/#workflow. Could you consider using the rendered version of the documentation instead of the github pages? For example: https://autowarefoundation.github.io/autoware.universe/latest/perception/lidar_apollo_segmentation_tvm_nodes/#parameters
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.
Why we use only the rendered version of documents?
I think it is convenience both github README and the rendered version.
In addition, as the reaction in PR of #5241 is neglected for now, I cannot recognize the maintenance ability for using the json schema for parameter tables.
As code owner, I cannot accept the change that cause inconvenience for maintenance, and it is not allowed to delete the markdown parameter tables unless there is enough ability to maintain the json schema for parameter tables.
This pull request has been automatically marked as stale because it has not had recent activity. |
Because this PR has stale label and there are conflicts from many changes. |
I don't see any issue with this PR. Would it be possible to re-open this issue and work on getting it merged? Thanks! |
@kaspermeck-arm |
If I'm understanding correctly, there are two issues:
@scepter914 - is this correct? |
Yes.
Because of many documentation update the parameter table is not enough to explain the parameters as you can see radar_object_clustering. As the parameter table change, I think the PR should not replace the parameter explain but only add tables. Anyway, once this PR marked stale and there was a difference from the main branch as a result of being abandoned, so I think you should recreate the PR with a clean commit log as OSS develop. |
This is the section which should be replaced with the auto-generated schema-to-table macro with It was decided that having a single source of truth brings more value than having the parameter table in the README file. If you want to add more context outside of the README if the description field in the table isn't sufficient, like you express you want. You can compare and to see how it will look with the new coding guidelines. Looks pretty nice, yeah? :)
Agreed, a new PR based on this PR can be created instead of trying to fix this one. @scepter914 - can we agree on the suggestions above? |
I cannot agree your suggestion. In summary, I cannot accept the change "replacing from raw README to parameter table made from a json file" and I can only accept the change "adding parameter table made from a json file with a short description" like below table.
|
Description
Implement the ROS Node configuration layout described in https://github.com/orgs/autowarefoundation/discussions/3371 for the
radar_tracks_msgs_converter
package.Tests performed
Package built and launch locally.
colcon build --symlink-install --cmake-args -DCMAKE_BUILD_TYPE=Release --packages-up-to radar_tracks_msgs_converter
Effects on system behavior
More reliable and faster parameter configuration file creation.
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.