Fixing val.py incorrect recalls issue #43#44
Conversation
|
Instead of hardcoding, can't we use |
|
Also, what are the recalls for Patch-NetVLAD (compared to vanilla NetVLAD)? |
I don't think so, since msls concatenates the two datasets together. So eval_set.qIdx contains a list of query indices that are from both datasets. |
|
I've made changes that now means that val.py should work in the general case, with any combination of mapillary cities. Please re-review and let me know your feedback. |
|
Thanks, lgtm! What do you think @oravus? |
|
Yep, this should do (ignore my earlier comment). |
|
Agreed that it's not very nice atm. I've got a plan, let me fix tomorrow |
|
Fix #43 |
|
Hey @StephenHausler @oravus - I think f06d664 makes it a bit cleaner. I did "open loop" coding though and haven't tested if it still works properly - could you please check @StephenHausler? |
|
I've just tested the code, it works perfectly. Thanks Tobi for your refactor, looks great |
Made changes to val.py that should fix the indices issue that was causing low reported recalls for mapillary validation on the cph and sf datasets. Without PCA, the recalls with NetVLAD (with the mapillary trained model) are now: 0.495, 0.65, 0.718, 0.77, 0.83, 0.868.