Krishna/clear logs - #71
Open
krish-134 wants to merge 6 commits into
Open
Conversation
…pp and cpp to use gzlog to write Gazebo logs into ~/.gazebo/server-*/default.log when verbose:=true
…nformed gazebo message
…Krishna/ClearLogs
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Repeated message from Issues:
Hey guys, I made some changes to make Gazebo launches a little cleaner in the terminal logs.
Issue:
gazebo_launch.py had verbose: 'true' hardcoded for gzserver, which enabled Gazebo terminal logging.
Combined with gazebo_utils.cpp/.hpp unconditionally logging every SDF parameter it read (including matrices for added_mass, linear_damping, etc.), this flooded the terminal on every simulation startup.
Changes:
Let me know what you think!