Methods › Reinforcement Learning › Reinforcement Learning Frameworks › POMO › Papers where code ran, page 1
POMO
Papers archive 2025-07-28
archive papers tagged: 6 · with a code link: 5 · where Syntology ran a sample: 4 (3 with a run with no instrument failure, 1 where every run was a failure of Syntology's instrument) Syntology
Show: all tagged papersonly where code ran (4 of 6 tagged: 3 with a run with no instrument failure, 1 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 (3 with a run with no instrument failure, 1 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.
-
SVRPBench: A Realistic Benchmark for Stochastic Vehicle Routing Problem 28 May 2025 · 1 repository · arXiv:2505.21887Syntology official (archive's flag): 2 ran · 2 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; 0 where Syntology's instrument failed) · 0 unverified (of 2 harvested samples)
-
RL4CO: an Extensive Reinforcement Learning for Combinatorial Optimization Benchmark 29 Jun 2023 · 3 repositories · arXiv:2306.17100Syntology official (archive's flag): 9 ran · 12 ran (of which 0 constructed an object rather than computing a result; 12 with no instrument failure: 0 honoured, 0 violated, 12 with no contract checked; 0 where Syntology's instrument failed) · 4 unverified (of 16 harvested samples) · 3 pointer-only (licence)
-
Learning to Solve Routing Problems via Distributionally Robust Optimization 15 Feb 2022 · 1 repository · arXiv:2202.07241Syntology official: no sample here; runs from other or unrecorded repositories · 2 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; 2 where Syntology's instrument failed) · 1 unverified (of 3 harvested samples) · 3 pointer-only (licence)
-
POMO: Policy Optimization with Multiple Optima for Reinforcement Learning 30 Oct 2020 · 3 repositories · arXiv:2010.16011Syntology community repositories only · 1 ran (of which 0 constructed an object rather than computing a result; 1 with no instrument failure: 0 honoured, 0 violated, 1 with no contract checked; 0 where Syntology's instrument failed) · 7 unverified (of 8 harvested samples) · 8 pointer-only (licence)