Skip to content

Conversation

@ageorgou
Copy link
Contributor

An example of how to set the seed. This should result in the same values being generated every time. This also means that all the runs will have the same id and be identical, so it only makes sense for single runs.

@jennifersmith203
Copy link
Collaborator

Thanks Anastasis, this will be REALLY useful. I tried copying the changes into my branch but it's not working at the moment - is that because we haven't merged PR #193 ("Replace random functions") yet? Thanks.

@andrew-phillips-1
Copy link
Collaborator

Hi Jenny

Yes I was thinking the same - I intend to try it with the new PR merged. Please let me know if you find it works

@ageorgou
Copy link
Contributor Author

Yes, I should have made that clear. This is on top of the changes in #193 (switching to rand('uniform') etc).

It would be good to eventually also merge these changes (setting the seed), but they shouldn't be enabled all the time (or all the runs would be identical). Perhaps we can find a way that they can be toggled on and off.

@jennifersmith203
Copy link
Collaborator

Thanks, yes that makes sense. It would be handy to have them all turned off as default but with a quick way to turn them all on when needed.

@andrew-phillips-1
Copy link
Collaborator

Yes agree - thanks.

There is an additional data step for r&da2, where the seed was
not set before. The place where it was set did not involve any
randomness.
Also use the more appropriate macro variable, as e was not strictly
increasing.
@ageorgou ageorgou changed the base branch from replace-random to core September 21, 2021 08:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants