-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Recipe for fine-tuning with lower resolution images #714
Comments
@avaradarajanfigma Thanks for your question. I believe the processor will automatically do the resize process as shown here. You do not need to modify any code to get our vision model working with lower resolution images. Of course you can run fine-tuning on you own lower resolution images using finetune_vision_model.md, if you want. Let me know if you have any questions. |
My question is, is there a way to initialize the model/processor in such a way that it doesn't scale up the lower resolution images first(resulting in fewer visual tokens), so that it is possible to fine tune with less memory? |
I do not think it is possible to feed lower resolution image into our vision model. (1) Processor will always resize as |
Thanks. What GPUs were the recipes/quickstart/finetuning/finetune_vision_model.md recipe tested on? I tried on 4 A10 GPUs and it OOMs. |
What is your command to run the fine-tune? |
I am using the same command as in recipes/quickstart/finetuning/finetune_vision_model.md, except I changed batch size to 1
|
Can I see the error message? I think Lora should work as estimated from this table. I was using the H100 to test the fine-tune but I will investigate more about this problem. |
Below are the OOM errors. Based on the model sizes in that table - they are not referring to the vision models.
|
🚀 The feature, motivation and pitch
Is fine-tuning the Vision models at a lower resolution supported? If so, can you please add a recipe for that(or add a note in recipes/quickstart/finetuning/finetune_vision_model.md for how to do that. I tried setting the size param in processor as
But this results in a tensor size mismatch error
Alternatives
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: