Skip to content
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

Add Storm-7B to AlpacaEval #294

Merged
merged 2 commits into from
May 3, 2024
Merged

Add Storm-7B to AlpacaEval #294

merged 2 commits into from
May 3, 2024

Conversation

yifan123
Copy link
Contributor

@yifan123
Copy link
Contributor Author

yifan123 commented May 2, 2024

We also added Storm-7B (num_beams=10).

@@ -0,0 +1,14 @@
Storm-7B-num-beams-10:
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this is the right name, but it seems that you generated the outputs with a different name?

Both the leaderboard and the outputs were generated with a config named "Storm-7B (num_beams=10)" please change those manually or regenerate with the current config.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I apologize for the typos. In the num_beams experiment, we use beam search, which slows down the generation process. To address this, we use our own repository that supports multi-GPU generation and then copy the results into this repository.

We have updated the commit for Storm-7B (num_beams=10).

Thanks for your review.

@@ -0,0 +1 @@
GPT4 Correct User: {instruction}<|end_of_turn|>GPT4 Correct Assistant:
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why do you have GPT4 in the prompt?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for your detailed review. Our model is finetuned from openchat-3.5-0106 which uses the chat template: GPT4 Correct User: {instruction}<|end_of_turn|>GPT4 Correct Assistant:. For example, if the question is How are you today?, we input GPT4 Correct User: How are you today?<|end_of_turn|>GPT4 Correct Assistant: into our model. It's just a template, similar to other chat templates. You can see the same chat template in another model in this repo.

@YannDubs YannDubs merged commit b04b1b8 into tatsu-lab:main May 3, 2024
2 checks passed
@YannDubs
Copy link
Collaborator

YannDubs commented May 3, 2024

Very impressive results @yifan123 !

I must say that I'm a shocked that a 7B gets that performance. What data was it trained on? What's the magic sauce to get such performance?

@yifan123
Copy link
Contributor Author

yifan123 commented May 3, 2024

We follow the same setup as in Starling-7B, using the same base model (openchat-3.5-0106) and fine-tuning on the same offline preference dataset (Nectar), without adding any additional datasets.

Our LM only differs in the optimization algorithms: apply DPO iteratively on newly generated responses ranked by the reward model (Starling-RM-34B). Note that Starling-RM-34B is also trained on Nectar by the K-wise maximum likelihood estimator, which means no extra data is used.

Our improvement stems mainly from the iterative training. The figure below shows that using only the first iteration's dataset in the second iteration results in minimal improvement.

We need to highlight the limitations of our study:

Storm-7B is a quick demonstration that a language model, fine-tuned with AI feedback, can easily surpass or match state-of-the-art models, as assessed by the same AI feedback. However, this improvement on the automatic leaderboard may not necessarily indicate better alignment with human intentions. Our model therefore represents a critical, preliminary reevaluation of the RLAIF paradigm, questioning how much learning from and being evaluated by AI feedback aligns with actual human preferences.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants