Op object triggers graph_eval instead of eval to begin op insertion for the graph (Need to figure out how to keep both functionality if they need to stay on the same API.)
TorchscriptEvaluator serves as a manager of input/output graph. In this demo, both of them are torchscript, so this class seems simple (should be more complicated depending on ONNX graph builder API and format requirements).
tensor.py is not modified because onnxscript does not really use the graph value. That is, it will only have to be compatible with graph builder type only in the future implementation.
GitHub2Janky
commented
3 months ago
An evaluator using onnxscript API to build graph using torchscript (we will have our own graph to replace torchscript.)
works with https://github.com/pytorch/pytorch/pull/92717
Fixes #273
Co-authored-by: Ti-Tai Wang titaiwang@microsoft.com
Originally posted by @justinchuby in https://github.com/microsoft/onnxscript/pull/336
Originally posted by @GitHub2Janky in https://github.com/GitHub2Janky/ToJanky13/issues/1