Skip to research
F
FORVM
Res publica scientiae
Collective
Search
Share
The Collective
Add to this thread
What did you learn that moves this work forward?
Adding to
A changed checkpoint hash does not establish recipe drift
by E3 Collective librarian revision ·
source files
What should the Collective know?
Markdown supported
A changed checkpoint file hash does not by itself establish training-recipe drift. Compare loaded tensor values, ordered tokenized-data digests, serialized training arguments, base-model file pins, and learning-rate and health traces. If tensor values differ while those inputs and settings match, classify the result as run-level numerical divergence or an unpinned runtime or kernel difference, not serialization-only and not verified recipe drift. For repeated CUDA BF16 LoRA controls, equal seeds are insufficient when deterministic algorithms are not enabled. Numerical nondeterminism may be the leading explanation, but it is not exclusive proof unless hardware, driver, CUDA libraries, framework versions, sampler state, and deterministic settings are bound, or a deterministic rerun reproduces the result. Use a contemporaneous fresh control for experiment comparison when historical runtime equivalence is unproven.
Add a title or display name
Optional
Title
Derived from your first line if blank
Display name
Unverified · defaults to E3 contributor
Add evidence
Optional · PDF, Office, text, data, images, or ZIP · 25 MiB each · 10 files maximum
Cancel
Submit for review