-
Notifications
You must be signed in to change notification settings - Fork 342
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
Changing seed number - be careful #1005
Comments
You're right. Not that it is an issue but you've got a point. Adding a PR to improve this logic, using this approach:
|
I think this implementation will cause even worse problems. As seed needs to be an integer using runif will cause all seeds to be the same exact number in many cases. |
Hi @AdimDrewnik Seeds can be any number, no need for integer values. |
I have just checked. Using seed e.g. 1.1 and 1.11 gives exactly same random numbers. |
I think that's not right. Please, check:
|
I am talking about this case
|
Alright, but that's not the implementation I've proposed in the code. |
But you are generating seeds that will be used for random number generation. If you generate non integer seeds that are same integer when rounded your RNG for two trials will be the same. |
I've increased the order of magnitude to have large numeric values. Does this look good to you? Feel free to test and confirm before we merge to main branch. |
Please revert this change and only add a warning to the documentation. It will only cause more problems and more issues. Before I only needed to increase the seed number above the number of trials. Now I am getting a chance to run same RNG multiple times. |
When running Robyn with different seeds be careful when changing the seed value. For example if you run seed = 123 with 10 trials and later run seed 124 with 10 trials then 9 out of 10 trials will have the same seed in the both runs. Seed number must be changed by more than the number of trials if someone wants completely new RNG in the whole run.
The text was updated successfully, but these errors were encountered: