-
Notifications
You must be signed in to change notification settings - Fork 379
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
Add TorchGeo CLI tutorial #2479
Conversation
|
Yeah, I'm not sure if there's an easy way to know the name of the trained model checkpoint to use. Maybe we can specify the name to use? I wish |
You can setup a ModelCheckpoint to save last then point it to |
Hmm, I'll look into it, but I'm hoping to not make the config.yaml too complicated. |
Then we need to be really clear that "torchgeo test" and "torchgeo validate" are just going to return results from a random initialized model (which is.... not helpful). I think a reader would expect "torchgeo test" to test the trained model as the tutorial is written currently. We should also show users how to actually test their model too because that's going to be what people want to do with "test" or "validate" lol |
Fixed |
* Add TorchGeo CLI tutorial * Pass checkpoint path
Basically copied the docs from the README to a tutorial.