Humanoid-PushRecovery-CrossEmbodiment

Humanoid-PushRecovery-CrossEmbodiment simulates balance-recovery trials for humanoid robots subjected to external pushes, terrain irregularities, and low-friction (slip) events, using the same reduced-order dynamics the push-recovery control literature itself relies on: Linear Inverted Pendulum CoM dynamics (Kajita et al., 2001), Capture Point balance-recoverability analysis (Pratt, Carff, Drakunov & Goswami, 2006), Divergent-Component-of-Motion feedback control (Englsberger, Ott & Albu-Schaffer, 2015), and the ankle/hip/step/fall strategy-escalation taxonomy of Stephens (2007). 32 independently-sampled robot "embodiments" (mass, CoM height, foot size, hip strategy budget, max step distance, sensorimotor reaction latency, sensor noise) each generate 60 trials varying push magnitude/direction, standing vs. walking gait phase, terrain roughness, and floor friction, at 50 Hz for 3 seconds (150 steps) per trial. Robot parameters are illustrative ranges spanning published research-humanoid scales, not a fitted digital twin of any named robot. Following Kalyanakrishnan & Goswami (2011, International Journal of Humanoid Robotics), the dataset reproduces their reported non-monotonic fall pattern: identical push magnitude at different points in the gait cycle produces opposite outcomes, due to the narrower base of support during single-leg stance. This is empirically verified in the generated trials. Following Mungai, Prabhakaran & Grizzle (2024, ICRA), roughly 18% of trials are "intermittent": a second, smaller push arrives while the robot is still mid-recovery from the first, testing robustness to compounding disturbances. Each timestep records 22 channels: CoM kinematics, capture point, zero-moment point, IMU-like acceleration/gyroscope readings, ankle/hip torque, ground reaction forces, simplified joint angles, and gait-support phase. The train/val/test split is grouped by robot embodiment, so entire robot designs are held out for testing generalization to unseen humanoid morphologies, not just unseen pushes on familiar hardware. This is a synthetic dataset: no real robot telemetry, proprietary, or personal data was used.