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

tests: ensure seed change test uses new seed #2675

Merged
merged 1 commit into from
May 23, 2023

Conversation

kmantel
Copy link
Collaborator

@kmantel kmantel commented May 23, 2023

Since each test uses incrementing fixed seeds from 0, using new_seed = 1 will cause it to share a seed with some other component, depending on the order in which components are created (ex: one Parameter is instantiated before or after another, resulting in different individual seeds for each).

This ensures that new_seed will actually be unused in the test.

Since each test uses incrementing fixed seeds from 0, using new_seed = 1
will cause it to share a seed with some other component, depending on
the order in which components are created (ex: one Parameter is
instantiated before or after another, resulting in different individual
seeds for each).

This ensures that new_seed will actually be unused in the test.
@github-actions
Copy link

This PR causes the following changes to the html docs (ubuntu-latest-3.7-x64):

No differences!

...

See CI logs for the full diff.

@kmantel kmantel merged commit c4c7ae7 into PrincetonUniversity:devel May 23, 2023
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.

1 participant