Methods › General › Parameter Norm Penalties › ROME › Papers where code ran, page 1
Rank-One Model Editing
ROME
Papers archive 2025-07-28
archive papers tagged: 23 · with a code link: 15 · where Syntology ran a sample: 7 (5 with a run with no instrument failure, 2 where every run was a failure of Syntology's instrument) Syntology
Show: all tagged papersonly where code ran (7 of 23 tagged: 5 with a run with no instrument failure, 2 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 7 of the 7 tagged papers where Syntology ran at least one harvested sample (5 with a run with no instrument failure, 2 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.
-
R2R: Efficiently Navigating Divergent Reasoning Paths with Small-Large Model Token Routing 27 May 2025 · 1 repository · arXiv:2505.21600Syntology official (archive's flag): 1 ran · 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) · 0 unverified (of 1 harvested sample)
-
Understanding the Collapse of LLMs in Model Editing 17 Jun 2024 · 1 repository · arXiv:2406.11263Syntology 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 (of 2 harvested samples) · 1 pointer-only (licence)
-
Is Bigger Edit Batch Size Always Better? -- An Empirical Study on Model Editing with Llama-3 1 May 2024 · 1 repository · arXiv:2405.00664Syntology 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) · 2 pointer-only (licence)
-
Rebuilding ROME : Resolving Model Collapse during Sequential Model Editing 11 Mar 2024 · 1 repository · arXiv:2403.07175Syntology official (archive's flag): 13 ran · 13 ran (of which 0 constructed an object rather than computing a result; 10 with no instrument failure: 0 honoured, 0 violated, 10 with no contract checked; 3 where Syntology's instrument failed) · 2 unverified (of 15 harvested samples) · 10 pointer-only (licence)
-
Model Editing at Scale leads to Gradual and Catastrophic Forgetting 15 Jan 2024 · 1 repository · arXiv:2401.07453Syntology official (archive's flag): 7 ran · 7 ran (of which 0 constructed an object rather than computing a result; 5 with no instrument failure: 0 honoured, 0 violated, 5 with no contract checked; 2 where Syntology's instrument failed) · 2 unverified (of 9 harvested samples) · 9 pointer-only (licence)
-
Can Sensitive Information Be Deleted From LLMs? Objectives for Defending Against Extraction Attacks 29 Sep 2023 · 1 repository · arXiv:2309.17410Syntology official (archive's flag): 9 ran · 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) · 5 unverified (of 14 harvested samples)
-
Locating and Editing Factual Associations in GPT 10 Feb 2022 · 4 repositories · arXiv:2202.05262Syntology official (archive's flag): 1 ran · 4 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; 2 where Syntology's instrument failed) · 11 unverified (of 15 harvested samples)