Fix DPO with Reference Model#387
Closed
austin362667 wants to merge 4 commits into
Closed
Conversation
Signed-off-by: Austin Liu <austin362667@gmail.com>
Signed-off-by: Austin Liu <austin362667@gmail.com>
austin362667
force-pushed
the
fix/alignment/dpo
branch
from
November 22, 2024 02:31
56721f2 to
4ddce2b
Compare
Contributor
Author
|
This is wrong!! The correct implementation is in #405. What I did wrong: # This is incorrect:
ref_chosen_logps = torch.randn(B // 2, device="cuda", dtype=dtype)
ref_rejected_logps = torch.randn(B // 2, device="cuda", dtype=dtype)Why I'm wrong: In DPO, the reference log probabilities MUST come from evaluating the reference model on the same inputs.
How to fix: Thanks to @shivam15s The correct implementation is already in PR #405. I'll close this PR to align with that approach. |
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
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.
Summary
Thanks to @ByronHsu, he identified that the implementation in #378 lacked a reference model for DPO, effectively making it a CPO (Contrastive Preference Optimization) instead. To address this issue, I have:
ref_chosen_logpsandref_rejected_logpsThese changes ensure that DPO tests and benchmarks now function correctly.
DPO Loss Formulation
As mentioned in the previous PR #378,
In a reference setting, we get the formula:
For the loss:
This corresponds to the code:
Testing Done
Updated benchmarks:
make testto ensure correctnessmake checkstyleto ensure code stylemake test-convergenceto ensure convergence