We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
AoT Executor and Graph Executor should treat the names in the same way.
AoT Executor replaces non-alphanumeric characters in the input name while Graph Executor does not. Setting the input data using the original name e.g.
aot_executor.set_input(‘predict_images:0’, input_data)
results in error ‘cannot find ‘predict_images:0’ among input’ while
graph_executor.set_input(‘predict_images:0’, input_data)
is fine. The different behavior is not intuitive.
See https://discuss.tvm.apache.org/t/aot-problem-in-microtvm-utvm-host-driven-application/13100
TVM version: v0.15.dev0
Use a network with an input tensor name containing a non-alphanumeric character, e.g. 'serving_default_input_2:0' in conv1d_batchnorm_pruned.zip
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Expected behavior
AoT Executor and Graph Executor should treat the names in the same way.
Actual behavior
AoT Executor replaces non-alphanumeric characters in the input name while Graph Executor does not.
Setting the input data using the original name e.g.
aot_executor.set_input(‘predict_images:0’, input_data)
results in error ‘cannot find ‘predict_images:0’ among input’ while
graph_executor.set_input(‘predict_images:0’, input_data)
is fine. The different behavior is not intuitive.
See https://discuss.tvm.apache.org/t/aot-problem-in-microtvm-utvm-host-driven-application/13100
Environment
TVM version: v0.15.dev0
Steps to reproduce
Use a network with an input tensor name containing a non-alphanumeric character, e.g. 'serving_default_input_2:0' in
conv1d_batchnorm_pruned.zip
The text was updated successfully, but these errors were encountered: