Papers › MOPO: Model-based Offline Policy Optimization

MOPO: Model-based Offline Policy Optimization

27 May 2020NeurIPS 2020 12arXiv:2005.13239archive 2025-07-28

Tianhe Yu, Garrett Thomas, Lantao Yu, Stefano Ermon, James Zou, Sergey Levine, Chelsea Finn, Tengyu Ma

Offline reinforcement learning (RL) refers to the problem of learning policies entirely from a large batch of previously collected data. This problem setting offers the promise of utilizing such datasets to acquire policies without any costly or dangerous active exploration. However, it is also challenging, due to the distributional shift between the offline training data and those states visited by the learned policy. Despite significant recent progress, the most successful prior methods are model-free and constrain the policy to the support of data, precluding generalization to unseen states. In this paper, we first observe that an existing model-based RL algorithm already produces significant gains in the offline setting compared to model-free approaches. However, standard model-based RL methods, designed for the online setting, do not provide an explicit mechanism to avoid the offline setting's distributional shift issue. Instead, we propose to modify the existing model-based RL methods by applying them with rewards artificially penalized by the uncertainty of the dynamics. We theoretically show that the algorithm maximizes a lower bound of the policy's return under the true MDP. We also characterize the trade-off between the gain and risk of leaving the support of the batch data. Our algorithm, Model-based Offline Policy Optimization (MOPO), outperforms standard model-based RL algorithms and prior state-of-the-art model-free offline RL algorithms on existing offline RL benchmarks and two challenging continuous control tasks that require generalizing from data collected for a different task. The code is available at https://github.com/tianheyu927/mopo.

PaperPDFConference PDFCodeCode Syntology ranMethod as code

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.

Syntology holds a reference implementation of MOPO, generated from the paper text (not the authors' code), at level 3 on Syntology's ladder: V2 “two implementations GENERATED from the paper's signature and spec agree numerically (1e-6) on fixture inputs” “neither of the two ever read the authors' own code, so V2 measures how unambiguously the paper specifies the method, not fidelity to the authors' implementation (measured 2026-09-11, commit 75eaa77: cross_checked_by is a second LLM on 2,628 of 2,831 served samples)”; V3 “paper-derived property tests pass on both of those same two generations.” (quoted from Syntology's server card). For this implementation, level 3 is recorded, but its report lists no property test that passed on both. No rung compares this code against the authors' implementation. For agents: get_reference_implementation(name='MOPO') (how to connect); the free check have('2005.13239') needs no token.

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

Code

The archive's official repository (tianheyu927/mopo) was not harvested; the 8 samples below come from 4 community repositories.

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

By repository: community (archive-listed): 8 samples from 4 repositories, 3 ran (2 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-24 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

tianheyu927/mopo officialmentioned in papermentioned on GitHubMITSyntology: not harvested report
Yihao-Sun/pytorch-mopo mentioned on GitHubpytorchSyntology: 2 samples, 0 ran · 2 unverified report
junming-yang/mopo mentioned on GitHubpytorchSyntology: 2 samples, 1 ran (1 instrument-failed) · 1 unverified report
runamu/compositional-conservatism mentioned on GitHubpytorchSyntology: 1 sample, 0 ran · 1 unverified report
yihaosun1124/OfflineRL-Kit mentioned on GitHubpytorchSyntology: 3 samples, 2 ran (0 instrument-failed) · 1 unverified report
polixir/OfflineRL pytorchSyntology: not harvested 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: 3 ran (of which 1 constructed an object rather than computing a result; 2 with no instrument failure: 0 honoured, 0 violated, 2 with no contract checked; 1 where Syntology's instrument failed) · 5 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 · our draft was wrong
2ran
5unverified

Licence: 0 of the 8 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 4 repositories linked to this paper, official or community; the list below is grouped by repository, each group headed by its name and what it is to the paper. “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.

Yihao-Sun/pytorch-mopo community (archive-listed) 2 samples, 0 ran · 2 unverified
FakeEnv mopo.py unverified MIT (permissive) · 905ff707fa717537 · report
MOPO mopo.py unverified MIT (permissive) · 29dd6b4e1d20ae33 · report
junming-yang/mopo community (archive-listed) 2 samples, 1 ran (1 instrument-failed) · 1 unverified
dict_batch_generator algo/mopo.py ran · our draft was wrong MIT (permissive) · 9bfce911836d13d9 · report fixture: signature data:dict/0/?, batch_size:int/0/int, keys:NoneType/0/? · returned generator · level recorded 2026-09-22
MOPO algo/mopo.py unverified MIT (permissive) · 4915612bb67c4977 · report
runamu/compositional-conservatism community (archive-listed) 1 sample, 0 ran · 1 unverified
train in 522 papers run_example/run_mopo.py unverified MIT (permissive) · 2c8a2717c213a768 · report
yihaosun1124/OfflineRL-Kit community (archive-listed) 3 samples, 2 ran (0 instrument-failed) · 1 unverified
BaseDynamics offlinerlkit/policy/model_based/mopo.py ran MIT (permissive) · 0367ac63f92bed11 · report fixture: returned BaseDynamics · level recorded 2026-09-22
SACPolicy in 5 papers offlinerlkit/policy/model_based/mopo.py ran MIT (permissive) · b3d37324c880e711 · report fixture: signature batch:dict/0/? · returned dict · level recorded 2026-09-24
MOPOPolicy offlinerlkit/policy/model_based/mopo.py unverified MIT (permissive) · cee64d8d029d6485 · report

Method as code Syntology

What Syntology's graph records as this paper's claimed method, lifted into code: each assembly names its bricks (functions and classes), each with its own role and its own verification level. An assembly is not a check that the code implements the method correctly or reproduces the paper's results. Levels are each brick's own verification level in Syntology's graph (level 0: no recorded run), listed brick by brick and never combined into one level; “ran” means the brick executed on a synthesized input, not that its output is correct, and the instrument figure counts failures of Syntology's instrument, not of the code. For a generated assembly, an independent peer is a second implementation generated separately from the same paper text; neither implementation read the authors' code. At level 2 the two agreed numerically on the fixture's inputs; level 3 is recorded when property tests derived from the paper also passed on both, and each level 3 card prints how many its report lists. Where a model read the code against the paper's claim, each assembly's label verdict is one model's judgement, kept in this page's JSON twin; it is not calibrated, so no card prints it. A generated assembly's label was set when its code was generated for the method, and no model judged it; its card prints it as "by construction" or "not judged by a model". Siblings are assemblies lifted from this paper in the same batch for the same method: alternative readings kept side by side; none replaces or supersedes another. Where an assembly's phrase has no constructed figure, a brick that ran is not among the harvested samples this build reads, and whether a brick's run only constructed an object is read from that brick's harvested sample, so the figure was not counted; it does not say there were none.

5 assemblies on this paper: 4 harvested, 1 generated, listed in 2 groups (siblings lifted in one batch form one group).

generated Assembly for MOPO (graph method: MOPO), generated from the paper text, not the repository's code. 1 brick; individually on a fixture: 1 ran (1 with no instrument failure: 1 honoured, 0 violated, 0 with no contract checked; 0 where Syntology's instrument failed) · 0 unverified. Ran end-to-end against an independent peer; level 3 is recorded, but its report lists no property test that passed on both.

label matches by construction: the code was generated for this method (not judged by a model)

  1. compute_penalized_reward entry · level 3 · ran · honoured contract · b3588cd5c750128cb7ac5f8227b29162476bc36e5f554508ea0a892152dbb322

4 sibling assemblies for MOPO (harvested), lifted in the same batch on 2026-09-09: alternative readings kept side by side; none replaces or supersedes another.

harvested Assembly for MOPO (graph method: MOPO). 4 bricks; individually on a fixture: 3 ran (of which 2 constructed an object rather than computing a result; 3 with no instrument failure: 0 honoured, 0 violated, 3 with no contract checked; 0 where Syntology's instrument failed) · 1 unverified. The assembly has not been run end-to-end.

one of 4 siblings

  1. MOPOPolicy entry · level 0 · unverified · cee64d8d029d6485
  2. BaseDynamics helper · level 1 · ran · 0367ac63f92bed11
  3. SACPolicy helper · level 1 · ran · b3d37324c880e711
  4. BasePolicy helper · level 1 · ran · bc6ec59a73ed3500

harvested Assembly for MOPO (graph method: MOPO). 2 bricks; individually on a fixture: 1 ran (of which 0 constructed an object rather than computing a result; 0 with no instrument failure: 0 honoured, 0 violated, 0 with no contract checked; 1 where Syntology's instrument failed) · 1 unverified. The assembly has not been run end-to-end.

one of 4 siblings

  1. MOPO entry · level 0 · unverified · 4915612bb67c4977
  2. dict_batch_generator helper · level 1 · ran · our draft was wrong · 9bfce911836d13d9

harvested Assembly for MOPO (graph method: MOPO). 1 brick; individually on a fixture: 0 ran · 1 unverified. The assembly has not been run end-to-end.

one of 4 siblings

  1. train entry · level 0 · unverified · 2c8a2717c213a768

harvested Assembly for MOPO (graph method: MOPO). 3 bricks; individually on a fixture: 1 ran (of which 0 constructed an object rather than computing a result; 0 with no instrument failure: 0 honoured, 0 violated, 0 with no contract checked; 1 where Syntology's instrument failed) · 2 unverified. The assembly has not been run end-to-end.

one of 4 siblings

  1. MOPO entry · level 0 · unverified · 29dd6b4e1d20ae33
  2. FakeEnv model · level 0 · unverified · 905ff707fa717537
  3. format_samples_for_training helper · level 1 · ran · our draft was wrong · 1bb5583dba32f555

Each brick ends with its code_sha256, Syntology's identity for that exact code; click one to copy the get_code call that returns it. For agents, on Syntology's MCP service: assembly(arxiv_id="2005.13239") returns these assemblies with each brick's role and wiring (how to connect).

Tasks

Continuous ControlOffline RLReinforcement Learning (RL)continuous-controlmodel

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