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

[bug] Nondeterminism #98

Open
AlekseyKorshuk opened this issue Oct 19, 2024 · 1 comment
Open

[bug] Nondeterminism #98

AlekseyKorshuk opened this issue Oct 19, 2024 · 1 comment

Comments

@AlekseyKorshuk
Copy link
Contributor

I have spotted some lines where the generator is used without the seed. Some of them might not be used, but the rest a critical for result consistency. Here is the list:

@AlekseyKorshuk AlekseyKorshuk changed the title [bug] Nondeterminism in scenarios [bug] Nondeterminism Oct 19, 2024
@jzleibo
Copy link
Collaborator

jzleibo commented Nov 13, 2024

Here's how we're thinking about this. We could make the lines you mention use the seed, and we should and will do that in the long run. However, this won't actually make the result deterministic. The problem is that these are all places that will be called after substantial use of the LLM API has already happened. But the LLM API could be delayed for network traffic reasons, rate limits, etc, any number of things. These would all end up advancing the seed. So just making the lines you mention take a seed parameter would not actually yield a deterministic result in practice.

What we have done to take as big a step as possible toward determinism is to make sure that all the random choices that happen in environment setup, before we use the LLM, are all seeded properly. This part of the variation really can be made deterministic, so we have done that.

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

No branches or pull requests

2 participants