-
Notifications
You must be signed in to change notification settings - Fork 428
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
Fix batch size 1 by specifying squeeze dims #166
base: main
Are you sure you want to change the base?
Conversation
Thanks for your fix, but what does |
...hm. I'll be honest, I don't remember my reasoning behind it; I just know it doesn't break. Looking at the relevant code again, it seems |
So does it mean it's probably just redundant? Does it still work with batch size greater than 1? Also it would be great if you could implement gradient accumulate for the accelerate version of fine-tuning with 1 GPU but someone else could do it too. Sorry I am too busy to test the code nor adding new stuff. |
@Sobsz |
Seems like the testing iterations are failing silently because of the |
@Sobsz |
@Sobsz
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Validation losses have a range mismatch, something likely has to be done here, as we cant't just not have validation loss
turns out that this also breaks higher batch sizes |
.squeeze(0) is going to squeeze the wrong dimension when batch size > 1, need to use .squeeze(dim=1) in most of these places (from manually stepping through with a debugger). |
@brthor can all of them be changed to dim=1 or do some need to remain 0? if so which ones? |
Fixes #104 (as far as I can tell).