-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Refactor ScriptArguments
#2145
Refactor ScriptArguments
#2145
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. |
gradient_checkpointing_use_reentrant (`bool`, *optional*, defaults to `False`): | ||
Whether to apply `use_reentrant` for gradient_checkpointing. | ||
ignore_bias_buffers (`bool`, *optional*, defaults to `False`): | ||
Debug argument for distributed training. Fix for DDP issues with LM bias/mask buffers - invalid scalar type, |
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.
It seems to be a debug argument. Should we remove it like in #2055?
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.
Thanks for harmonizing all this, LGTM apart from 1 change about the split for some of the RL examples, if you change it be sure to update the docs etc.
What does this PR do?
Script arguments class is defined
trl/examples/scripts/orpo.py
Lines 64 to 69 in 70036bf
SFTScriptArguments
:trl/trl/commands/cli_utils.py
Lines 82 to 94 in 70036bf
DPOScriptArguments
:trl/trl/commands/cli_utils.py
Lines 112 to 129 in 70036bf
RewardScriptArguments
:trl/trl/commands/cli_utils.py
Lines 97 to 109 in 70036bf
They are pretty much the same. I suggest:
ScriptArguments
SFTScriptArguments
,DPOScriptArguments
andRewardScriptArguments
in favor ofScriptArguments
.ScriptArguments
to all examples scripts.Before submitting
Pull Request section?
to it if that's the case.
documentation guidelines.
Who can review?
Anyone in the community is free to review the PR once the tests have passed. Feel free to tag
members/contributors who may be interested in your PR.