Skip to content
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

ONNX updates #527

Merged
merged 51 commits into from
Apr 29, 2024
Merged

ONNX updates #527

merged 51 commits into from
Apr 29, 2024

Conversation

pgleeson
Copy link
Member

No description provided.

Sandeep Pillai and others added 30 commits March 8, 2024 17:34
For some reason, for some ops, the opset version is set to the miniumum supported version. For certain ops, this is version 1. The ONNX runtime is printing a warning about any version less than 7. So, if the opset version is less than 7, opset_version.
To ensure keras_model.py is run before the keras_to_MDF.py
which uses the model, I excluded them from examples and
instead import them from keras_to_MDF.py.
Ok, I think that keras_model.py is not running twice in some
cases because the module with the same name is getting cached.
I have re-included it and it seems that it should always run
first anyway.
Actually, I don't like depending on test execution order. If
we ever parallelize tests this will be bad. Lets try
using exec. I think this will ensure the keras_model.py that
is local to the script runs each and every time.
Since we are executing the keras_model.py in the callspace we
don't even need to serialize\deserialize model.
Fix minimum opset version used for ONNX op execution, Tensorflow Import Fixes
Added import os in examples/MDF/simple.py
Updates to actions; regenerated some images
@pgleeson pgleeson merged commit 5fb8305 into main Apr 29, 2024
20 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants