Implementing exaone3.5 #1480
Draft
Implementing exaone3.5 #1480
+106
−32
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
…ementing-exaone3
…ementing-exaone3
|
@KareemMusleh Thanks for the effort! I was just curious of the general process you go through to implement something like this. Is it different for every model, and how so? |
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.
This is my first attempt at an implementation of exaone into unsloth, it was requested in this issue.
I didn't want to implement exaone into a separate model class because exaone follows the llama architecture as was discussed in this issue. As of now I am having problems with the from_pretrained function when using config and state_dict. I've already opened an issue in transformers about it. I'll try to solve that problem soon.