-
Notifications
You must be signed in to change notification settings - Fork 213
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
Update intersect_dense.cu #797
Conversation
M. |
OK, we will have a try.
|
And please also try changing clip-grad to clip-grad-norm .. sometimes in
LSTMs, we can get grad explosion.
I don't know whether it might be possible to print out the total gradient
norm for each step. that will let us know if gradient explosion is
happening
(caution: if this does happen, it might be quite rare).
…On Fri, Aug 6, 2021 at 11:37 AM Mingshuang Luo ***@***.***> wrote:
OK, we will have a try.
M.
I think it would be better to put the score difference in special buffer
computed for that purpose (perhaps one element per FSA in the minibatch),
that can be transferred to CPU and the largest difference printed as a
warning if it is larger than 1.0. If we just let this happen silently, and
the score diff is larger than the beam, intersection may sometimes fail and
we won't have any idea why it failed.
You may need Kangwei's help with this.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#797 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAZFLO7QP75ASU3UVXS24ATT3NKHDANCNFSM5BUBAGMQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email>
.
|
Get it.
|
When I change clip_grad_value_ to clip_grad_norm_ in mmi_bigram_train.py, there are two good results.
|
Let's not change the other scripts until we have time test the effectof the change. For now we can merge this PR, after you have updated the RESULTS.md. |
OK, I get it.
|
When I run the new mmi_bigram_{train, decode}.py, there is a bug such as the following.
With kangwei's help, I remove some lines code in k2/csrc/intersect_dense.cu and the script can run successfully.
So I make a PR to update the intersect_dense.cu. I'm not sure if there are other ways to modify it.