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
git-base-vatex: input pixel_value dimension mismatch (blocking issue) #26230
Comments
Hey! I would suggest you to try to isolate the bug as we have limited timeframe to debug your custom code. If this is indeed a bug we can help you, otherwise the community forum is a good place to ask this! |
@ArthurZucker: I believe this is a bug because most of the code in
Any help would be greatly appreciated Thanks! |
Hi @shreyaskar123 this is not a bug on our side, it's a bug on the data preparation side. You can fix it by removing the batch dimension which the processor creates by default. |
@NielsRogge: I did try to remove the batch dimension (see #26230 (comment)), but I get a error that pixel_values isn't part of kwargs anymore. Could you please take a look? |
This issue has been automatically marked as stale because it has not had recent activity. If you think this still needs to be addressed please comment on this thread. Please note that issues that do not follow the contributing guidelines are likely to be ignored. |
System Info
transformers
version: 4.30.2Who can help?
@NielsRogge
Information
Tasks
examples
folder (such as GLUE/SQuAD, ...)Reproduction
At this point when I do the print the dimension is 5 (as expected). But when I print the dimension of
pixel_values
in the first line inforward
in filemodeling_git.py"
the dimension is 6. Because of this I get errorraise ValueError("pixel_values must be of rank 4 or 5") ValueError: pixel_values must be of rank 4 or 5
This is the full stack trace for reference:
Expected behavior
Ideally the dimension of
pixel_values
insideforward
would also be 5 and the finetuning of git-base-vatex on video would work This is a blocking issue and any help would be really appreciated!The text was updated successfully, but these errors were encountered: