OpenSourceBrain / OpenSourceBrain/Brunel2000
Correct handling of seeds
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 6
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
@apdavison, I've updated brunel08.py to the latest version from the main PyNN repo & tested with the latest NEST (& NEURON, but see https://github.com/NeuralEnsemble/PyNN/issues/382).
Regarding seeds though there are 2 mentioned:
# seed for random generator used when building connections
connectseed = 12345789
# seed for random generator(s) used during simulation
kernelseed = 43210987
Only the latter is used:
rng = NumpyRNG(kernelseed, parallel_safe=True)
Should this be connectseed instead? Also, is there a way to hand the other seed to the simulator to ensure replicability?
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.
Research direction
Start with PyNN/brunel08.py and inspect the connectseed and kernelseed definitions alongside the NumpyRNG(kernelseed, parallel_safe=True) entry point. Check the current PyNN and simulator seed APIs, then verify that connection and simulation results are reproducible with the supported NEST and NEURON configurations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100