Seeds and reproducibility

A seed fixes the random numbers a sampler draws with and nothing else. Batch composition, kernel selection, floating-point summation order, hardware and a silent provider revision all change the logits themselves, so the same seeded request can return different text on two execution paths. This chapter covers what the seed controls, why a near-tie flips under greedy decoding too, how to send one request down two paths and read the three possible outcomes, and what to log instead of relying on replay.

Sampling — read the current version at https://daviddominguez.dev/learn/en/sampling/random-seed

Back to top