Methods › General › Distributed Methods › IMPALA › Papers where code ran, page 1
IMPALA
Papers archive 2025-07-28
archive papers tagged: 16 · with a code link: 10 · where Syntology ran a sample: 4 (4 with a run with no instrument failure, 0 where every run was a failure of Syntology's instrument) Syntology
Show: all tagged papersonly where code ran (4 of 16 tagged: 4 with a run with no instrument failure, 0 where every run was a failure of Syntology's instrument)
Syntology We ran code from the paper's repository; we did not isolate this method inside it.
Page 1 of 1: papers 1 to 4 of the 4 tagged papers where Syntology ran at least one harvested sample (4 with a run with no instrument failure, 0 where every run was a failure of Syntology's instrument), newest first by the archive's date (ties by arXiv id). This is a filter on Syntology's record ordered by date only, not a ranking; a run is not a correctness claim. A paper missing from this list is not a recorded non-run: it may have no arXiv id, no harvested code, or only samples that have not run yet.
Repository counts are the archive's code-links table. A Syntology line states what Syntology ran from that paper's harvested code, as “N ran (of which C constructed an object rather than computing a result; K with no instrument failure: H honoured, V violated, P with no contract checked; I where Syntology's instrument failed) · U unverified”; the instrument figure counts failures of Syntology's instrument, not of the code. It is per sample and not a correctness claim. When the archive marks a repository official for the paper, the line starts with that repository's state (the archive's flag, not a verdict on who wrote the code; “community repositories only” when every sample that ran came from a community repository, “official: no sample here; runs from other or unrecorded repositories” when some came from a repository the paper names or has in its text, or from none recorded); hover it for the repositories the samples that ran came from.
-
Cleanba: A Reproducible and Efficient Distributed Reinforcement Learning Platform 29 Sep 2023 · 1 repository · arXiv:2310.00036Syntology official (archive's flag): 4 ran · 4 ran (of which 0 constructed an object rather than computing a result; 4 with no instrument failure: 0 honoured, 0 violated, 4 with no contract checked; 0 where Syntology's instrument failed) · 4 unverified (of 8 harvested samples) · 8 pointer-only (licence)
-
EnvPool: A Highly Parallel Reinforcement Learning Environment Execution Engine 21 Jun 2022 · 3 repositories · arXiv:2206.10558Syntology official (archive's flag): 3 ran · 5 ran (of which 0 constructed an object rather than computing a result; 4 with no instrument failure: 0 honoured, 0 violated, 4 with no contract checked; 1 where Syntology's instrument failed) · 0 unverified (of 5 harvested samples) · 1 pointer-only (licence)
-
TorchBeast: A PyTorch Platform for Distributed RL 8 Oct 2019 · 3 repositories · arXiv:1910.03552Syntology official (archive's flag): 3 ran · 6 ran (of which 0 constructed an object rather than computing a result; 2 with no instrument failure: 0 honoured, 0 violated, 2 with no contract checked; 4 where Syntology's instrument failed) · 3 unverified (of 9 harvested samples) · 3 pointer-only (licence)
-
IMPALA: Scalable Distributed Deep-RL with Importance Weighted Actor-Learner Architectures 5 Feb 2018 · 24 repositories · arXiv:1802.01561Syntology community repositories only · 16 ran (of which 6 constructed an object rather than computing a result; 10 with no instrument failure: 1 honoured, 1 violated, 8 with no contract checked; 6 where Syntology's instrument failed) · 18 unverified (of 34 harvested samples) · 3 pointer-only (licence)