lm_understand-logs README

The project's README from github.com/RikiyaT/lm_understand-logs. As one markdown file: README.md.

Logs: LLMs can understand and write neural network weights

The complete logs of every experiment in the blog post Sparks of Weight Space Programming: LLMs can understand and write neural network weights. For each experiment you get:

Each experiment folder has its own README. It says which run is which tab or row in the post, and which file each number comes from.

Folder In the post Runs Tools
exp1_which_game/ Experiment 1: which game was this network trained on? Breakout, Pong, Pac-Man, Freeway (open answer) none
exp2_diffusion/ Experiment 2: what does this diffusion model generate? circle, square, triangle none, no forward pass
exp3_language/ Experiment 3: which language a language model learned, from its middle blocks Python, romaji, English, two conversations each Python sandbox, no forward pass
exp4_fix_car/ Experiment 4: fix a failing network by editing its weights one one-shot edit none
exp5_write_from_scratch/ Experiment 5: write networks from scratch Breakout, Seaquest, Asterix (MinAtar) none
exp6_go_from_scratch/ Experiment 6: write a 1.5M-weight Go network 0, 10, 25 and 50 passes Python sandbox
exp7_sycophancy/ Experiment 7: which language model is sycophantic? four weights-only attempts, then the attention tool (3 pairs each) Python sandbox
exp8_math/ Experiment 8: make a language model better at math Qwen3.5-0.8B with 10, 25 and 50 passes, and the Gemma 3 270M follow-up Python sandbox

Only the runs the post reports are here. Trial runs of earlier prompt versions are left out.

How the model was run

"Astra" in the post is OpenAI's gpt-6-astra.

One turn. Every turn is one call of the Codex CLI: codex exec, or codex exec resume <thread> to continue a conversation. The prompt goes in on stdin. The reasoning effort is set per call and recorded in each turn's run.json:

Effort Experiments
high 1, 2, 4
xhigh 3, 5, 6, 7
max 8

No tools of its own. Every built-in Codex capability that gives the model a tool is switched off: shell, file editing, web search, image viewing, sub-agents, plugins and the rest. The configuration is in harness/codex_config.toml, and the system instructions are one neutral line, harness/instructions.md. Each call names the model and the effort itself, overriding the defaults in that file.

Every turn was audited. We checked each turn's event stream. A turn counts as tool-free when the stream holds only the model's messages, its reasoning summaries, and Codex's notice that code mode is disabled. The result is the audit.tool_free field of the turn's run.json. All 1,125 turns in this release are tool-free.

Where code was allowed (Experiments 3, 6, 7, 8):

Files

Not every file appears in every run.

File What it is
prompt.txt, message.txt What we sent: the first message, and later ones per turn.
events.jsonl The raw Codex event stream of one turn: the model's messages and reasoning summaries, plus token usage.
answer.md, turn_text.md, final_answer.md The model's reply in one turn, and its final reply.
explanations.md The model's explanation of each step, collected over the run, where the prompt asked for one.
tool_calls.jsonl One line per sandbox run: the code, its printed output, and the time it took.
run.json One turn's record: model, effort, tokens, wall time, and the audit.
state.json One conversation's record: turns, runs used, and whether it finished.
loop.log, driver.log, run.log The harness's log of the run.
eval/ The scoring, with the answer key or ground truth.
networks/ The networks the model read or wrote.

Placeholders. Internal paths are replaced by placeholders:

Placeholder Stands for
<data> our data disk
<repo> our experiment repository
<codex> the Codex binary
<codex_home> Codex's state folder
<venvs> Python environments
<home> home directory
<remote> a rented GPU node

Codex thread ids are replaced by id- and 8 hex digits. The same thread keeps the same id in every file, so turns of one conversation still match up.

Not included

Licenses

See LICENSE.

Content License
Logs, data and networks CC BY 4.0
Our scripts MIT
MinAtar source in Experiment 5's prompts GPL-3.0, see exp5_write_from_scratch/LICENSE-MinAtar

Third-party benchmark data keep their own licenses: MATH, GSM8K, IFEval, MMLU-Pro and the others in Experiment 8.

lm_understand-logs (RikiyaT/lm_understand-logs)

Searching Database…

What is this?The complete logs of every experiment in the blog post 'Sparks of Weight Space Programming: LLMs can understand and write neural network weights'. It has the prompts sent to the model, its replies, the code it ran, the evaluation behind each number, and the networks it read or wrote.
Is it a tool or library, or just data?It's a data release, not a program. There is no package to install; it's files with prompts, model replies, sandbox code and output, scoring and networks.
How do I find the run I care about?Open the folder of the experiment you want, such as exp4fixcar/, and read its README first. It maps each run to the tab or row in the post and names the file each number comes from.
Which model and tools were used?'Astra' is OpenAI's gpt-6-astra, run through the Codex CLI with one turn per call and all built-in tools switched off. Code was run only in Experiments 3, 6, 7 and 8, inside the author's own sandbox with no network.
What is missing from the release?Not included: the 17 GB Gemma 3 270M fine-tunes from Experiment 7, the intermediate files the model wrote while working, the text of Experiment 3's Python corpus, and the GPQA question texts in Experiment 8. Rebuild scripts and hashes are provided for some of these.
Does the model use tools during these experiments?Not built-in Codex tools: all 1,125 turns were audited as tool-free. Code execution happened only in a custom Python sandbox in Experiments 3, 6, 7 and 8.
What is the weight-space programming idea?The experiments test whether an LLM can read a neural network's weights and then edit or write them. Examples include fixing a failing network in Experiment 4 and writing a 1.5M-weight Go network in Experiment 6.
Can the model write game-playing networks from scratch?Experiment 5 asks the model to write networks from scratch for Breakout, Seaquest and Asterix in MinAtar, with no tools. The logs show each attempt and its evaluation.
What are similar projects?jeeves, NanoJev, bdh, detectorscope, math, Valen, MSA, pointdit
Creator
RikiyaT
Size
135.4 MB
Stars
732
Updated
CommitOct 29
Age
5d
Commits · 90 Days