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

Output of main and server is totally different #6734

Closed
njalan opened this issue Apr 18, 2024 · 4 comments
Closed

Output of main and server is totally different #6734

njalan opened this issue Apr 18, 2024 · 4 comments

Comments

@njalan
Copy link

njalan commented Apr 18, 2024

When I start the service by main and server command and ask the same question like '上海有什么好玩的', the output is different. so how to keep the output response of API is the same as the output of main command.

@schmorp
Copy link

schmorp commented Apr 18, 2024

Does it also change when you repeat it? LLMs are not deterministic, so there is no expectation that the same question yields the same answer. If that is the issue, try specifying a seed value with --seed.

@Jeximo
Copy link
Contributor

Jeximo commented Apr 18, 2024

how to keep the output response of API is the same as the output of main command.

It's unclear what settings you used. Readme shows seed, and temperature API.

Related: #6569 (comment)

@longcw
Copy link

longcw commented Apr 18, 2024

I have the same issue. I have the temp 0 and fixed seed, but the results of main and server are consistently different every time. If the cache_prompt enabled, the second run from the server with cache will have the same result to the main, even the first run is different. This is a problem bc I found that results from main usually have a better quality.

@github-actions github-actions bot added the stale label May 19, 2024
Copy link
Contributor

github-actions bot commented Jun 2, 2024

This issue was closed because it has been inactive for 14 days since being marked as stale.

@github-actions github-actions bot closed this as completed Jun 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants