-
Notifications
You must be signed in to change notification settings - Fork 682
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(autoware_multi_object_tracker): output from screen to both #8407
fix(autoware_multi_object_tracker): output from screen to both #8407
Conversation
Thank you for contributing to the Autoware project! 🚧 If your pull request is in progress, switch it to draft mode. Please ensure:
|
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
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #8407 +/- ##
==========================================
+ Coverage 23.74% 29.22% +5.48%
==========================================
Files 1378 1600 +222
Lines 101364 116782 +15418
Branches 38512 50281 +11769
==========================================
+ Hits 24072 34134 +10062
+ Misses 74853 73494 -1359
- Partials 2439 9154 +6715
*This pull request uses carry forward flags. Click here to find out more. ☔ View full report in Codecov by Sentry. |
Please wait for the merge as it is under discussion here. |
Description
Set output from screen to both to improve the debugging efficiency of Autoware in general.
With this change, the output from node will not only be displayed in screen but also to the log file.
See https://github.com/ros2/launch/blob/986ea832cec49c18bee4e29ee4df37fe3844fa90/launch/launch/logging/__init__.py#L397-L487
Related links
TIER IV INTERNAL THREAD
How was this PR tested?
Not tested
Notes for reviewers
None
Interface changes
None.
Effects on system behavior
Although there will be a slight increase in computational load due to the additional log, I would say that the risk is minimal since the node's output does not occupy terminal at this moment. But just in case, I would like to make this change for several nodes chosen from perception component which tends to have some issues pretty often.