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 · A37 · planned

Packs the same document sequence with the APT4 tokenizer for arm B.

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 @ 4d64dedcbe57761c48ea37d5ce80cb6c86198236

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

Command
python scripts/02_pack.py --arm apt4 --eos-id 2
Working directory
experiments/E05-control-arm
Configuration paths
None
Parameters
Same order as arm A; documents separated by </s> (id 2), uint16; about 1.067B tokens. The --eos-id 2 argument is recorded in the design and a later provenance note, not in a log. Run time not recorded.
Environment
unrecorded; CPU tokenization; one CUDA GPU, 16 GB
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

    Packs the same document sequence with the APT4 tokenizer for arm B.

    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.

    • apt4.bin · Not kept: written on the original training machine and never copied; rebuild with scripts/02_pack.py at the pinned revisions · unavailable
    • apt4.meta.json · Not kept: written on the original training machine and never copied; rebuild with scripts/02_pack.py at the pinned revisions · unavailable

    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.