All GA models export to CoreML via. torch.export with the same performance and user experience as torch.jit.trace
Open
Nobody has claimed this yet.
triaged
- Dominant language
- Python
- Stars
- 5k
- Forks
- 1.2k
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 581
Description
🚀 The feature, motivation and pitch
GA model list: https://docs.google.com/spreadsheets/d/18HbvYhnhPfkHih0oRPGvUloRVyZpTwKtZxaJrfkD_9s/edit?gid=0#gid=0
Alternatives
No response
Additional context
No response
RFC (Optional)
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked GA model list and compare the existing torch.export and torch.jit.trace workflows for those models. Define which CoreML export cases are in scope, then verify equivalent performance and user experience across the listed models.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, pytorch
- Domain
- machine-learning, mobile-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100