Stop flooding the terminal by default with all matches, switch to debug if desired#364
Stop flooding the terminal by default with all matches, switch to debug if desired#364
Conversation
This monitor was not modified in this PR. I'll rebase to see if that helps. |
ed3377a to
c0a8297
Compare
|
Ping @ct2034 Any objections here? |
|
Or can this at least get in before Kilted? 🙂 |
| has_initialized_ = true; | ||
|
|
||
| RCLCPP_INFO( | ||
| RCLCPP_DEBUG( |
There was a problem hiding this comment.
Can we please keep those messages that are not triggered per match on info
|
Hey @MCFurry @Timple |
…e initial log of the function
|
Sorry it took a while! |
|
Based on what we discussed above, that I am happy to change the level in the In any case, I think this would also be a good use for RCLCPP_DEBUG_THROTTLE. What do you think? |
|
The issue is that there a loop around all parameters: for (const auto & param : parameters) {Every analyzer added prints information about all other analyzers as well. Since we have a lot of analyzers, adding only 1 causes a massive print flood. |
|
@ct2034 if you like things to be verbose, do you have any ideas how to get around printing always all parameters? |
We noticed that when extending a ROS system with many analyzers, the terminal during startup is flooded with all the analyzer matches.
I reckon these can be debug logs that one can enable when desired.
(Example in the tests, since these require these stdout logs)