What is the entire URL out of the browser, exactly where the error occurred? TroutSpotter
Can you describe what the issue is you’re experiencing? I have 10+ bulk imports and decided to start sending them to the IA. I haven’t seen results for any of the images after a few days, and get “error initiating IA job” when I click on an individual encounter’s link. These are large batches but it’s been several days since I started a few of them.
Can you provide steps on how to reproduce what you’re experiencing?
If this is a bulk import report, send the spreadsheet to services@wildme.org with the email subject line matching your bug report
I spot-checked a few of your recent imports and it looks like detection has completed on them. Once the Computer Vision Status at the top of the import table shows detection complete, you can scroll to the bottom of the table and click on the Send to identification button once you’ve selected the regions to search for match candidates.
Once identification runs, you’ll be able to see your match results.
I’ve been selecting “send to identification” on a handful of my bulk imports and am only seeing images as “trout: queuing” or “trout: waiting to queue”. It’s been days since sending them and I’m only seeing one photo in one bulk import that is showing that it’s complete, or “trout:completed”.
When I click on this fish (encounter d8bb6b69), I’m unable to annotate it at all. It has an option to “confirm no match”, but shows an error when I select this option that reads “Something went wrong with assigning the new name to the individual containing encounter d8bb6b…”
Should I keep sending all of my bulk imports “to identification”, or will this clog the system up?
Can you link to the encounter you’re referring to? I don’t know which bulk import it’s from and I’m unable to search for it with the partial ID you shared.
Hold off for now while I verify what’s causing the errors. I hope to have an update soon.
Thanks for hanging in there. I think this was just a hiccup in WBIA because I manually re-ran a single encounter from one of your imports and got match results back pretty quickly.
Thanks for looking into this! I waited to check up on this incase things needed time to run, but it looks like things are still stuck. Here’s what I’m still seeing on my end:
One bulk import ( Import Task 48220d28-c4b4-48dd-9310-f8142d1a99d5) has an “IA?” label as “detection”.
Only one trout in “trout: completed” and still does not give me the option to annotate (TroutSpotter)
One trout in “trout: queuing” and says “error initiating IA job” (TroutSpotter)
All 13 other jobs appear to be stuck in “trout: queuing” mode, too.
This only means that the import has been sent to detection. If the field is blank in the Import Tasks table, it means it hasn’t started detection yet. When it’s sent to identification, this field changes to “identification.”
I see an annotation and match results here. I’m not sure I understand what you mean about not having the option to annotate. I can see the “add annotation” option in the menu of the image form the encounter page. You can view our help docs on manual annotation if you want to manually change the annotation on this encounter: Manual Annotation (Beta) — Wildbook documentation
I sent this import to ID. It looks like maybe you had sent just the encounter to detection manually from its encounter page? They’re all showing as waiting to queue now. Let me know if you run into any other issues.
Apologies, I was misusing the term “annotation”. I meant confirming match or no match. For the fish I mentioned previously, this is what I’m seeing when I want to confirm that there is “No Match” between the individuals.
Thanks for clarifying! This is a known bug that was fixed in version 10.3 of Wildbook. Troutspotter is currently on version 10.2, so this won’t be a problem when it gets an update (we’re gradually working on updating all Wildbooks to the same version). In the meantime, you can click on the edit button of the Identity section of the encounter page to assign a new ID for it.
The general answer is it depends on how many jobs are waiting in the queue. However, given how much time has already passed and Troutspotter doesn’t usually ahve a lot of traffic going on there, I’m looking into if this is an issue with this version of Wildbook not correctly reflecting when no matches are available. Similar to what was reported in ACW.
