move gptq patching to export stage #465
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The documentation is not available anymore as the PR was closed or merged. |
eaidova
force-pushed
the
ea/move_gptq_export
branch
from
1780d90 to
d0df7c9
Compare
|
@AlexKoff88 @helena-intel @echarlaix could you please take a look? |
AlexKoff88
approved these changes
Oct 31, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
move GPTQ patching to export inside export_main to allow convert models using optimum-cli
changed default factory class in OVModelForCausalLM to be able override it (in case if used model class inherited from OVModelForCausalLM, returns instance of this class in backward compatible way, current changes leads to getting always OVModelForCausalLM that may be unexpected from user side)