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.

Sign up for GitHub

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

Jump to bottom

Improve tests for randomized generators #348

Closed
jougs opened this issue May 18, 2016 · 2 comments
Closed

Improve tests for randomized generators #348

jougs opened this issue May 18, 2016 · 2 comments
Assignees
@hakonsbm
Labels
I: No breaking change Previously written code will work as before, no one should note anything changing (aside the fix) S: Normal Handle this with default priority T: Maintenance Work to keep up the quality of the code and documentation. ZC: Infrastructure DO NOT USE THIS LABEL ZP: In progess DO NOT USE THIS LABEL

Comments

@jougs
Copy link
Contributor

jougs commented May 18, 2016

  • From manualtests, test_sinusoidal_poisson_generator_{5,6}.sli should be made to work as automated MPI tests.
  • We currently have no tests of the statistical properties of spike trains generated by randomized generators. That should be fixed.
@heplesser heplesser added ZC: Infrastructure DO NOT USE THIS LABEL I: No breaking change Previously written code will work as before, no one should note anything changing (aside the fix) ZP: In progess DO NOT USE THIS LABEL S: Normal Handle this with default priority T: Maintenance Work to keep up the quality of the code and documentation. labels Jun 29, 2017
@heplesser heplesser mentioned this issue Jun 30, 2017
Closed
@hakonsbm hakonsbm mentioned this issue Jun 30, 2017
Open
@hakonsbm
Copy link
Contributor

As these points are pretty different tasks, I am creating a PR regarding your first point, and I have created a separate issue, #773, for your second point.

@hakonsbm hakonsbm mentioned this issue Jun 30, 2017
Merged
@heplesser
Copy link
Contributor

I am closing this one since follow-up issues have been created, and part of the issue has been addressed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@hakonsbm hakonsbm

Labels
I: No breaking change Previously written code will work as before, no one should note anything changing (aside the fix) S: Normal Handle this with default priority T: Maintenance Work to keep up the quality of the code and documentation. ZC: Infrastructure DO NOT USE THIS LABEL ZP: In progess DO NOT USE THIS LABEL
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@heplesser @jougs @hakonsbm