Writing on behalf of Olive Ridley Project this error has occurred for our users in Seychelles, North Male and Laamu
When submitting an encounter IoT annotations are not being detected/added automatically. This has persisted including returning to check for annotation detection the next day.
Further to this when attempting to fetch results IoT times out and gives up fetching results.
Please advise
Hi @Splinter, welcome!
Can you link to some of the encounters you’re having trouble with so I can look into this further?
Hi!
See some examples here:
Encounter1 (manual annotation, matching not processing)
Encounter2 (waiting for detection since Dec 31st)
Encounter3 (manual annotation, matching not processing)
Encounter4 (waiting for detection)
Encounter5 (manual annotation, matching not processing since Dec 30th)
Hope this helps.
Even if recent encounters passed through detection and then matching, an error appears for the suggested match results, such as in the encounter below. I can see the inspection images, so it’s not actually an error, but still thought I’d flag it as the system being somehow unhappy.
Encounter with Error for inspection image (“Error. Something went wrong fetching the inspection image”)
Best,
Steph
Just a brief addition: When starting a new match, it might start but then I end up with the error message “error initiating IA job”.
Thank you! Usually if restarting a match after receiving an error doesn’t help, then something might be going on with WBIA. I’ll let you know as soon as I have an update.
Hi!
Is there by any chance an update here?
Since Jan 3rd, it seems to have processed things occasionally, but it’s very inconsistent. Still the same problems with annotation detection & then WBIA.
Best,
Steph
Sorry for the delay! I know the devs began looking into it last week, but I need to check in to see what the outcome of that investigation was and whether any match errors will re-run automatically or need to be pushed through manually.
We’re re-syncing acmIDs and re-sending those to detection. That should complete today and you’ll be able to re-send those encounters to identification to see match results.
I got confirmation this morning that detection has caught up if you want to start re-IDing today.
Thank you for the feedback - I’ll give it try today with new encounter uploads.
From what I can see though detection/annotation creation has not caught up yet for some pending encounter, see for example:
Should we reupload the images for those or what’s the best procedure? I don’t want to set manual annotations on these to avoid encounter duplication.
Good news: in a future version of Wildbook, you’ll be able to edit existing annotations and avoid the unintentional clones that happen when you need to fix a bad annotation. I’m really excited about what I’ve seen so far!
I’m gonna check to see if there are any other stray encounters that didn’t get detections re-synced and then get back to you. I just want to clarify if you’re seeing this with new uploads or if you’re only seeing this on ones uploaded before Jan 16th.
Editing annotations sounds absolutely brilliant, I am excited to here!
The synchronisation issues happens both with encounters predating Jan 16th and it did happen during new uploads yesterday again as well.
Anastasia,
I am running into the same issue. Encounters that have been uploaded starting on 1/6/2025 are still waiting for detection. I have since went back through and added annotations to a few of them. Any update on this. Encounter 1
These detections are complete.
We’re working on this today.
Thanks for the example! We’re working on another re-sync today that will go back a bit further than our initial attempt to resolve this.
Hi!
Not sure this is fully functional again, e.g. Encounter1 for which detection is complete, now has the issue that there is no option to start another match in the drop down menu.
Not necessatily a problem in case of known individuals, but it is for potential new turtles which I’d like to check against other subsets of the data.
Another example is this Encounter3 - annotation is on the image, but still listed as detecting & can’t run match.
Apologies if this is simply because the system is overall still processing, just thought I’d flag it right away.
Best,
Steph
No worries; this is good feedback! I checked against some other encounters to see if the missing “start another match” option was widespread, but I still saw it available on other encounters. I’m looking into why it’s not appearing on this encounter.
Do you mind deleting and redrawing the head annotation on that picture and let me know if that works?
Just went to check if redrawing the annotation would work for the Encounter1. Now the dropdown menu did contain the “start another match” option, so it just seems to be a delay?
Redrawing annotations does work, I had tested this on another encounter before. Should I still try it for this one for consistency?
It looks like the team is still in the middle of upgrading IoT, so let’s hold off on troubleshooting this since WBIA will be impacted until the update is complete.
Now that the IoT upgrade is complete, do you mind trying again now with the annotation fix?
Hi!
Manual annotations will allow me to “start a match”. I have occasionally experienced issues with the placement of a manual annotation, which is another issue though (probably for another thread). Matching process takes a while then (20mins?). I can select “start another match” from the dropdown afterwards.
Detection still is very slow on newly uploaded encounters. Encounters uploaded on Jan 22nd still not annotated (see for example1, example2)
Encounters uploaded earlier in January have annotations. When clicking “match results”, it is stuck in “Waiting for match results” though (example3, example4).
I am only giving a few examples here from a location I am uploading myself, but all ORP team members/accounts are experiencing the same issue.
Best,
Steph
