-
Notifications
You must be signed in to change notification settings - Fork 3k
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
[BUG][CUDAProvider] No attribute with name:'activation'is defined #23119
Comments
This is an invalid model. It has a node using FusedConv, but the node does not have activation attribute. |
@tianleiwu Thanks for your explanation. I’m still a bit confused. If the FusedConv operator requires an activation attribute, why does the provided model pass validation ( |
FusedConv is not operator in onnx domain. It is in com.microsoft domain. CPU has different implementation for activation. When activation is not defined, it falls back to Identity. onnxruntime/onnxruntime/contrib_ops/cpu/fused_activation.cc Lines 10 to 34 in 0981bbf
So the model can be handled by CPU provider. |
@tianleiwu Thanks for the clarification. Is it possible to modify the CPU provider implementation to align it with the CPU behavior? Specifically, we could convert the default value of activation to Identity. This would ensure that both CPU and GPU exhibit the same behavior. @tianleiwu Do you think these changes would be a valid solution? Thanks again! |
Yes, it is possible to change CUDA code to align with CPU behavior on this, and also update the spec to mark the attribute to optional. |
Describe the issue
Bug Report
Loading and optimizing the model with CUDA crashed! In comparison, it can run well when executing optimization on the CPU.
The crash stack trace:
To reproduce
Notice:
Urgency
No response
Platform
Linux
OS Version
Ubuntu 12.04
ONNX Runtime Installation
Built from Source
ONNX Runtime Version or Commit ID
5c1b7cc
ONNX Runtime API
Python
Architecture
X64
Execution Provider
CUDA
Execution Provider Library Version
No response
The text was updated successfully, but these errors were encountered: