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

Concerning definition for running_loss #8

Open
phucdoitoan opened this issue Feb 28, 2020 · 1 comment
Open

Concerning definition for running_loss #8

phucdoitoan opened this issue Feb 28, 2020 · 1 comment

Comments

@phucdoitoan
Copy link

phucdoitoan commented Feb 28, 2020

It is not an issue. I just want to ask why do you use running_loss = running_loss*0.9 + loss.item()*0.1 for monitoring the loss during training?
Do you have any special reason for this?
Isnt it conventional to monitor the average loss after each epoch (in this case, after each iteration)?

@Andras7
Copy link
Owner

Andras7 commented Aug 24, 2020

Hi,
I've used the moving average because it seemed more useful for me (it forgets the past), but feel free to use anything else.

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

No branches or pull requests

2 participants