[examples] flux-control: use num_training_steps_for_scheduler #11662
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.
[examples] flux-control: use num_training_steps_for_scheduler in get_scheduler instead of args.max_train_steps * accelerator.num_processes
What does this PR do?
Fixes #11661
Closes #11661
By using the already prepared
num_training_steps_for_scheduler
in the intended way, we make sure that theargs.max_train_steps
variable gets not accessed in case it is None.Before submitting
documentation guidelines, and
here are tips on formatting docstrings.
Who can review?
@sayakpaul