What Wildbook should this feature be in? GiraffeSpotter
What would you like to see? We recently removed HotSpotter from the default algorithm for GiraffeSpotter and made MiewID the only default, with HotSpotter only there on standby for single re-rematches. Is it possible the have HotSpotter a default unchecked box when sending to match, so it is available for running an entire job when needed? Such as how it remaing for sending a single encounter to match (as pictured below)
How would this functionality help you? In some cases, MiewID is working fine (e.g., Angolan giraffe in Namibia) but it is still not performing well for Luangwa giraffe in Zambia. As such, for every single encounter annotation a person is requred to send each to re-match with Hotsotter and this manual requirement is taking a very long time to get through. It would really help if for some cases (e.g., Luangwa), one could select to send the job to HotSpotter (while still keeping the default at MiewID).
Thank you
Note: Not all feature requests can be accepted, but all of them are reviewed by our product team. We’re unable to provide implementation timelines for accepted requests. We are a small team with many competing priorities. Thanks for your understanding!
Hi @CourtneyMarne
I’m not sure I understand the request. Is the option to select Hotspotter is missing from a specific species or you asking about being able to send multiple encounters at once through Hotspotter?
Multiple encounters at once through Hotspotter yes.
When first sending to match (after detection complete) there is no option to select the algorithm - it is default MiewID. After first run, if the match was not possible, one can rematch and then the option to select the algorithm appears to then use hotspotter or miewID (as in the screenshot). However, we are having 100s needing to be rematached with HotSpotter in the Zambia data, and it taking too long to send each encounter annotation to rematch manually one by one. It would be really helpful to be able to chose to send the entire job again to hotspotter in the Zambia cases. I hope this is more clear! 
Thanks for clarifying!
@jason for visibility.
This main reason for disabling Hotspotter is that it works really well on smaller jobs, but consumes an exponential amount of data as jobs get larger and the database of images to compare against grows. It sounds like a better solution would be to discuss retraining MiewID to see if we can get higher confidence matches if you’re seeing cases where hundreds of encounters aren’t displaying suitable candidates.
Thanks @Anastasia, unfortunately we have no more Luangwa giraffe images than those already uploaded, and (if I’m not mistaken) I believe it was done relatively recently. But if we could improve it that would help for sure
