Describe the bug
Launching zed2.launch through terminal causes the terminal to become flooded with debug messages. I upgraded to 3.4.2, but had this happening also in the previous version I was on.
Looks like this:
[DEBUG] [1615857187.177669129]: No new BAROM. DATA
[DEBUG] [1615857187.178948377]: Publishing TF
[DEBUG] [1615857187.179232125]: No new IMU temp.
[DEBUG] [1615857187.179328607]: No new BAROM. DATA
[DEBUG] [1615857187.183450453]: Publishing TF
[DEBUG] [1615857187.184026717]: No new IMU temp.
[DEBUG] [1615857187.184169246]: No new BAROM. DATA
[DEBUG] [1615857187.185328302]: Publishing TF
[DEBUG] [1615857187.185938454]: No updated sensors data
[DEBUG] [1615857187.191010681]: Publishing TF
[DEBUG] [1615857187.191322845]: No new IMU temp.
[DEBUG] [1615857187.191529312]: No new BAROM. DATA
[DEBUG] [1615857187.194299332]: Publishing TF
[DEBUG] [1615857187.194828011]: No new IMU temp.
@orrblue you compiled the node in DEBUG mode.
Try to compile forcing the Release mode to remove the debug messages:
$ catkin_make -DCMAKE_BUILD_TYPE=Release
Describe the bug Launching zed2.launch through terminal causes the terminal to become flooded with debug messages. I upgraded to 3.4.2, but had this happening also in the previous version I was on.
Looks like this: [DEBUG] [1615857187.177669129]: No new BAROM. DATA [DEBUG] [1615857187.178948377]: Publishing TF [DEBUG] [1615857187.179232125]: No new IMU temp. [DEBUG] [1615857187.179328607]: No new BAROM. DATA [DEBUG] [1615857187.183450453]: Publishing TF [DEBUG] [1615857187.184026717]: No new IMU temp. [DEBUG] [1615857187.184169246]: No new BAROM. DATA [DEBUG] [1615857187.185328302]: Publishing TF [DEBUG] [1615857187.185938454]: No updated sensors data [DEBUG] [1615857187.191010681]: Publishing TF [DEBUG] [1615857187.191322845]: No new IMU temp. [DEBUG] [1615857187.191529312]: No new BAROM. DATA [DEBUG] [1615857187.194299332]: Publishing TF [DEBUG] [1615857187.194828011]: No new IMU temp.
Device information:
Thank you