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

[Model] support cogvlm2 model #261

Merged
merged 1 commit into from
Sep 17, 2024
Merged

Conversation

white2018
Copy link
Contributor

Before you open a pull-request, please check if a similar issue already exists or has been closed before.

When you open a pull-request, please be sure to include the following

  • A descriptive title: [xxx] XXXX
  • A detailed description

Thank you for your contributions!

This PR intends to enhance the functionality of lmms-eval by supporting CogVLM2 model, which is not covered in latest version.

The code is evaluated with mmstar dataset. Here is the screeshot as follows:
image

Copy link
Collaborator

Choose a reason for hiding this comment

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

Hi @white2018 , is this a duplicate commit? Remember that you have add this model in the previous PR

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Sorry! It is a wrong commit. Forget about it.

Copy link
Collaborator

@kcz358 kcz358 left a comment

Choose a reason for hiding this comment

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

The cogvlm model looks good. Just wondering is the minimonkey model being added for another time?

@white2018
Copy link
Contributor Author

The cogvlm model looks good. Just wondering is the minimonkey model being added for another time?

@kcz358 This commit about minimonkey model is just a mistake. Sorry about that.

@kcz358
Copy link
Collaborator

kcz358 commented Sep 17, 2024

Hi @white2018 , you mind if I try rebase and drop the duplicated commits on you branch?

@white2018
Copy link
Contributor Author

Hi @white2018 , you mind if I try rebase and drop the duplicated commits on you branch?

OK, I try it.

@kcz358
Copy link
Collaborator

kcz358 commented Sep 17, 2024

Thank you! @white2018 , I can also help you do it if you don't have time to do so. Since I can edit on this PR branch, I can directly push to this branch that stick to this PR in your forked repo.

@white2018
Copy link
Contributor Author

white2018 commented Sep 17, 2024

Thank you! @white2018 , I can also help you do it if you don't have time to do so. Since I can edit on this PR branch, I can directly push to this branch that stick to this PR in your forked repo.

@kcz358 That will be appreciated. Thanks a lot!

@kcz358
Copy link
Collaborator

kcz358 commented Sep 17, 2024

Hi @white2018 , I have drop the duplicate commits and rebase to main. Can you help me do a final code check to see if I did not accidentally dropped any code changes? If the current change is good, I will merge this PR. Thank you for your contribution!

@white2018
Copy link
Contributor Author

Hi @white2018 , I have drop the duplicate commits and rebase to main. Can you help me do a final code check to see if I did not accidentally dropped any code changes? If the current change is good, I will merge this PR. Thank you for your contribution!

@kcz358 Everything is OK

@kcz358 kcz358 merged commit 236667d into EvolvingLMMs-Lab:main Sep 17, 2024
1 check passed
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