-
Notifications
You must be signed in to change notification settings - Fork 58
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
How to include an ONNX model into onnxscript script? #1882
Comments
Cc @gramalingam |
Agree, it would be great to have this feature. Unfortunately, onnxscript doesn't have it yet. Ideally, we should have a wrapper function that allows us to treat an existing ONNX model as a function, and be able to call it from an onnxscript function. Would be great to add this feature. |
Yes!
Works, but misses the fantastic debuggability of onnxscript! Looking forward to this happening :) |
Feel free to reopen if the question is not answered. |
The workaround mentioned earlier works OK, but is REALLY cumbersome, against the ease-of-use of onnxscript. With anything but a trivial model graph it becomes a pain to manage the manual merging of all the models, manually linking the inputs and outputs. So although this is possible, a function wrapper that @gramalingam suggested would be oh-so-much-better. Any chance it could be put on the roadmap? |
Thank you for your feedback! I will take a closer look at this. |
Hi onnnxscript people,
Onnxscript is great, I love it, thanks!
I currently use it e.g. for preprocessing tasks, but would want to include the 'real' model in the flow as well.
More, I would e.g. like to include 3 models as an assembly in an onnxscript.
Until now I didn't find a way (tutorial, documentation) on how to do it. It's perhaps slightly related to #952 which converts the ONNX model to a script, I guess to also be able to 'merge' it with other scripts (and tweak the whole thing).
Therefore, in essence - is it possible to include a 'compiled' (proto) ONNX model as a part of an onnxscript?
Thanks!
The text was updated successfully, but these errors were encountered: