Make seeded runs reproducible across releases and say how they depend on the backend

Abierto
  • ¿Algo no está bien?
#15 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
55/100
Tipo de issue
Nueva funcionalidad
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
python, rust
Área
backend, documentation, testing

Línea de trabajo

Start by locating the run implementation and its StdRng usage, then check the README, run docstrings, and the FAQ entry named in the issue. Read how backend="auto" selects its probability precision and inspect the existing seeded-run tests. Done means the generator is explicitly versioned, a fixed-seed test pins exact counts, and all three documentation locations describe reproducibility by engine version and backend.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

enhancement
What you want to do

run(seed=42) is documented as giving "repeatable counts", but:

  • StdRng does not guarantee the same random stream across rand versions, so counts may change
    after a dependency update;
  • with backend="auto", a machine with a GPU and one without sample from different probabilities
    (f32 vs f64), so the same seed can give different counts.
Implementation notes
  • Replace StdRng with an explicitly versioned generator such as rand_chacha::ChaCha8Rng or
    ChaCha20Rng, and add a test that pins the exact counts for a fixed seed, so a change is caught.
  • Update the README, run docstrings and the FAQ entry "Will the same seed give the same counts?"
What it could look like
No API change. The docs say: "the same seed gives the same counts with the same qsengine
version and backend".
Contributing
  • I would like to open a pull request for this (see CONTRIBUTING.md).
Lenguaje dominante
Rust
Estrellas
1
Forks
0
Merge medio
12 min
PR fusionados (30 d)
4

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de kaiwave/qsengine

Todos los issues de kaiwave/qsengine

Issues similares

Más issues de Rust

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.