-
Notifications
You must be signed in to change notification settings - Fork 467
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
Feat/Split ONNX Import #2568
base: main
Are you sure you want to change the base?
Feat/Split ONNX Import #2568
Conversation
…or split is provided
@antimora For nodes that produce multiple outputs, is there a recommended pattern for how to assign and return these outputs in the forward method? I tried to do the reverse of Also, in the generated ONNX graph, all three outputs of the graph are named "split1_out1", but the outputs of the node are named uniquely. How do we ensure that each output of a multi-output node is named uniquely (assuming they should be)? I keep getting this error when I try generating the IR:
I have a feeling that the non-unique names might be tripping this up, because the overall structure of the outputs is consistent with other IRs I've generated. I also copied some of the generated graph to show you what I mean.
|
Pull Request Template
Checklist
run-checks all
script has been executed.Related Issues/PRs
#2440
Changes
Adds split to the list of supported ops that can be imported via ONNX.
Testing
tbd