openvinotoolkit / openvinotoolkit/nncf
[TorchFX] Stop using PT commands and migrate to FX commands
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Python
- Stars
- 1.2k
- Forks
- 305
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 27
Description
🚀 Feature request
The task is to migrate torchFX backend to FX commands to separate PT and FX backends
https://github.com/openvinotoolkit/nncf/pull/2882#discussion_r1734697947
Feature Use Case
No response
Are you going to submit a PR?
- Yes I'd like to help by submitting a PR!
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 by locating the torchFX backend and its current PT command usage, then read the linked pull request discussion for the intended separation between PT and FX backends. Done means the torchFX backend uses FX commands rather than PT commands and the two backend command paths are separated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, pytorch
- Domain
- machine-learning
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100