Detection not working for wild dogs in ACW

In which Wildbook did the issue occur? African Carnivores

What operating system were you using? MacOS Sequoia 15.5

What web browser were you using? Chrome

What is your role on the site? Researcher

What happened?
Bulk import works fine, detection process doesn’t (notification of completion, but nothing happened). Next, ‘identification’ is offered; bulk import has to be deleted and re-uploaded for ‘detection’ button to reappear.

What did you expect to happen?
To find many bounding boxes after completion of job…

What are some steps we could take to reproduce the issue?
Upload any wild dogs bulk import and send it to detection.
(Btw, this seems to be only a bug in wild dogs, other species work fine.)

Hi @dabegg, welcome!

I looked at your 3 most recent bulk imports and I see that detection hasn’t started yet, but the detection button is visible on each of them:

It’s not clear whether these are are meant to be re-upload attempts where the detection button now appears or if there’s something preventing the buttons from showing up on your end and that’s why detection hasn’t been started.

Can you share one or more of the spreadsheets from your bulk imports to services@wildme.org so we can troubleshoot this further?

Hi Anastasia,
Thank you very much for your quick reply.
The bulk imports you mentioned are re-uploads where detection did not work. I have just tried to send the first one to detection once again, but it is still the case that I can press the button, the job is then displayed as ‘completed’, but in fact no bounding boxes have been drawn. After that, only the option ‘send to identification’ is available (see print screen for current example:


), so that the bulk import has to be deleted and re-uploaded in order to see the ‘detection’ button again. I hope my explanation makes sense, and I 'll be happy to provide the upload spreadsheets if required.

Thanks for sending your spreadsheet and for the clarifying details! I’ll look into this and follow up with you soon.

Hi @dabegg

I haven’t been able to replicate this so far in testing. Do you mind emailing me some of the images from this import to see if something with the files is the issue?

Separately, it looks like one of your columns in mislabeled. The field name is “u” but I suspect it’s supposed to be the Encounter.occurrenceID field.

Also, the devs have asked if you upload a new bulk import and are missing the detection button, to leave it alone and send us the link to the import so we has as much information as possible to debug.

Just to clear up any misunderstandings: the ‘detection’ button is visible after uploading. However, when you click on it, detection does not work and the ‘identification’ button appears next.

Ah, ok, I understand now. Thanks for sending the additional spreadsheet and images! I can replicate this in bulk import and also in the Report an Encounter workflow.

I hope to have an update later today.

Thanks for your patience! Detections were completing on the backend but weren’t displaying on the frontend, which is why it had the send to identification button displayed. We’ve fixed the issue and I can now see annotations in these imports:

The third one I previously linked above appears to have already been deleted.

If there are more imports that haven’t actually completed detection, post their URLs here and I can force them back through.

Hi Anastasia,
Thank you very much for quickly resolving this issue - detection is now working perfectly again.

1 Like