In which Wildbook did the issue occur? ARW
What happened? I am batch importing photos and running the detection algorithm. For each photo, I then manually launch both HotSpotter and MiewID against a ~300-photos database (Bois de Soeuvres). This is because HotSpotter is not implemented in batch import mode, but 100% of my recaptures were found by HotSpotter and missed by MiewID so far. HotSpotter regularly gets stuck at the “attempting to fetch results” stage. I usually solve the problem by launching the match again and the results appear within minutes. But this time, the problem seems more serious and I cannot get any HotSpotter results for my photos. MiewID works fine.
What did you expect to happen? Get HotSpotter results
What are some steps we could take to reproduce the issue?
See match results for the first 5 photos from this sighting: https://amphibian-reptile.wildbook.org/occurrence.jsp?number=BDS_B_05112024
Thanks!
Hi @nbelouard
It does look like ARW has had over 1000 jobs to work through over the last 48 hours that’s it’s still working to complete. When you re-send your encounters back through ID before they’ve had a chance to complete it doesn’t cancel out the current ID job. It just adds the new request to the already existing queue, further increasing wait times.
Also, we’re still actively working on an issue with MiewID’s accuracy for Salamandra salamandra that was reported here. Once this is resolved, that should help reduce your reliance on Hotspotter, though I am concenred that it needs to be sent twice every time in order to see a match. I’ll have the devs looks into that as well.
For now, let’s wait for ARW to finish working through its job queue and let me know if you’re still having trouble with your matches.
Hi,
Thanks for your response. Got it, I won’t re-send jobs again! I didn’t think previous jobs were kept in memory. I had the feeling that HotSpotter got stuck at the fetching stage when the queue was long at the time I sent the job, and stayed stuck from there. That is, I found it still stuck the day after/at a less busy time, but if I re-sent it at this point, I got immediate results. I am tempted to test it again this time but will give it a day or two!
I should say it does work fine most of the time though. And I am excited to rely on MiewID in the future!
No worries! I learned this morning that the troubleshooting work the machine learning team was doing to fix the MiewID issue I linked earlier was impacting the processing of pending jobs. I hope to have an update for you soon.
To keep documenting the issue, photos 8-10 that I sent to HotSpotter this morning, I got the results in <5 min. Photo 1-7, that I had sent to HotSpotter 4 days ago, are still “attempting to fetch results”. I just re-sent photo 1, and I got the results in 5 min.
When this happens again, can you post the link to the initial match result page with the attempting to fetch results message? It’ll be easier for us to troubleshoot what’s happening if we have that link.
Every match job has a unique task ID, so posting that first URL and then restarting your match again will give you a new URL for the updated match. The encounter will always link to whatever the most recently run match task so I don’t have a way to find that original task that needed to be re-run.
Here they are (I haven’t re-sent those yet, they have been attempting to fetch results since Dec 10):
https://amphibian-reptile.wildbook.org/iaResults.jsp?taskId=c9a6af66-070a-4ab7-8dc8-3a1c67cd413d
Thank you for the links! Just to clarify, once you post those links, you’re free to re-send those matches so you can finish working on IDs. I want to make sure you don’t have to delay any work while we investigate why Hotspotter is being sluggish during its first round of matches.
Got it, thanks. Something’s changed already as I got my first two matches by MiewID this week, yay!
1 Like