IoT Annotations & match results

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:

Encounter1
Encounter2

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

1 Like

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

The IoT upgrade started on Jan 22, so any uploads made between then and the 24th would likely have run into WBIA issues as the notice recommend users to pause new uploads during that time.

Because these were uploaded during the maintenance period, these will need to be manually annotated since WBIA was unavailable during that time.

I re-sent these to ID. Results should come back soon.

Have any of the issues you or your team run into been occurring after the upgrade completed on the 24th or are these mostly just lingering issues from before and during the upgrade period?

Detections in IoT should now be fixed. It’s been gradually getting through the backlog of stuck detections.

I’ve spot-checked encounters and matches from your recent links and I see annotations and match results on examples 3 and 4. If you still see pending detections after the weekend, let me know.

Hi!

Feedback from my team indicates that the detection and the following matching process still is not running smoothly, even for recently uploaded encounters. Processing times exceed several hours (non-bulk uploads) or even days. All examples I had compiled by the end of the week had processed by this morning (min. 48h later), so I can’t attach a negative example here.

Not sure if this is still part of a backlog or if there is a way to check on processing times from your end. Sorry, this is not as substantial a feedback as I’d hoped!

It’s still helpful context to have; thanks for the update! Let me discuss with my teammates and I’ll let you know what I hear back.

1 Like

It looks like there have been some significant job peaks in IoT over the last week, which tracks with the behavior you described of detection and jobs completing, but slower than expected.

WBIA is behaving as expected given the job volume it’s seeing.