-
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
Fixed bug in trainer notebook #434
Conversation
Continuing discussion from #101 with @robmarkcole and @caleborb6:
What file actually creates
It should be tested on our release branch, right? If not, we should fix that. |
It is created by the CSV logger in the notebook. The CSV logger uses the name of the metrics in the trainer. We changed Cyclone to use the regression trainer and added a more comprehensive set of metrics to log at some point. This involved renaming "rmse" --> "RMSE".
It is uniquely not! Because that notebook involves actually training models, which is not feasible on CPU, we skip it during tests. |
Can we train it for a single mini-batch? |
Whether the trainer works with the dataset is covered by our other tests. The problem here was the logging assumptions (and the specific problem would only show up at the end of an epoch of training). I don't know how to make a good test for this within the notebook. |
Yes, the point of the tutorial tests is not to test TorchGeo, it's to test the tutorials to ensure that they stay up-to-date. |
No description provided.