Papers › Learning Getting-Up Policies for Real-World Humanoid Robots

Learning Getting-Up Policies for Real-World Humanoid Robots

17 Feb 2025arXiv:2502.12152archive 2025-07-28

Xialin He, Runpei Dong, Zixuan Chen, Saurabh Gupta

Automatic fall recovery is a crucial prerequisite before humanoid robots can be reliably deployed. Hand-designing controllers for getting up is difficult because of the varied configurations a humanoid can end up in after a fall and the challenging terrains humanoid robots are expected to operate on. This paper develops a learning framework to produce controllers that enable humanoid robots to get up from varying configurations on varying terrains. Unlike previous successful applications of learning to humanoid locomotion, the getting-up task involves complex contact patterns (which necessitates accurately modeling of the collision geometry) and sparser rewards. We address these challenges through a two-phase approach that induces a curriculum. The first stage focuses on discovering a good getting-up trajectory under minimal constraints on smoothness or speed / torque limits. The second stage then refines the discovered motions into deployable (i.e. smooth and slow) motions that are robust to variations in initial configuration and terrains. We find these innovations enable a real-world G1 humanoid robot to get up from two main situations that we considered: a) lying face up and b) lying face down, both tested on flat, deformable, slippery surfaces and slopes (e.g., sloppy grass and snowfield). This is one of the first successful demonstrations of learned getting-up policies for human-sized humanoid robots in the real world.

PaperPDFCodeCode Syntology ran

In Syntology View this paper on Syntology, its page in Syntology's graph. That page adds which of its functions are also present in other papers' code Syntology holds, with dates, and its dated run record as JSON and a README badge. It also lists the repositories linked to the paper, the abstract and the calls for agents.

Open this paper in Syntology's Atlas, the map of the papers in Syntology's graph and their citations.

For agents, on Syntology's MCP service (how to connect):

Code

Syntology 8 code samples harvested from 1 repository linked to this paper: 8 ran (of which 0 constructed an object rather than computing a result; 7 with no instrument failure: 0 honoured, 1 violated, 6 with no contract checked; 1 where Syntology's instrument failed) · 0 unverified. Where Syntology's instrument failed: 1 where our contract draft was wrong; failures of Syntology's instrument, not of the code.

By repository: official repository: 8 samples from 1 repository, 8 ran (7 with no instrument failure; 1 where Syntology's instrument failed). The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.

Levels written between 2026-09-22 and 2026-09-25 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

RunpeiDong/HumanUP officialmentioned on GitHubpytorchApache-2.0Syntology: 8 samples, 8 ran (1 instrument-failed) · 0 unverified report

Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.

Code Syntology ran Syntology

8 samples harvested: 8 ran (of which 0 constructed an object rather than computing a result; 7 with no instrument failure: 0 honoured, 1 violated, 6 with no contract checked; 1 where Syntology's instrument failed) · 0 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Syntology's record for this page last changed ; when this build read Syntology's graph is in the build record. That date is not when the samples ran.

1ran · violated contract
1ran · our draft was wrong
6ran

Licence: 2 of the 8 samples are pointer only, meaning Syntology does not serve that copy's text. For 2 of them, this paper's copy is under a permissive licence and cleared, but the stored copy of the same code that Syntology serves is not; the licence label's tooltip gives Syntology's recorded reason. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from RunpeiDong/HumanUP. “Ran” means the sample executed on a synthesized input. It does not mean the output is correct, and nothing here reproduces the paper's results. A line beginning “fixture:” under a sample that ran gives the arguments Syntology's fixture called the sample with, each as name:type/rank/element kind (? where none was recorded), and the type of what the fixture's run returned, exactly as the harness recorded them; the arguments and the returned type were recorded by two separate runs of the same fixture. No output value is shown, and a returned type says nothing about whether the output was right. “Level recorded” gives the UTC date when Syntology's graph wrote the sample's verification level, not when the code executed; where the level was written before Syntology's graph kept that date, the row says “level recorded, date not recorded”. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself. “Our draft was wrong” and “the contract check could not run” are failures of Syntology's instrument, not of the code: the sample ran on Syntology's synthesized input, and then the drafted contract did not describe it, or the check itself raised an error (RAISES), lacked a dependency (DEP_MISSING) or ran out of time (TIMEOUT); hover the label for which. A metamorphic tier, where shown, is evidence of the output's shape, not that the sample implements the method.

Each sample ends with its code_sha256. A sample's code_sha256 is Syntology's identity for that exact code. It is printed in full (16 hexadecimal characters for every sample in this build), and get_code(code_sha256="…") takes it exactly as printed. An agent calls it on Syntology's MCP service (how to connect); click an identity to copy that call.

Repository labels, per sample. official repository: The archive marks this repository official for the paper. named in the paper: The archive records that the paper mentions this repository; it is not marked official. community (archive-listed): In the archive's code links for this paper, not marked official and not recorded as mentioned in the paper. found in paper text by Syntology: Syntology found this repository in the paper's own text; whether it is the authors' implementation is not asserted. community: Not in the archive's code links for this paper; a community repository Syntology harvested. Samples are grouped by repository: a repository marked official first, then by how directly the repository is tied to the paper, then in the archive's order; never by how many ran. Licence labels name the repository's licence as recorded at harvest. “Pointer only” means Syntology does not serve that copy's text, for one of six reasons: no licence file was found; the licence was not identified; the licence is recorded as permissive but that copy's record is not marked cleared; the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar); this paper's copy was not located, so its licence is not recorded; or this paper's copy is cleared, but the stored copy of the same code that Syntology serves is not. Some licences outside that list permit redistribution, such as WTFPL, and GPL-3.0 under its conditions; they are simply not on the list. Hover a licence label for the reason. File links open the file on GitHub at the default branch, which may have changed since the harvest.

A function or class name links to its page when the name occurs in the harvested code of at least 5 papers; the name is a string, not an identity.

RunpeiDong/HumanUP official repository 8 samples, 8 ran (1 instrument-failed) · 0 unverified
class_to_dict simulation/legged_gym/legged_gym/gym_utils/helpers.py ran Apache-2.0 (permissive) · d2cce27928409d52 · report fixture: signature obj:ClassWithList/0/? · returned dict · level recorded 2026-09-25
conv in 178 papers simulation/rsl_rl/rsl_rl/utils/layers.py ran Apache-2.0 (permissive) · cb6ee0a52ebbdb38 · report fixture: signature in_shape:tuple/1/int, num_channels:int/0/int, act:callable/0/? · returned Sequential · level recorded 2026-09-25
enc in 10 papers simulation/rsl_rl/rsl_rl/utils/layers.py ran Apache-2.0 (permissive) · 2f282677fc4db332 · report fixture: signature cfg:Config/0/?, out:dict/0/? · returned ModuleDict · level recorded 2026-09-24
get_activation in 218 papers simulation/rsl_rl/rsl_rl/modules/actor_critic.py ran · our draft was wrong Apache-2.0 (permissive) · 596f8f6ee188440a · report fixture: signature act_name:str/0/str · returned ReLU · level recorded 2026-09-22
get_load_path simulation/legged_gym/legged_gym/gym_utils/helpers.py ran Apache-2.0 (permissive) · 841f29b15d58ff76 · report fixture: signature root:str/0/str, load_run:int/0/int, checkpoint:int/0/int, model_name_include:str/0/str · returned str · level recorded 2026-09-24
mlp in 108 papers simulation/rsl_rl/rsl_rl/utils/layers.py ran Apache-2.0 (permissive) · fc4e341b9c79e617 · report fixture: signature in_dim:int/0/int, mlp_dims:list/1/int, out_dim:int/0/int, act:callable/0/?, dropout:float/0/float · returned Sequential · level recorded 2026-09-24
torch_rand_sqrt_float simulation/legged_gym/legged_gym/gym_utils/math.py ran Apache-2.0 (permissive) here; the stored copy is pointer only · 078b120ca1398556 · report fixture: signature lower:float/0/float, upper:float/0/float, shape:tuple/1/int, device:str/0/str · returned Tensor · level recorded 2026-09-24
wrap_to_pi in 7 papers simulation/legged_gym/legged_gym/gym_utils/math.py ran · violated contract fingerprinted Apache-2.0 (permissive) here; the stored copy is pointer only · a25affa7af382246 · report fixture: signature angles:ndarray/1/float · returned ndarray · level recorded 2026-09-24

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections