-
Notifications
You must be signed in to change notification settings - Fork 260
progress bar added for training and validation, on screen logs structured #204
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
base: develop
Are you sure you want to change the base?
Conversation
…passing issue when only evaluating any pretrained model.
…nal logger and the progress bar
Hi @shubsraj , I created a new PR shubsraj#1 which mainly adds a config parameter ![]() |
Add config parameter `progress_bar`
start_steps = epoch * num_training_steps_per_epoch | ||
|
||
print("Grad accum steps: ", args.grad_accum_steps) | ||
print("Total batch size: ", batch_size * utils.get_world_size()) | ||
# print("Grad accum steps: ", args.grad_accum_steps) |
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.
I'm not sure how helpful these print statements are in the current context, so I left them unchanged. I'll leave it to a core maintainer to decide whether they should be removed or kept.
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.
Every time before an epoch, the same info was printed, so I shifted it to the main code to print it once, before the start of the training while adding a progress bar.
…ured.
Description
A progress bar has been added for training and validation processes, allowing better monitoring of training.
How has this change been tested, please provide a testcase or example of how you tested the change?
YOUR_ANSWER
no special change, just created a progress bar using tqdm and implemented in the main engine code for one epoch and the evaluate function, which adds structure to the logs and making it easier to read.
For example, documentation changes, usability, usage/costs, secrets, etc.
Docs
No change in the documentation
