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

How do I trace back to offending network-layer in my python code when an error occurs during CoreML-conversion #2152

Open
sreeneel opened this issue Feb 23, 2024 · 0 comments
Labels
question Response providing clarification needed. Will not be assigned to a release. (type)

Comments

@sreeneel
Copy link

❓Question

When I encounter an error during convert_nodes, is there a way to trace back to what part of my network layers caused this.
Currently I can inspect what node, and its op-name & operands and try to guess what part of my network could have originated it.
But as you can imagine there could be many source-points that could have triggered this.
Is there any way we can pin-point this more easily? Any additional debugging I should enable(if so, how do I go about doing this?)

TIA

@sreeneel sreeneel added the question Response providing clarification needed. Will not be assigned to a release. (type) label Feb 23, 2024
@sreeneel sreeneel changed the title How do I trace back to offending python code when an error occurs during CoreML-conversion How do I trace back to offending network-layer in my python code when an error occurs during CoreML-conversion Feb 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Response providing clarification needed. Will not be assigned to a release. (type)
Projects
None yet
Development

No branches or pull requests

1 participant