-
Notifications
You must be signed in to change notification settings - Fork 294
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
Support qwen for pytorch engine #1265
Conversation
220e835
to
aecbe06
Compare
@jjjjohnson hi, thanks for the reminder. Will update later. |
@RunningLeon Look like there is en error in Qwen pytorch backend...
![]() |
@jjjjohnson Hi, thanks for your feedback. I'll try to reproduce the issue. Coming back to you soon. |
@jjjjohnson hi, lmdeploy had supported qwen with old version. It seems you are running new version of Qwen and some rewriting fails in this case. Could try PR #1351? thanks for your understanding. |
Cool! THX! |
Motivation
Support Qwen for pytorch engine
opencompass results:
![1710216709011](https://private-user-images.githubusercontent.com/28671653/311938049-2eb3baa4-5b39-4abb-afec-c7fd44d0b70c.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjA3MTY4MDUsIm5iZiI6MTcyMDcxNjUwNSwicGF0aCI6Ii8yODY3MTY1My8zMTE5MzgwNDktMmViM2JhYTQtNWIzOS00YWJiLWFmZWMtYzdmZDQ0ZDBiNzBjLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA3MTElMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwNzExVDE2NDgyNVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWQxMGUxYjZlYTdiMWU2ZDViNTFlZmQ3M2YxNDBiMWQ2NWVkZGZjOTFlOWUxYWE0YTQyNmVhZjI4MWZmOTg3YTUmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.8t5rcC0Yay6W2Uud0Yo_0C__0JPRt3nhb571pqI0W_4)
Modification
Please briefly describe what modification is made in this PR.
BC-breaking (Optional)
Does the modification introduce changes that break the backward-compatibility of the downstream repositories?
If so, please describe how it breaks the compatibility and how the downstream projects should modify their code to keep compatibility with this PR.
Use cases (Optional)
If this PR introduces a new feature, it is better to list some use cases here, and update the documentation.
Checklist