Clean up prototype transforms before migration
See original GitHub issueThe transforms in torchvision.transforms
are fully JIT scriptable. To achieve this we needed a lot of helper methods and unnecessary strict or plain wrong annotations.
The revamped transforms in torchvision.prototype.transforms
will no longer be JIT scriptable due to their ability to handle more complex inputs. Thus, we should clean-up our code removing everything that was just added to appease torch.jit.script
. This should only happen as one of the last steps before migration to the main area.
Issue Analytics
- State:
- Created 2 years ago
- Comments:7 (3 by maintainers)
Top Results From Across the Web
Clean up your server instance before migration
Before migrating to cloud, learn how to clean up your Jira or Confluence instance for a smoother migration to cloud.
Read more >Data Migrations and The Importance of Centralizing Your ...
When we are migrating data to Salesforce, the first step in the process is to transform our data so that it exactly matches...
Read more >4 Best Practices for Data Migration Validation - LinkedIn
Analyze: Analyze source system data and identify mapping rules upfront. This step coincides with the Transformation step as you transform, clean ...
Read more >How to migrate a traditional app to SaaS: Yalantis approach
Migrating to a SaaS business model is complex but possible. Go through a full and proven plan of action based on Yalantis' experience....
Read more >Workday Data Migration : How we saved over 2000 ho...
Clean up and align the data between the systems using mapping files and common business rules. Remove duplicates and merge redundant records ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I would go with option 3. IMO the current typing annotations provide sufficient info without introducing complex solutions like 2.
Regardless of #6584, the transforms will not be JIT scriptable. Thus, cleaning them up is still relevant.