Inputs generation improvements #1982
Merged
Conversation
This file contains 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
spolu
requested review from
fontanierh and
philipperolet
and removed request for
fontanierh
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixes 1874
GPT_3_5_TURBO_DEFAULT_MODEL_CONFIGtoGPT_3_5_TURBO_16K_MODEL_CONFIGGPT_4_DEFAULT_MODEL_CONFIGtoGPT_4_32K_MODEL_CONFIGBecause it was hella confusing
Otherwise switch to gpt-4-32k with fallback to gpt-4 based on context requirements for inputs generation.|
Testing with the dust-apps, gpt-4 is much better at taking into account the entire conversation,