-
Notifications
You must be signed in to change notification settings - Fork 285
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 training on only LAION 2B #137
Comments
As implied by the title we should allow users to train on only laion 2B. This should be very straightforward and involves making mmc4 arguments optional in train.py and refactoring the training loop on train_utils.py |
@anas-awadalla is it still open for contribution? |
@nayeem01 Yes! We kept the previous PR out for too long and now it is outdated. Feel free to work on it. |
Noticed the linked PR. Is this open for contribution? @anas-awadalla |
Hi @isaac-chung. We have this implemented in #261. We would still love it if you contributed to a different issue :). |
Take your running command as an example, how can I change the following command to only train on LAION-2B based on a pre-trained OPT-1.3B?
By the way, I would like to ask about the contribution of MMC4 for training. Have you conducted an ablation study on MMC4 + LAION-2B and LAION-2B only? Thank you very much for your time and consideration!
Originally posted by @HenryHZY in #129 (comment)
The text was updated successfully, but these errors were encountered: