feat: start working on revisions instead of preferences #1999
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.
Don't land this PR yet. I would initially like some feedback on the idea of this PR, and if this is a welcome change in TRL.
This PR seeks to adds revisions to TRL. Revisions create preference pairs by minimally revising a completion, unlike Judges who rank a set of completions.
To do this, I've added a
tmp/trainer/revisions.py
file with all the revision logic.see CLAIR paper: https://www.arxiv.org/abs/2408.06266
TODO: