Change theme
Help
Press space for more information.
Show links for this issue (Shortcut: i, l)
Copy issue ID
Previous Issue (Shortcut: k)
Next Issue (Shortcut: j)
Sign in to use full features.
Vote: I am impacted
Notification menu
Refresh (Shortcut: Shift+r)
Go home (Shortcut: u)
Pending code changes (auto-populated)
View issue level access limits(Press Alt + Right arrow for more information)
Request for new functionality
View staffing
Description
This will create a feature request which anybody can view and comment on. Please describe your requested enhancement. Good feature requests will solve common problems or enable new use cases.
What you would like to accomplish:
The input type of the model should be ImageType instead of MLMultiArrayType. The CoreML documentation speaks to the performance benefits here [1]. In addition to improved performance, usage of ImageType allows iOS/macOS developers to use Apple's Vision API which makes it much easier to run the inferences on CoreML models.
The model should be configured as an image classifier, and the labels should be embedded in the classifier configuration. This allows developers to more easily use the inference results, as the classification scores will be directly associated with their respective labels without need of lookup in an accompanying dictionary file.
How this might work:
If applicable, reasons why alternative solutions are not sufficient:
Unfortunately, there is no option to export in Keras format so this is not possible on customer's end. It's also difficult to modify the existing MLModel [2]. Because of this, customer request that the AutoML Vision product team can change the internal conversion process to include these optimizations, or alternatively provide a TF2 SavedModel export option (the SavedModel export option currently available seems to be based on TF1, and is very difficult to use to convert to MLModel) so that customer can convert it themselves.
[2]https://github.com/apple/coremltools/issues/1143#issuecomment-805301470
Other information (workarounds you have tried, documentation consulted, etc):