-
Notifications
You must be signed in to change notification settings - Fork 2k
DOC: Explain uninitialized weights warning #2369
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
Merged
BenjaminBossan
merged 2 commits into
huggingface:main
from
BenjaminBossan:doc-troubleshooting-weights-not-initialized
Feb 10, 2025
Merged
DOC: Explain uninitialized weights warning #2369
BenjaminBossan
merged 2 commits into
huggingface:main
from
BenjaminBossan:doc-troubleshooting-weights-not-initialized
Feb 10, 2025
Conversation
This file contains hidden or 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
Users sometimes get confused by the warning from transformers that some weights are uninitialized and need to be trained when they use models for classification. A recent example is huggingface#2367. Even though the warning does not come from PEFT, let's add a section to the docs to explain this warning, as the situation is a bit different here.
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. |
stevhliu
approved these changes
Feb 7, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great explanation!
Co-authored-by: Steven Liu <59462357+stevhliu@users.noreply.github.com>
BenjaminBossan
added a commit
to BenjaminBossan/peft
that referenced
this pull request
Feb 18, 2025
Users sometimes get confused by the warning from transformers that some weights are uninitialized and need to be trained when they use models for classification. A recent example is huggingface#2367. Even though the warning does not come from PEFT, let's add a section to the docs to explain this warning, as the situation is a bit different here. --------- Co-authored-by: Steven Liu <59462357+stevhliu@users.noreply.github.com>
Guy-Bilitski
pushed a commit
to Guy-Bilitski/peft
that referenced
this pull request
May 13, 2025
Users sometimes get confused by the warning from transformers that some weights are uninitialized and need to be trained when they use models for classification. A recent example is huggingface#2367. Even though the warning does not come from PEFT, let's add a section to the docs to explain this warning, as the situation is a bit different here. --------- Co-authored-by: Steven Liu <59462357+stevhliu@users.noreply.github.com>
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.
Users sometimes get confused by the warning from transformers that some weights are uninitialized and need to be trained when they use models for classification. A recent example is #2367.
Even though the warning does not come from PEFT, let's add a section to the docs to explain this warning, as the situation is a bit different here.