-
Notifications
You must be signed in to change notification settings - Fork 2.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
[Codec] Update codec checkpoint config #7835
[Codec] Update codec checkpoint config #7835
Conversation
create_wandb_logger: true | ||
wandb_logger_kwargs: | ||
name: ${name} | ||
project: ??? |
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.
Should we keep the convention that all ???
be at the top of the file? I think TTS is the only domain which does it currently.
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 don't have a strong preference.
We could move to the top, set it to project: audio_codec
or possibly remove altogether (wandb.init
API indicates it's optional, but haven't tested it).
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 think for wandb the "name" field is supposed to be the name of a specific run to track. "project" is the category to sort runs by.
So project could be set to ${name} or some other hardcoded value. Name can be removed, assuming user will override it if they want to organize their runs (if not provided then wandb generates a random name like happy-giraffe-42)
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.
We can set both to null
, seems to be common across other recipes:
wandb_logger_kwargs:
name: null
project: null
03e4712
to
a2f521e
Compare
jenkins |
CI failing with an unrelated error
|
a2f521e
to
f99f5a1
Compare
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 Ante. LGTM.
CI failing on |
They are coming from megatron. |
f99f5a1
to
8f012da
Compare
Rebasing onto |
Signed-off-by: Ante Jukić <ajukic@nvidia.com>
8f012da
to
9ba6d81
Compare
jenkins |
Signed-off-by: Ante Jukić <ajukic@nvidia.com> Signed-off-by: Piotr Żelasko <petezor@gmail.com>
Signed-off-by: Ante Jukić <ajukic@nvidia.com>
What does this PR do ?
Update codec configs to always save NeMo checkpoint with best
val_loss
.Collection: TTS
Changelog
checkpoint_callback_params
to always saveNeMo
checkpoint with bestval_loss
and to save 5 best checkpointscreate_wandb_logger
totrue
, sincemodel.log_config.log_wandb
is set totrue
by defaultUsage
N/A
Before your PR is "Ready for review"
Pre checks:
PR Type:
If you haven't finished some of the above items you can still open "Draft" PR.
Who can review?
Anyone in the community is free to review the PR once the checks have passed.
Contributor guidelines contains specific people who can review PRs to various areas.
Additional Information