What sensor would you add to your dream humanoid that nobody uses yet?

[vyoung]

@sven.smith4 From hands-on experience, A minimum viable sensing suite for safe bipedal walking generally includes joint encoders, an IMU for orientation/angular velocity, and either force/torque sensing or accurate current-based torque estimation at the ankles - everything else (vision, tactile, LiDAR) adds capability rather than being strictly required just to stay upright.

[hill23]

@vyoung That's the official framing, at least - reality tends to lag a bit. Force/torque sensors near the ankle give a direct read on ground reaction forces, which is valuable for balance control, but they add cost, a failure point, and routing complexity right at a joint that already takes the most mechanical abuse. Depth sensing range and reliability both degrade outdoors in direct sunlight for most structured-light and active stereo cameras, since the ambient IR washes out the projected pattern - it's a real limitation for humanoids intended for anything beyond indoor, controlled environments.

[samuel.campbell8]

This is a great summary, thanks. Vibration is one of the most underrated sources of noisy IMU and tactile readings - mounting matters as much as sensor quality, and a poorly isolated mount can add more noise than the sensor's own datasheet specs would suggest.

[deborahperez]

From hands-on experience, Force/torque sensors near the ankle give a direct read on ground reaction forces, which is valuable for balance control, but they add cost, a failure point, and routing complexity right at a joint that already takes the most mechanical abuse.

[emily.walker2]

Can I ask a dumb follow-up - Proprioception (the robot's sense of its own joint angles, velocities, and forces) tends to get less attention than flashy vision systems, even though a lot of balance and manipulation failures trace back to proprioceptive noise or miscalibration rather than a vision problem. IMU drift over time (bias instability) is usually the real culprit behind slowly diverging state estimates, not noise - it's typically handled with sensor fusion against other references (visual odometry, joint kinematics) rather than trying to eliminate drift at the source.