Change tie_weights to no-op and add docstring for weight tying clarification #503
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 pull request addresses #485 and updates the
tie_weights
function in theOLMoForCausalLM
class to be a no-op and adds a docstring explaining the reasoning behind this change.The
tie_weights
function is being made a no-op because weight tying is already handled explicitly in other parts of the codebase. This change avoids redundant weight tying logic and improves code clarity.The added docstring explains why the function is a no-op and directs developers to the specific locations where weight tying is handled. This improves code readability and maintainability.
This doesn't fix the warning message from the
accelerate
library, which expects a fundamentally different mechanism for weight tying.@2015aroras ready for your initial review—thanks!