Azure-docs: Export failure

Created on 10 May 2020  Â·  11Comments  Â·  Source: MicrosoftDocs/azure-docs

Hello, I have a Object Detection trained model (general (compact)) and I want to export it to coreML and Tensorflow Lite but the export fails with only a "Failed" message. Where can I find more logs or some diagnostic data? Where can I report this?


Detalji dokumenta

⚠ Ne uređujte ovu sekciju. Ona je neophodna za povezivanje problema slijedom docs.microsoft.com ➟ GitHub.

Pri2 cognitive-servicesvc custom-visiosubsvc cxp product-question triaged

All 11 comments

Thanks for the question! We will review and get back to you shortly.

I'm experiencing the same issue

Hello, now I'm able to export, so I guess something changed. But with an object detection model with two labels I get an output shape with these dimensions [1, 13, 13, 35]. Is there any documentation about the output shape obtained using custom vision and how to decipher it? Or the export is just bugged and I need to wait for a fix? When I look into the object returned by the prediction it doesn't make mush sense.

@nexxuno thanks for your feedback. I am following up internally to gather information. Will followup once I have more details. Thanks.

Hello, you can look into a sample python script in the exported zip package, which describes how to parse the [1, 13, 13, 35] output vector. Another option is to use "General (compact) [S1]" domain, which has better output format. The detail of the format is in its exported zip file.

Ok, I'm using Xamarin, I've tried the compact S1 but as far as I understand it needs a Flex delegate for the tensorflow.lite interpreter to be parsed. Unfortunately it's not available in the Microsoft tensorflow library for Xamarin as far as I know, I've opened a new request here:

https://github.com/xamarin/XamarinComponents/issues/867

I'll try and see if I can port the python post processing included with the non-S1 model export to C#, then again all this trial and error could be avoided with some better documentation (but maybe it's just me).

Thanks for the inputs!

Thanks! We were not aware of the issue with Xamarin. I'll see if we can replace the Flex op with a new standard op which was introduced in TFLite 2.1.

Thank you very much, please let me know as soon as I can test this with a new export.

Thanks for your input @shonohs. Will now proceed to close this thread.

@shonohs since this issue has been closed is there any other issue opened on some other repo where I can follow the progress?

Was this page helpful?
0 / 5 - 0 ratings

Related issues

spottedmahn picture spottedmahn  Â·  3Comments

Agazoth picture Agazoth  Â·  3Comments

bdcoder2 picture bdcoder2  Â·  3Comments

Favna picture Favna  Â·  3Comments

Ponant picture Ponant  Â·  3Comments