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

Boost randon number generator #19

Open
toeklk opened this issue Dec 9, 2017 · 0 comments
Open

Boost randon number generator #19

toeklk opened this issue Dec 9, 2017 · 0 comments
Labels

Comments

@toeklk
Copy link
Collaborator

toeklk commented Dec 9, 2017

migrated from Bugzilla #491
status NEW severity normal in component wrappers for 0.7.0
Reported in version trunk on platform All
Assigned to: BFL mailinglist

Original attachment names and IDs:

On 2008-01-18 13:27:55 +0100, Tinne De Laet wrote:

  Apparently, calling sampleFrom on a Gaussian always results in the same set of samples when using Boost as a random number generator. It appears like boost has a fixed list of random samples, resulting in the same samples when executing the program multiple times. This problem does not occur when using lti as a randon number generator. Is this an intrinsic problem with Boost (or are we not using the rng properly)? I found the following note on http://www.boost.org/libs/random/random-generators.html "Note: These random number generators are not intended for use in applications where non-deterministic random numbers are required. See nondet_random.html for a choice of (hopefully) non-deterministic random number generators." So maybe we should use the proposed class when we want non-deterministic randon numbers. Tinne

On 2008-01-18 17:06:35 +0100, Tinne De Laet wrote:

  This bug causes the new pdf_test (see BUG # 441, Attachment # 214) to fail deterministically. Apparently the 496'th sample is located outside the 4 sigma region. Tinne

On 2008-02-09 20:13:47 +0100, Klaas Gadeyne wrote:

  Created attachment 233 quick-n-dirty fix for the test This patch show that this can be fixed using a seed. However, this is only a quick and dirty fix, so I'm not in favour of having it applied. The proper way to fix this is to make objects of the RNGs
@toeklk toeklk added the bug label Dec 9, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant