Papers › Regression Planning Networks

Regression Planning Networks

28 Sep 2019NeurIPS 2019 12arXiv:1909.13072archive 2025-07-28

Danfei Xu, Roberto Martín-Martín, De-An Huang, Yuke Zhu, Silvio Savarese, Li Fei-Fei

Recent learning-to-plan methods have shown promising results on planning directly from observation space. Yet, their ability to plan for long-horizon tasks is limited by the accuracy of the prediction model. On the other hand, classical symbolic planners show remarkable capabilities in solving long-horizon tasks, but they require predefined symbolic rules and symbolic states, restricting their real-world applicability. In this work, we combine the benefits of these two paradigms and propose a learning-to-plan method that can directly generate a long-term symbolic plan conditioned on high-dimensional observations. We borrow the idea of regression (backward) planning from classical planning literature and introduce Regression Planning Networks (RPN), a neural network architecture that plans backward starting at a task goal and generates a sequence of intermediate goals that reaches the current observation. We show that our model not only inherits many favorable traits from symbolic planning, e.g., the ability to solve previously unseen tasks but also can learn from visual inputs in an end-to-end manner. We evaluate the capabilities of RPN in a grid world environment and a simulated 3D kitchen environment featuring complex visual scenes and long task horizons, and show that it achieves near-optimal performance in completely new task instances.

PaperPDFConference PDFCodeCode 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 10 code samples harvested from 1 repository linked to this paper: 9 ran (of which 0 constructed an object rather than computing a result; 9 with no instrument failure: 0 honoured, 0 violated, 9 with no contract checked; 0 where Syntology's instrument failed) · 1 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code; here there are none.

By repository: community (archive-listed): 10 samples from 1 repository, 9 ran (9 with no instrument failure; 0 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 on 2026-09-24 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

danfeiX/RPN mentioned on GitHubpytorchMITSyntology: 10 samples, 9 ran (0 instrument-failed) · 1 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

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

9ran
1unverified

Licence: 0 of the 10 samples are pointer only, meaning Syntology does not serve that copy's text. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from danfeiX/RPN. “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.

danfeiX/RPN community (archive-listed) 10 samples, 9 ran (0 instrument-failed) · 1 unverified
compute_bce_loss rpn/net.py ran fingerprinted MIT (permissive) · e786b68cb3c4c783 · report fixture: signature logits:Tensor/2/float, labels:Tensor/2/float, weight:Tensor/1/float · returned Tensor · level recorded 2026-09-24
get_action in 25 papers rpn/grid_envs.py ran MIT (permissive) · 04faa2fa28055032 · report fixture: signature pos1:list/1/int, pos2:list/1/int · returned str · level recorded 2026-09-24
make_action_graph_inputs rpn/data_utils.py ran MIT (permissive) · afba6b8db6213003 · report fixture: signature serialized_action:list/1/int, object_ids:list/1/int, num_nodes:int/0/int · returned tuple · level recorded 2026-09-24
masked_symbolic_state_index rpn/net.py ran MIT (permissive) · 8d9b5ebd873578ea · report fixture: signature symbolic_state:Tensor/2/float, mask:Tensor/2/float · returned Tensor · level recorded 2026-09-24
open_door_inst rpn/grid_envs.py ran fingerprinted MIT (permissive) · ad56cec7ef825a1b · report fixture: signature color:str/0/str · returned list · level recorded 2026-09-24
return_path rpn/grid_envs.py ran MIT (permissive) · 87e60fd22f0f7945 · report fixture: signature current_node:Node/0/? · returned tuple · level recorded 2026-09-24
same_sg_list rpn/eval_grid.py ran MIT (permissive) · 2dfea827f19374e4 · report fixture: signature sgl1:list/1/SceneGraph, sgl2:list/1/SceneGraph · returned bool · level recorded 2026-09-24
sample_actions rpn/data_utils.py ran MIT (permissive) · d8cfd66dcbe99521 · report fixture: signature num_samples:int/0/int, num_objects:int/0/int, num_actions:int/0/int · returned ndarray · level recorded 2026-09-24
to_graph_dense rpn/data_utils.py ran MIT (permissive) · fca703346be0f49e · report fixture: signature inputs:ndarray/2/float, input_ids:ndarray/1/int, input_len:int/0/int, id_to_index_map:dict/0/? · returned ndarray · level recorded 2026-09-24
rollout_policy rpn/eval_grid.py unverified MIT (permissive) · b44701e4cd64d292 · report

Tasks

regression

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Methods

RPN

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