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

How to specify 'mode' when using checkpoint_on in the new Result types. #3401

Closed
Rob-Fletcher opened this issue Sep 8, 2020 · 4 comments
Closed
Labels
question Further information is requested won't fix This will not be worked on

Comments

@Rob-Fletcher
Copy link

What is your question?

I have been using PL for a while now and am just getting around to switching all of my code over to a newer version (0.9.0 from 0.6.0). I would like to switch over to using the newer TrainResult and EvalResult types instead of plain dictionaries. In the past I used a ModelCheckpoint() that I passed into the trainer with the monitor and mode options set. Now using the EvalResult type and passing it a 'checkpoint_on' option, I dont know how to specify a mode (min or max). Is this possible? Looking through the code it seems like maybe you can still pass a 'mode' through the ModelCheckpoint() but this seems a bit strange since it splits up what you are monitoring and whether its a min or max into two different places that you have to specify (one in my model and another in the ModelCheckpoint() ). Is this right? If so would it make sense to add the ability to pass a mode in with the {Train/Eval}Result as well?

@Rob-Fletcher Rob-Fletcher added the question Further information is requested label Sep 8, 2020
@github-actions
Copy link
Contributor

github-actions bot commented Sep 8, 2020

Hi! thanks for your contribution!, great first issue!

@Rob-Fletcher
Copy link
Author

If there currently isnt a way to do this and you guys think its needed I can make a PR.

@carmocca
Copy link
Contributor

mode is currently passed to ModelCheckpoint. I am with you in that it is confusing having the metric and the mode in different places. We have a discussion over at #3286 about how we should fix it.

@stale
Copy link

stale bot commented Oct 21, 2020

This issue has been automatically marked as stale because it hasn't had any recent activity. This issue will be closed in 7 days if no further activity occurs. Thank you for your contributions, Pytorch Lightning Team!

@stale stale bot added the won't fix This will not be worked on label Oct 21, 2020
@stale stale bot closed this as completed Oct 29, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested won't fix This will not be worked on
Projects
None yet
Development

No branches or pull requests

2 participants