Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Revise random generator interface in NEST #245

Closed
heplesser opened this issue Mar 1, 2016 · 2 comments · Fixed by #1549
Closed

Revise random generator interface in NEST #245

heplesser opened this issue Mar 1, 2016 · 2 comments · Fixed by #1549
Assignees
Labels
I: User Interface Users may need to change their code due to changes in function calls S: High Should be handled next T: Enhancement New functionality, model or documentation
Milestone

Comments

@heplesser
Copy link
Contributor

The interface to the random number generators in NEST, both in the kernel and at the SLI level, is clumsy and should be updated for NEST 3. Specifically, we should

  • provide an easy way to seed all kernel RNGs using a single master seed
  • provide an easy way to change the type of RNG used in the kernel
  • make changing and seeding kernel RNGs easy from the Python level
  • consider changing the default RNG type from Knuth to MersenneTwister
  • review the algorithms used for non-uniform random deviate generation
  • review whether buffering random numbers really makes sense wrt performance
  • simplify the way RNG creation is handled on the SLI level (eliminate RNG and RDV factory objects)

This is a follow-up to trac.146, trac.437 and trac.669.

@heplesser heplesser added ZC: Kernel DO NOT USE THIS LABEL I: User Interface Users may need to change their code due to changes in function calls ZP: Pending DO NOT USE THIS LABEL S: High Should be handled next T: Enhancement New functionality, model or documentation labels Jun 29, 2017
@heplesser heplesser added this to the NEST 3.0 milestone Jun 29, 2017
@ikitayama
Copy link

@heplesser Is there a work-in-progress branch to give it a try?

@jougs
Copy link
Contributor

jougs commented Apr 25, 2018

@ikitayama: I only have a preliminary prototype at the moment and definitely won't be able to finish it before the end of May. You can watch out for the corresponding pull request here and just chime in if you experience any problems on K then.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
I: User Interface Users may need to change their code due to changes in function calls S: High Should be handled next T: Enhancement New functionality, model or documentation
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants