Skip to content
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

[ASR] Adding ssl config for fast-conformer #6672

Merged
merged 3 commits into from
May 19, 2023

Conversation

krishnacpuvvada
Copy link
Collaborator

What does this PR do ?

Adding SSL config for fast-conformer

Collection: ASR

Changelog

  • Added SSL config for fast-conformer (examples/asr/conf/ssl/fast-conformer/fast-conformer.yaml)
  • Added boolean flags whether to indicate a particular loss is active or not via config file and associated changes ( nemo/collections/asr/models/ssl_models.py file).

Before your PR is "Ready for review"

Pre checks:

  • Make sure you read and followed Contributor guidelines
  • Did you write any new necessary tests?
  • Did you add or update any necessary documentation?
  • Does the PR affect components that are optional to install? (Ex: Numba, Pynini, Apex etc)
    • Reviewer: Does the PR have correct import guards for all optional libraries?

PR Type:

  • New Feature
  • Bugfix
  • Documentation

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

  • Related to # (issue)

adding boolean flags for ssl losses

Signed-off-by: Krishna Puvvada <[email protected]>
nithinraok
nithinraok previously approved these changes May 17, 2023
Copy link
Collaborator

@nithinraok nithinraok left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@nithinraok
Copy link
Collaborator

In examples/conf, fastconformer directory is written as fastconformer here you wrote it to fast-conformer can you make it consistent.

@krishnacpuvvada krishnacpuvvada merged commit b81a3f1 into NVIDIA:main May 19, 2023
6 checks passed
hsiehjackson pushed a commit to hsiehjackson/NeMo that referenced this pull request Jun 2, 2023
* adding ssl config for fast-conformer
adding boolean flags for ssl losses

Signed-off-by: Krishna Puvvada <[email protected]>

* [pre-commit.ci] auto fixes from pre-commit.com hooks

for more information, see https://pre-commit.ci

* renaming fast-conformer to fastconformer in config folder

Signed-off-by: Krishna Puvvada <[email protected]>

---------

Signed-off-by: Krishna Puvvada <[email protected]>
Co-authored-by: Krishna Puvvada <[email protected]>
Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
Signed-off-by: hsiehjackson <[email protected]>
@SatenHarutyunyan
Copy link

The config indicates that MLM loss is not used. Did you get better results with just the contrastive loss? Can you share any of your findings with ssl training on fast conformer please?

@nithinraok
Copy link
Collaborator

Previously with conformer models, we haven;t observed significant gain with MLM loss included for downstream tasks. Hence we used only Contrastive loss this time for FC

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants