From f16ece488fd8a9c363ac26bd7ca7e14abfef554f Mon Sep 17 00:00:00 2001 From: Andrej Karpathy Date: Sun, 8 Mar 2026 23:16:30 +0000 Subject: [PATCH] clarification to baseline run instruction, there was some language from a previous version that wasn't fully cleaned up --- program.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/program.md b/program.md index 598f776..28d37cf 100644 --- a/program.md +++ b/program.md @@ -13,7 +13,7 @@ To set up a new experiment, work with the user to: - `prepare.py` — fixed constants, data prep, tokenizer, dataloader, evaluation. Do not modify. - `train.py` — the file you modify. Model architecture, optimizer, training loop. 4. **Verify data exists**: Check that `~/.cache/autoresearch/` contains data shards and a tokenizer. If not, tell the human to run `uv run prepare.py`. -5. **Initialize results.tsv**: Create `results.tsv` with header row and baseline entry. The baseline results are already known from the output format section below (val_bpb: 0.997900, peak_vram_mb: 45060.2). Do NOT re-run the baseline — just record it. +5. **Initialize results.tsv**: Create `results.tsv` with just the header row. The baseline will be recorded after the first run. 6. **Confirm and go**: Confirm setup looks good. Once you get confirmation, kick off the experimentation.