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

Migrate to use official iOS wrapper from PyTorch team #149

Open
cereallarceny opened this issue Jul 7, 2020 · 0 comments
Open

Migrate to use official iOS wrapper from PyTorch team #149

cereallarceny opened this issue Jul 7, 2020 · 0 comments
Assignees
Labels
Priority: 3 - Medium 😒 Should be fixed soon, but there may be other pressing matters that come first Severity: 1 - Critical 🔥 Causes a failure of the complete software system, subsystem or a program within the system Status: Available 👋 Available for assignment, who wants it? Type: Improvement 📈 Performance improvement not introducing a new feature or requiring a major refactor
Milestone

Comments

@cereallarceny
Copy link
Member

Description

We would like to migrate to the official iOS wrapper from the PyTorch team. This was never merged into PyTorch itself, so for now we will need to copy the files. This will replace the following classes related to plan execution, diff generation, and model reporting: TorchTensor, TorchIValue, and TorchModule.

Are you interested in working on this improvement yourself?

Additional Context

pytorch/pytorch#25541

@cereallarceny cereallarceny added Priority: 3 - Medium 😒 Should be fixed soon, but there may be other pressing matters that come first Severity: 1 - Critical 🔥 Causes a failure of the complete software system, subsystem or a program within the system Status: Available 👋 Available for assignment, who wants it? Type: Improvement 📈 Performance improvement not introducing a new feature or requiring a major refactor labels Jul 7, 2020
@cereallarceny cereallarceny added this to the 0.2.0 milestone Jul 7, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority: 3 - Medium 😒 Should be fixed soon, but there may be other pressing matters that come first Severity: 1 - Critical 🔥 Causes a failure of the complete software system, subsystem or a program within the system Status: Available 👋 Available for assignment, who wants it? Type: Improvement 📈 Performance improvement not introducing a new feature or requiring a major refactor
Projects
None yet
Development

No branches or pull requests

2 participants