Preference dataset docs #1636
Merged
Preference dataset docs #1636
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
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/torchtune/1636
Note: Links to docs will display an error until the docs builds have been completed. ✅ No FailuresAs of commit 02ca414 with merge base 9a863c8 ( This comment was automatically generated by Dr. CI and updates every 15 minutes. |
facebook-github-bot
added
the
CLA Signed
RdoubleA
approved these changes
Sep 20, 2024
| The ground-truth in preference datasets is usually the outcome of a binary comparison between two completions for the same prompt, | ||
| and where a human annotator has indicated that one completion is more preferable than the other, according to some pre-set criterion. | ||
| These prompt-completion pairs could be instruct style (single-turn, optionally with a single prompt), chat style (multi-turn), or | ||
| some other set of interactions between a user and model (e.g. free-form text completion). |
There was a problem hiding this comment.
is this true, or do we only support preference chat? I guess as long as you make the transform it should work for all three, but your example below implies only chat
There was a problem hiding this comment.
Since we support an optional system prompt it should work for all three right? That was the whole point of the preference dataset refactor to support arbitrary interactions
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.
Context
What is the purpose of this PR? Is it to
Please link to any issues this PR addresses.
#1529
Details on expected preference dataset format, where you can use it, and how to use custom preference datasets.
I haven't covered using different preference message transforms - maybe that can go in the message docs?