tensorflow / tensorflow/model-optimization
QAT training support strided_slice
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.6k
- Forks
- 349
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 1
Description
System information
- TensorFlow version (you are using):2.3.2
- Are you willing to contribute it (Yes/No):
Motivation
What is the use case and how does it broadly benefits users? Prioritization and whether a feature is added is based on how it
helps the community and the feature's maintenance costs.
As examples:
-
Instead of, "Enable the technique for my model," "Enable this technique to work better with standard object detection models, including R-CNN (link) and SSD (link)" is stronger.
-
Instead of, "Try something more customized with the technique," "Implement a variant of the algorithm described in equations X and Y of this paper" is clearer.
Describe the feature
Describe how the feature helps achieve the use case
Describe how existing APIs don't satisfy your use case (optional if obvious)
As examples:
-
You tried using APIs X and Y and were able to do Z. However, that was not sufficient because of ...
-
You achieved your use case with the code snippet W. However, this was more difficult than it should be because of ... (e.g. ran into issue X or had
to do Y).
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
The issue names no files, tests, or entry points. First clarify the intended QAT behavior for the TensorFlow strided_slice operation and identify the existing QAT operator-support path; done should include an agreed implementation scope and tests demonstrating strided_slice training support.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, tensorflow
- Domain
- machine-learning
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100