-
Notifications
You must be signed in to change notification settings - Fork 359
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
ConstraintViolationError #6782
Comments
Hi, @adonnini. Can you provide the dynamic shape constraints that you pass into export, as well as information about the model that you are exporting? Thanks! |
@GregoryComer thanks for the follow-up You can find the entire model with instructions on how to run it here https://github.com/adonnini/adonnini-trajectory-prediction-transformers-masterContextQ/tree/main Here is the line where I pass the model and the inputs
where Thanks |
According to this error message, it seems like one of your input tensor is having an unexpected size. Can you please print out the tensor shapes for It's a bit hard to tell from reading your code https://github.com/adonnini/adonnini-trajectory-prediction-transformers-masterContextQ/tree/main |
@larryliu0820 , Thanks for getting back to me The printout of the four variables themselves is very big. I thought that the information about the shapes is what your really wanted given your question. Below, you will find the output of the four print statements of the shapes of the four variables. Please note that the model runs successfully when excluding the executorch related code. Even with the executorch code, the frist epoch completes successfully. By the way, the fact that the shapes of dim 1 of enc_input and dec_input is different is not an issue for the model. As I said, the train_minimum.py runs successfully without the executorch code. You can try it yourself. Thanks
|
@angelayi do you have any suggestions? Is it worth an issue in pytorch/pytorch? |
By specifying To fix this you can make each of the dims different, or you can try a new thing, |
@angelayi Thanks for your suggestion. After making the change you suggested (I should have seen the error, Thanks), execution failes producing the error log reported below. @larryliu0820 I think the ball may be back in the executorch court. FYI, below you will also find the executorch related code (in train-minimum.py) ERROR LOG
CODE
|
Can you use the new torch.export.export API?
and the rest should be the same |
@larryliu0820 , I made the change you suggested. Execution failed with the same error. Please find below the error log and the code change I made. Did I make a mistake in making the change? ERROR LOG
CODE
|
What I meant is you can skip this line:
And do |
@larryliu0820 Sorry. I re-ran the code with the corrected code. There was progress (I think). Execution failed. ERROR LOG
CODE
|
@metascroy This goes into At the same time @adonnini we can also skip this pass - change your code to:
|
@larryliu0820 I made the change. Please find below update code and (big) error log. CODE
ERROR LOG(see attached file) |
@adonnini :) this is not helpful for debugging because it seems like it's just a graph dump. Someone from our side need to repro this locally and debug. I don't have the time right now but if you want to wait I may get back next week. |
@larryliu0820 Thanks for your help. I really appreciate it. I understand about your priorities. Would you mind if I check in with you in 1-2 weeks? |
@adonnini yeah ping me next week I'll spend some time repro your issue |
Hi,
I just upgraded to executorch 0.4 and ran my code which previously failed as described in
#1350
Now it fails with
ConstraintViolationError
Please find the error log below.
Please let me know if you need additional information.
Thanks
ERROR LOG
The text was updated successfully, but these errors were encountered: