Constrained generation with json schema for ExllamaV3 #397
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
beep39
force-pushed
the
json-schema-for-exllamav3
branch
from
cef7560 to
1f197cc
Compare
beep39
force-pushed
the
json-schema-for-exllamav3
branch
from
1f197cc to
d53ca13
Compare
Signed-off-by: kingbri <8082010+kingbri1@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Is your pull request related to a problem? Please describe.
Constrained generation with JSON schema is not supported for exllamav3 models.
Why should this feature be added?
Generation with JSON schema should also work for exllamav3 models.
Additional context
Added grammar.py with add_json_schema_filter similar to exllamav2 implementation