Hi @namduc, deploying with the VM after autoscheduling shoudl be fine and it's
not clear why autoscheduler thinks your logs dont apply to your model. Would it
be possible for you to post your tuning script as well?
---
[Visit
Topic](https://discuss.tvm.apache.org/t/how-to-apply-best-histo
Yes `TVMCPackage` (between the `compile` and `run` steps) sounds like what you
want. It's the deployable artifact. `TVMCModel` is the high level graph
definition. If you wanted to tune a model for a few different hardware targets
you could use the one `TVMCModel` to produce several `TVMCPackag
Hi @Airbala, although this message looks scary, all it means is that you
haven't performed the autotuning process. TVM will still work fine, it just
might not be as fast as it could be. If you want to learn more about
autotuning, check out one of the tutorials here:
https://tvm.apache.org/doc
The fix is now merged, if you update to master your model should work.
---
[Visit
Topic](https://discuss.tvm.apache.org/t/prelu-op-can-not-support-broadcast/7880/4)
to respond.
You are receiving this because you enabled mailing list mode.
To unsubscribe from these emails, [click
here](h
Sorry for the delay in response. @blacklong617, you're right that we should
support broadcasting alpha but currently dont. This PR:
https://github.com/apache/incubator-tvm/pull/6549 fixes the issue.
---
[Visit
Topic](https://discuss.tvm.apache.org/t/prelu-op-can-not-support-broadcast/7880