Home › Code › append_log

append_log

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.

append_log appears in the code Syntology harvested for 14 papers, as 4 distinct code bodies found in 14 places (a place is one code body under one paper). Of the 14 papers, 1 with a sample that ran: 0 with a run with no instrument failure, 1 where every run was a failure of Syntology's instrument. 0 of the code bodies carry 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 append_log 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 4 distinct code bodies named append_log: 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) · 3 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
1ran · our draft was wrong
0ran; the contract check could not run
0ran
3unverified
0fingerprinted

Licence is a property of each copy, so it is counted per place: 9 of the 14 places are pointer only (Syntology does not serve that copy's text); at 7 of those 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 (hover the licence cell for why). 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

14 papers shown of 14, newest first; 14 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 1 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
An Empirical Study of Privacy Leakage Chains via Prompt Injection in Black-Box Chatbot Environments added by Syntology 2026-05 (from id) In-Sam/Kill-Chain-of-Privacy-Leakage-via-Prompt-Injection/prompt_injection/log_analyzer.py 2266d9e028d0a26e ran · our draft was wrong no licence file found · pointer only
arXiv:2507.08387 2025-07 (from id) shlee94/Off2OnRL/rlkit/rlkit/core/logging.py 46e6d80fdfab6884 unverified no licence file found · pointer only
Adaptive $Q$-Aid for Conditional Supervised Learning in Offline Reinforcement Learning 3 Feb 2024 rail-berkeley/rlkit/rlkit/core/logging.py 46e6d80fdfab6884 unverified MIT (permissive) here; the stored copy is pointer only
Variational Curriculum Reinforcement Learning for Unsupervised Discovery of Skills 30 Oct 2023 seongun-kim/vcrl/vcrl/core/logging.py 46e6d80fdfab6884 unverified MIT (permissive) here; the stored copy is pointer only
PID-Inspired Inductive Biases for Deep Reinforcement Learning in Partially Observable Control Tasks 12 Jul 2023 IanChar/GPIDE/rlkit/core/logging.py 46e6d80fdfab6884 unverified MIT (permissive) here; the stored copy is pointer only
Stabilizing Contrastive RL: Techniques for Robotic Goal Reaching from Offline Data 6 Jun 2023 chongyi-zheng/stable_contrastive_rl/rlkit/core/logging.py 9817c2d99db83a09 unverified MIT (permissive)
Adaptive and Explainable Deployment of Navigation Skills via Hierarchical Deep Reinforcement Learning 2023-05 (from id) leekwoon/hrl-nav/src/rlkit/core/logging.py 46e6d80fdfab6884 unverified MIT (permissive) here; the stored copy is pointer only
S2P: State-conditioned Image Synthesis for Data Augmentation in Offline Reinforcement Learning 30 Sep 2022 dsshim0125/s2p/rlkit/core/logging.py 46e6d80fdfab6884 unverified MIT (permissive) here; the stored copy is pointer only
Mildly Conservative Q-Learning for Offline Reinforcement Learning 9 Jun 2022 vitchyr/rlkit/rlkit/core/logging.py 46e6d80fdfab6884 unverified MIT (permissive) here; the stored copy is pointer only
Augmenting Reinforcement Learning with Behavior Primitives for Diverse Manipulation Tasks 7 Oct 2021 UT-Austin-RPL/maple/maple/core/logging.py 46e6d80fdfab6884 unverified MIT (permissive) here; the stored copy is pointer only
What Can I Do Here? Learning New Skills by Imagining Visual Affordances 1 Jun 2021 patrickhaoy/ptp/rlkit/core/logging.py 9817c2d99db83a09 unverified MIT (permissive)
Benchmarking Unsupervised Object Representations for Video Sequences 12 Jun 2020 ecker-lab/object-centric-representation-benchmark/ocrb/op3/core/logging.py 1029760706cbba76 unverified MIT (permissive)
Entity Abstraction in Visual Model-Based Reinforcement Learning 28 Oct 2019 jcoreyes/OP3/op3/core/logging.py 1029760706cbba76 unverified MIT (permissive)
Contextual Imagined Goals for Self-Supervised Robotic Learning 23 Oct 2019 anair13/rlkit/rlkit/core/logging.py 9817c2d99db83a09 unverified MIT (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