-
Notifications
You must be signed in to change notification settings - Fork 431
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
For structuring JSON, I find the numbers (float/integers) are problematic with a consistent pattern of repetitive zeros #847
Comments
Another issue of repetition:
|
Encountering the same issue frequently with integers in json schemas, even with the sample JSON schema/prompt. Schema and prompt are the same as in the readme.
Note: not only 0s, there is a random 4 somewhere in there too. I am using a llama2 based quantized 7b model, and this will happen maybe 70% of the time |
Also encountering the other repetition ( Ex: |
For the newline issue, changing the For the int/float issue, no good solution yet. Maybe using |
This would allow to mitigate some repetition issues that certain LLMs have. This should resolve #847 Co-authored-by: Samuel Magnan <samuel@glodonusa.com>
…i#932) This would allow to mitigate some repetition issues that certain LLMs have. This should resolve dottxt-ai#847 Co-authored-by: Samuel Magnan <samuel@glodonusa.com>
…i#932) This would allow to mitigate some repetition issues that certain LLMs have. This should resolve dottxt-ai#847 Co-authored-by: Samuel Magnan <samuel@glodonusa.com>
…i#932) This would allow to mitigate some repetition issues that certain LLMs have. This should resolve dottxt-ai#847 Co-authored-by: Samuel Magnan <samuel@glodonusa.com>
Describe the issue as clearly as possible:
When I try to structure a JSON output to float, I will occasionally hit an error which upon inspection is caused by the field outputting a non-ending zeros such as:
Steps/code to reproduce the bug:
Expected result:
Error message:
The text was updated successfully, but these errors were encountered: