-
Notifications
You must be signed in to change notification settings - Fork 22.6k
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
test_view_dynamic_zero_dim no longer testing zero input #105066
Comments
iiuc the unittest's intention could be to op test scenarios from rcnn models where it may return zero boxes depending on input image. Based on recommendation, I suppose we should add a larger snippet that doesn't start for size 0 input but captures how one is emitted in the middle/output. @ezyang Do you happen to know if such behavior from vision models is dynamically supported by symbolic tracing? |
Zero size input is legitimate, we sort of support this: if you ask whether or not something is equal to zero, we will always say False, but the hypothesis is the traced graph will work anyway for the zero case. |
…ro_dim" From #105066. The case was meant to test 0 bbox generated by vision models, but the bboxes still have `.view()` operated. The case was disabled, and not supported. Added a comment to clear the potential confusion in the future. We will wait for model example to proceed on this. [ghstack-poisoned]
From #105066. The case was meant to test 0 bbox generated by vision models, but the bboxes still have `.view()` operated. The case was disabled, and not supported. Added a comment to clear the potential confusion in the future. We will wait for model example to proceed on this. [ghstack-poisoned]
From #105066. The case was meant to test 0 bbox generated by vision models, but the bboxes still have `.view()` operated. The case was disabled, and not supported. Added a comment to clear the potential confusion in the future. We will wait for model example to proceed on this. Pull Request resolved: #105950 Approved by: https://github.com/BowenBao, https://github.com/thiagocrepaldi
…ro_dim" From #105066. The case was meant to test 0 bbox generated by vision models, but the bboxes still have `.view()` operated. The case was disabled, and not supported. Added a comment to clear the potential confusion in the future. We will wait for model example to proceed on this. [ghstack-poisoned]
From #105066. The case was meant to test 0 bbox generated by vision models, but the bboxes still have `.view()` operated. The case was disabled, and not supported. Added a comment to clear the potential confusion in the future. We will wait for model example to proceed on this. [ghstack-poisoned]
Re-enable in #127349 |
🐛 Describe the bug
#104828 (comment)
Filing an issue as requested by @thiagocrepaldi @titaiwangms
I don't think the exported model should work with a zero size input. The reason is that we 0/1 specialize on tracing; when you trace a model that has size 2, we assume that if you dynamically vary the shape, you won't vary it to 0 or 1. It is strange to have a model that exports and works with either size 0, or size 2.
If there is a more realistic example, we should put it in here instead.
Versions
main
The text was updated successfully, but these errors were encountered: