-
Notifications
You must be signed in to change notification settings - Fork 84
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
why my loss is negative and 0.000000 #29
Comments
Dice loss is negative and bounded ( = it is ok ) Line 471 in 8dd13e4
Hope it helps daddy. |
and read again readme - sec training |
what its meaning?please say clearly, thanks! |
my guess is that your data is not in expected format - try to run it with -debug=1
|
On Fri, 17 May 2019 02:08 Kei_Cin, ***@***.***> wrote:
I've faced with the same issue in seg_loss, ctc_loss and reg:
[image: Screenshot from 2019-05-17 16-01-48]
<https://user-images.githubusercontent.com/45931733/57916530-32ec2680-78bd-11e9-9e3d-a4723d533f03.png>
Follow your above advice, I've run with -debug=1 and find some images,
but this below example is confusing me:
[image: Screenshot from 2019-05-17 16-05-38]
<https://user-images.githubusercontent.com/45931733/57916791-c6255c00-78bd-11e9-9cbf-21b772b2639c.png>
Why does it just a part of my training sample?
The loss is still zero and negative after 2000 step. Is it right or what I
need to do to fix this?
You have to fix this
1. input size should be at least 512 - otherwise a lot of words will be
partially out of image = do not care see training parameters in Readme
… Thanks a lot, sir!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#29?email_source=notifications&email_token=AA7KHMAGXTNGX7JYQDGYNDLPVZY2HA5CNFSM4HIEMRQKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODVUGUNI#issuecomment-493382197>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AA7KHMAXPP7DIWZMCMSKT4DPVZY2HANCNFSM4HIEMRQA>
.
|
why my loss is negative and 0.000000,please help child!!@MichalBusta
like this:
The text was updated successfully, but these errors were encountered: