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

未关闭
  • 哪里不对？
#15 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
55/100
Issue 类型
功能
描述清晰度
描述清楚
活跃度
活跃
技术栈
python, rust
领域
backend, documentation, testing

调研方向

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.

由索引模型根据 Issue 内容生成。

描述

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).
主要语言
Rust
星标
1
派生
0
平均合并
12 分钟
30 天内合并 PR
4

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

kaiwave/qsengine 的其他 Issue

查看 kaiwave/qsengine 的全部 Issue

相似的 Issue

更多 Rust Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。