vh
dae77ee118
Rehome run 3c from ana-ml2 to pfi-gx10 unchanged: same corpus, base,
recipe and hyperparameters, different host. Slower (~13.3 h vs ~2.5 h)
and correct — an Anaheim breaker trip costs a 40-minute drive each way
and 13 hosts down, three of them SureFire client machines, while the
GX10 is a ~240 W appliance at NH3 that can take nothing else down.
Verified rather than assumed, because ana-ml2 ran transformers 5.15.1
on x86-64 and this box runs 5.16.1 on aarch64 — the silent
backend-delta class that has already voided conclusions here:
- both 49 GB base shards sha256-match ana-ml2's (size equality is a
weaker claim and was already true)
- a full encode was run into a throwaway dir and the encoded corpus
compared byte-for-byte: 197,360,233 B, sha256 c08bb1fe2ecb0be3,
identical. Every aggregate matched too. That verified artifact is
what the run will train on — it is seeded into run-03c/encode-cache
- the harness's own suite: 122 passed on aarch64
- the config generator asserts key-by-key that no non-path value
differs from run-03c.json
The encode-cache filename differs by design (base_model_path is part of
the key) — an input hash, not an output hash. Documented so it is not
misread as drift, or "fixed" by faking /tank on this box.
Corpus is copied to local NVMe; the box mounts no NFS. nh3-nas is now on
the same subnet, which makes mounting it tempting and still wrong under
a 13 h unattended run.
The launcher refuses on a live pidfile rather than a pgrep: `pgrep -f
erp_sft_harness` invoked over ssh matches the invoking shell's own argv.
That self-match cost a shell during staging.
Not launched. 13.3 h is the operator's call.
930 B
930 B
erp-tune on pfi-gx10
Canonical copies of what is staged on pfi-gx10 for ERP-seat SFT run 3c — the LoRA that died on ana-ml2 at step 24 of 604 when an Anaheim breaker tripped.
| file | deployed to |
|---|---|
run-03c-gx10.json |
/home/infra-ops/erp-tune/run-03c-gx10.json |
launch-run-03c.sh |
/home/infra-ops/erp-tune/launch-run-03c.sh |
run-03c-gx10.json is ana-ml2:/tank/erp-tune/run-03c.json with its eight path
keys rehomed to local NVMe and two substitute_controls entries appended
recording the host move and the library delta. No hyperparameter, corpus,
base, mask or recipe value differs — verified key-by-key at generation.
Full context, what was verified and how to launch:
docs/runbooks/gx10-run-03c.md.
The harness itself (eitri-smithy) is not vendored here; it lives on the box at
/home/infra-ops/erp-tune/eitri-smithy, git 0a6bd2e.