-
Notifications
You must be signed in to change notification settings - Fork 124
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
Deprecate OVTrainer #1167
Deprecate OVTrainer #1167
Conversation
The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update. |
Works for me, @AlexKoff88 feel free to merge |
@echarlaix, we decided to deprecate and remove it due to low interest. However, we are working on QAT for LLMs which could be contributed as an example by inheriting and implementing the HF Trainer interface instead of bringing it to the core functionality of Optimum-Intel. |
@ljaljushkin, please take a look as well. |
Why deprecating the |
The main reason is to get flexibility in this flow:
|
### Changes Remove paragraphs with link to `https://github.com/huggingface/optimum-intel/tree/main/examples/openvino` ### Reason for changes huggingface/optimum-intel#1167
### Changes Remove paragraphs with link to `https://github.com/huggingface/optimum-intel/tree/main/examples/openvino` ### Reason for changes huggingface/optimum-intel#1167
What does this PR do?
Deprecate
OVTrainer
and related logic as stated in #890.Before submitting