gaze_at_pose consumes high drive space
Closed this issue · 7 comments
Take a look at gaze_at_pose-34-stdout.log
One day it consumes 88GB space.
strands@bob:~/.ros/log/2e170bda-ac18-11e6-9e5d-00032d22587c$ ls -hs
total 89G
8.0K activity_exploration-1.log 16K execute_policy_server-29.log 0 robot-robot_state_publisher-8-stdout.log 101M rosout.log.6
8.0K backtrack_server-23.log 0 fremenserver-26-stdout.log 0 robot_pose_publisher-9-stdout.log 101M rosout.log.7
0 chest-chest_joint_state_publisher-4-stdout.log 88G gaze_at_pose-34-stdout.log 16K ros_mary_bridge-2.log 101M rosout.log.8
4.0K chest-chest_joint_state_publisher-4.log 4.0K human_aware_navigation-36.log 0 rosapi-4-stdout.log 101M rosout.log.9
0 chest-chest_robot_state_publisher-5-stdout.log 0 joystick-10-stdout.log 4.0K rosapi-4.log 8.0K strands_webserver-6.log
0 chest_xtion-depth_metric-6-stdout.log 0 map_server-1-stdout.log 12K rosbridge_websocket-3.log 296K teleop_head-13-stdout.log
0 chest_xtion-depth_metric_rect-5-stdout.log 0 maryserver-1-stdout.log 16K roslaunch-bob-14040.log 328K teleop_head-13.log
0 chest_xtion-depth_points-7-stdout.log 17M master.log 176K roslaunch-bob-14196.log 0 tf2_web_republisher-5-stdout.log
0 chest_xtion-depth_rectify_depth-4-stdout.log 12K mdp_policy_executor_extended-2.log 68K roslaunch-bob-14221.log 4.0K topological_localisation-27.log
0 chest_xtion-depth_registered_sw_metric_rect-10-stdout.log 6.8M mdp_task_executor-3.log 88K roslaunch-bob-16307.log 0 topological_map_manager-25-stdout.log
0 chest_xtion-driver-2-stdout.log 8.0K mdp_task_guarantees_estimator-1.log 480K roslaunch-bob-16663.log 4.0K topological_map_manager-25.log
0 chest_xtion-points_xyzrgb_sw_registered-9-stdout.log 276K monitored_nav-24.log 64K roslaunch-bob-20306.log 44K topological_navigation-28.log
0 chest_xtion-register_depth_rgb-8-stdout.log 0 no_go_map_server-2-stdout.log 32K roslaunch-bob-27576.log 4.0K topological_prediction-32.log
0 chest_xtion-rgb_rectify_color-3-stdout.log 0 odometry_mileage-33-stdout.log 480K rosout-1-stdout.log 0 travel_time_estimator-31-stdout.log
0 diagnostic_aggregator-6-stdout.log 0 pc_monitor-5-stdout.log 84M rosout.log 4.0K travel_time_estimator-31.log
4.0K door_checking-16.log 4.0K pc_monitor-5.log 101M rosout.log.1 0 visualise_map-30-stdout.log
4.0K door_passing-15.log 0 pose_extractor-35-stdout.log 101M rosout.log.10 4.0K visualise_map-30.log
8.0K door_prediction-20.log 4.0K pose_extractor-35.log 101M rosout.log.2 4.0K wait_action-4.log
4.0K door_wait_and_move_base-18.log 12K ptu_action_server-4.log 101M rosout.log.3
348K door_wait_and_pass-17.log 0 robot-joint_state_publisher-7-stdout.log 101M rosout.log.4
24K door_waiting-19.log 4.0K robot-joint_state_publisher-7.log 101M rosout.log.5
Any idea why?
I never noticed this. Not sure if there is logger setting for this... You could try to comment all the ROS_DEBUG statements.
@ferdianjovan please point me at one of these big log files
Third line, second column above.
I am sorry, I deleted the file because it is too large and Bob was running out of space.
But normally you can find it in Home folder, under .ros/log/, inside one of the folders there.
At the moment gaze does not produce anything.
I will comment once it is there and quite big.
Might be the same reason as #149 and https://github.com/strands-project/strands_hri/blob/hydro-devel/strands_gazing/src/gaze_at_pose/gaze_at_pose.cpp#L118-L120 is to blame.
I think that should solve it. Thanks @cdondrup
No worries, I am just confused why this never happened before. Maybe there is something wrong with tf?!
If anything, we try to make the eyes follow a person behind the screen where the eyes are still seeing the opposite side.