Execution attempt

Sign in with GitHub
← Experiment E5 · How much of the change from an untouched model to the same model after an APT4 transplant and continued pretraining is attributable to the continued pretraining rather than to the tokenizer replacement, when the original-tokenizer model receives identical continued pretraining?

Execution attempt · A50 · planned

Aggregates the scoring rows into the per-split decomposition, the gap per milestone, the probe curves and the paired digit comparison at 500M.

Succeeded · Registered by @stw2 via agent. Reported and received times are kept apart; no computation or result is verified.

Pinned source and configuration

https://github.com/stw2/tokenizer-science-tax @ 9a57aa40f4e774136f51b6730c33266d59094a45

Reference checked 2026-09-14 13:12 UTC. Later commits, branches or plan changes do not retarget this attempt.

Command
python scripts/09_analyze.py
Working directory
experiments/E05-control-arm
Configuration paths
None
Parameters
No random numbers. The ported script regenerates analysis.json byte for byte from the ported rows.
Environment
3 (standard library only; version unrecorded); Python standard library; Apple silicon, 128 GB unified memory
Output directory
Not recorded

Inputs

Materials the registrant named when registering this attempt, by content identity; obtainability is derived from their location reports. Nothing is fetched or verified.

Delivered events

  1. Registered

    #1

    Aggregates the scoring rows into the per-split decomposition, the gap per milestone, the probe curves and the paired digit comparison at 500M.

    reported · received · @stw2 via agent · posted to the Thread

  2. Started

    #2

    Started.

    reported · received · @stw2 via agent · attempt only

  3. Succeeded

    #3

    Completed with exit code 0.

    Exit code 0.

    • analysis.json · https://github.com/stw2/tokenizer-science-tax/blob/9a57aa40f4e774136f51b6730c33266d59094a45/experiments/E05-control-arm/results/analysis.json · public · sha256 0a35c4555c70… · 27452 bytes · M187

    reported · received · @stw2 via agent · posted to the Thread

Report an event

The registrant’s capture tool normally delivers start and outcome events. Reporting here is the same author report with the browser as the reported time; it does not observe the process.

This attempt has a delivered outcome. A new execution is a new attempt.