As a worker of hardware accelerator company, I find almost each company need to 
create a NN model parser tool to do the same work of Relay frontend, and the 
most important part of it is keep a model zoo.

>From my work experiences from two hardware accelerator companies, maintain a 
>IR and support NN framwork(e.g., Tensorflow, caffe, tflit) need lots of time 
>and work, and Relay make a better job than these company internal tools, but 
>we still want Relay have a well maintained model zoo and useful utilities(e.g, 
>tools to extract one single operator's Relay IR and its constants for hardware 
>to do unit test).

If Relay have a well maintained model zoo and these utilities I think lots of 
companies who hasn't NN parser tool will use Relay as their IR, if them think 
Relay is too complex(e.g., they needn't control flow), then I think they only 
need make a tool convert Relay IR to their IR instead of make a whole NN parser 
tool.

Actually this thought is from a real work task, when I import ResNet-50 
Tensorflow model to TVM, quantize it and build it, I found it will report error 
in quantize phase, it is strange to me, because this ResNet-50 model is used 
almost anywhere as a benchmark model, I know Relay must be have supported it, 
but I meet the error, and  after some debugging, I found after Relay Tensorflow 
frontend the Relay IR have lots of useless small functions, then I remember I 
have saw "RemoveUnusedFunctions" pass in discuss forum, so apply it resolve the 
quantize error. Even through it doesn't cause too much time to solve this 
problem, but I think it shouldn't be appeared, so if there is a model zoo, I 
would like to push this to it and  other people will not meet the error.





---
[Visit Topic](https://discuss.tvm.apache.org/t/relay-model-zoo/6348/3) to 
respond.

You are receiving this because you enabled mailing list mode.

To unsubscribe from these emails, [click 
here](https://discuss.tvm.apache.org/email/unsubscribe/f51ee91fecd1e087e5a7f54350d46524499e250f7ba48060ef3f5756a53390f0).

Reply via email to