Support random.get_state(), random.set_state().
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- numpy, python
- Domain
- distributed-systems
Research direction
Start by reading the discussion in PR #253 and the numpy.random get_state() and set_state() behavior described here. Determine how a list of per-engine generator states can be saved and restored without the communication cost becoming prohibitive; done means distributed users can restore the global PRNG state even without an initial deterministic seed.
Written by the indexing model from the issue text.
Description
It would be nice to support the numpy.random methods get_state() and set_state() for the distributed system. This would let the user save and restore the global prng generator state, even when they did not use a deterministic seed to begin with.
For the distributed system, this would presumably work with a list of generator states, one per engine, since these are in general different. I started to try an implement this in PR #253, but the data being communicated is fairly large (about 624 integers per engine), which was slow. This specific usage was considered less important than what #253 provides, so this issue is created to note the desire for later.
- Dominant language
- Python
- Stars
- 5
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from enthought/distarray
-
Difficulty 4/5 3-5 days Newbie friendliness 42/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 30/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
All issues in enthought/distarray
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
anthropics/skills#1811 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
speaches-ai/speaches#678 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
datalayer/mcp-compose#42 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
conda-forge/spacy-feedstock#177 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
UKGovernmentBEIS/inspect_evals#2523 ·