-
Notifications
You must be signed in to change notification settings - Fork 2.2k
Conversational dataset support for KTOTrainer
#2248
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
Conversation
The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great refactor @qgallouedec ! LGTM with a tiny nit
@@ -95,24 +93,6 @@ | |||
# Load the dataset | |||
dataset = load_dataset(script_args.dataset_name) | |||
|
|||
# If needed, reformat a DPO-formatted dataset (prompt, chosen, rejected) to a KTO-format (prompt, completion, label) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice refactor!
Co-authored-by: lewtun <lewis.c.tunstall@gmail.com>
* `get_batch_sample` -> `generate_from_model[_and_ref]` * add `num_items_in_batch=None` * `num_items_in_batch` in `training_step` * Fix return type hint * desc for unpair dataset util * update example * process in KTO * Update doc * KTO doc rewrite * fix orpo doc * add other dataset config names in test * update doc image * fix links in doc * Update reward and log probability metrics in KTOTrainer doc * skip enc-dec test * Update docs/source/kto_trainer.mdx Co-authored-by: lewtun <lewis.c.tunstall@gmail.com> --------- Co-authored-by: lewtun <lewis.c.tunstall@gmail.com>
What does this PR do?
Part of #2071
Fixes #2238
This PR also adds support for paired preference dataset for KTO.
Before submitting
Pull Request section?
to it if that's the case.
documentation guidelines.
Who can review?
Anyone in the community is free to review the PR once the tests have passed. Feel free to tag
members/contributors who may be interested in your PR.