Home › Code › merge_configs

merge_configs

Syntologyentry name in harvested code

Syntology's record for this page last changed ; when this build read Syntology's graph is in the build record.

merge_configs appears in the code Syntology harvested for 11 papers, as 11 distinct code bodies found in 11 places (a place is one code body under one paper). Of the 11 papers, 11 with a sample that ran: 7 with a run with no instrument failure, 4 where every run was a failure of Syntology's instrument. 1 of the code bodies carries a behaviour fingerprint.

What this page is not. Routines are grouped here by the exact string of their function or class name. Nothing asserts that two samples named merge_configs do the same thing, share code, or are comparable; the name is a string, not an identity. Behaviour outputs (what a fingerprinted sample returned on the shared battery) are not in this export and are not shown here; get_code(code_sha256="…") returns this sample's fingerprint on the shared battery, with the battery's shuffled null and lift; not shown on this site (how to connect). "Ran" means executed on a synthesized fixture, not that the code is correct or reproduces a paper.

Samples Syntology

The 11 distinct code bodies named merge_configs: 11 ran (of which 0 constructed an object rather than computing a result; 7 with no instrument failure: 0 honoured, 0 violated, 7 with no contract checked; 4 where Syntology's instrument failed) · 0 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. One tile per status, in the site's fixed vocabulary, each code body counted once:

0ran · honoured contract
0ran · violated contract
4ran · our draft was wrong
0ran; the contract check could not run
7ran
0unverified
1fingerprinted

Licence is a property of each copy, so it is counted per place: 1 of the 11 places is pointer only (Syntology does not serve that copy's text). This site shows no code text for any sample; every row below links to the file in its repository where the record names one.

“Ran” means the sample executed on a synthesized input; it does not mean the output is correct. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself; “our draft was wrong” and “the contract check could not run” (RAISES, DEP_MISSING or TIMEOUT; hover a row's label for which) are failures of Syntology's instrument, not of the code, and those samples did run. The ran count above is every status except unverified, the same rule as each paper page; “with no instrument failure” is honoured, violated and ran with no contract checked. A metamorphic tier, where shown, is evidence of the output's shape, not that the sample implements the method.

Papers

11 papers shown of 11, newest first; 11 places in the table. A paper with no recorded date is placed by the month its arXiv id encodes, shown in the Date column as YYYY-MM (from id). One row per place: a paper whose repository defines the name more than once appears more than once, and the same code body held for several papers appears once under each, with the same status. Titles and dates are the archive's archive 2025-07-28 for papers in the archive, and the graph's for 2 papers added by Syntology; 1 papers have no page here and are shown by their id only (arXiv: for an arXiv id; an id from another venue, such as ACL Anthology or AAAI, is named as that venue's id, never as an arXiv id). Status and fingerprint are Syntology's record of each code body; licence is recorded for each place. The File cell ends with the code body's 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.

PaperDateFileStatus SyntologyLicence
Towards Resource-Efficient LLMs: End-to-End Energy Accounting of Distillation Pipelines added by Syntology 2026-05 (from id) StellarLuminosity/Energy/distill_bench/core/config_loader.py ec6c6fa1db88bcea ran · our draft was wrong no licence file found · pointer only
IRPAPERS: A Visual Document Benchmark for Scientific Retrieval and Question Answering added by Syntology 2026-02 (from id) weaviate/query-agent-benchmarking/query_agent_benchmarking/internal/config/loader.py 056bbbb54bdfab38 ran · our draft was wrong BSD-3-Clause (permissive)
Query-Focused Retrieval Heads Improve Long-Context Reasoning and Re-ranking 11 Jun 2025 princeton-pli/QRHead/src/qrretriever/config.py 1b2be7c22837418d ran MIT (permissive)
Beyond Scalars: Concept-Based Alignment Analysis in Vision Transformers 9 Dec 2024 jvielhaben/nlmcd-align/executable_scripts/concept_discovery.py 794ca756a3cb0145 ran · our draft was wrong MIT (permissive)
CuNeRF: Cube-Based Neural Radiance Field for Zero-Shot Medical Image Arbitrary-Scale Super Resolution 28 Mar 2023 NarcissusEx/CuNeRF/src/utils.py 7bf720cc3d1aca64 ran MIT (permissive)
Spacerini: Plug-and-play Search Engines with Pyserini and Hugging Face 28 Feb 2023 cookiecutter/cookiecutter/cookiecutter/config.py 7cd35c0d6160808f ran BSD-3-Clause (permissive)
DHRL: A Graph-Based Approach for Long-Horizon and Sparse Hierarchical Reinforcement Learning 11 Oct 2022 jaylee0301/dhrl_official/DHRL/rl/algo/dhrl.py 4b9723d766ef342e ran · our draft was wrong MIT (permissive)
Panoptic-PolarNet: Proposal-free LiDAR Point Cloud Panoptic Segmentation 27 Mar 2021 edwardzhou130/Panoptic-PolarNet/utils/configs.py 493b63fa4db39051 ran BSD-3-Clause (permissive)
Would Mega-scale Datasets Further Enhance Spatiotemporal 3D CNNs? 10 Apr 2020 KevinPang180/3D-ResNets-PaddlePaddle/config.py 0e03ada3bc54e4fb ran Apache-2.0 (permissive)
Exploring Randomly Wired Neural Networks for Image Recognition 2 Apr 2019 hebo1221/RandWireNN/utils/config_helpers.py 9c0c354019b5b11c ran fingerprinted Apache-2.0 (permissive)
CVF open access id Nguyen_ESCAPE_Encoding_Super-keypoints_for_Category-Agnostic_Pose_Estimation_CVPR_2024_paper khoiucd/escape-tgt/cluster.py 779e663e48438326 ran Apache-2.0 (permissive)

This site shows no code text; each File cell links to the file on GitHub at the repository's current default branch, which may have changed since the 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 under a permissive licence, but the stored copy of the same code that Syntology serves is not cleared for its text. 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 cell for the reason. Per-sample records for a paper are on its paper page under "Code Syntology ran".

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