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

Evaluating every N epochs should mean that the eval losses are computed only every N epochs as well #32

Open
krasheninnikov opened this issue Apr 20, 2023 · 0 comments
Assignees

Comments

@krasheninnikov
Copy link
Owner

Current behavior is for the eval losses to be computed after every epoch even if N>1. This is because N controls how frequently EvalCallback is called, and eval losses are currently computed inside the trainer, not in our callback.

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