-
Notifications
You must be signed in to change notification settings - Fork 21
Improve show methods #511
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
Improve show methods #511
Conversation
…emove old show function
…/scheduler/etc, refactoring train_core, update metrics dict and show_metrics functions
|
I really like this PR, @rwood-97. Haven't had time/been able to test run it yet. Do you need me to do that? |
|
@kallewesterling I've updated the docs and two of the worked examples. Maybe if you have time an ideal thing would be to use the docs to write an example of Let me know what you have time for and I could potentially get @thobson88 or @kmcdono2 to check it. |
Sorry for the late response! I'll check it out and will test run things. I'll also use the docs to write an example of the |
|
A few things:
|
|
Otherwise, looking good! |
|
@rwood-97 Where in the docs do you think we should add the parts about these methods? As a new section under the post-processing step? |
|
Re. docs, I've added them in the I think the two issues in the worked examples are actually okay, I'm just working on moving these over to the |
|
Oh, I see now that you've already added the methods to the documentation. Can you let me know what you need me to do with the docs, then, @rwood-97 ? |
|
I think just have a quick look and check it makes sense would be ideal, otherwise I think this is good to merge |
|
Wiho!! MERGED!! |

Summary
Currently we have some very basic "show" methods for veiwing results. This is good for a quick look but would be better if we had some more advanced tools for visualising our results as part of the MapReader library.
Fixes #341
Address #478 - removed the utils.py file from annotate
Describe your changes
images.py,runner_base.pyandrec_runner_base.pyand addsexplore_xxmethods in each of these classes. Explore uses geopandas explore to create an interactive visualisation of results.check_georeferencingmethod ot the runners as this is needed to ensure we can convert to geo coords and therefore use the explore methods.infer_coords_from_patchesmethod in images.py which uses patches to infer parent coords. This is for e.g. if you have loaded patches via theload_patchesmethod and only added patch metadata (e.g. predictions).classifier.py- now instead oftrain_loss_epochandtrain_fscore_epochas the key for a dict, we have nested dict with keys oftrain,val, etc and then within that keys ofloss,fscoreetc.plot_metricsmethod, users now pass a list of metrics to plot (e.g. "loss", "fscore_micro", etc) and it will plot by default all phases. Can tell it just to plot for one phase by passing thephasesargument.Using the
show_patchesmethod:Using the
explore_patchesmethod:Using
explore_predictionsmethod (i.e. the equivalent toexplore_patchesbut for text spotting):Checklist before assigning a reviewer (update as needed)
Reviewer checklist
Please add anything you want reviewers to specifically focus/comment on.