Sharkbook matching against global database timing out

Support
, ,
1

What Wildbook are you working in?
Sharkbook

What is the entire URL out of the browser, exactly where the error occurred?

Can you describe what the issue is you’re experiencing?
Running a match against the global database will be in “Waiting for results. The machine learning queue is working.” state for hours before timing out, resulting in “error initiating IA job”

Can you provide steps on how to reproduce what you’re experiencing?
right click on image → start another match → Location ID select all → tick MiewID → Match

If this is a bulk import report, send the spreadsheet to services@wildme.org with the email subject line matching your bug report
not a bulk import

I also checked the machine learning queue (Administer > Data Integrity > Wildbook Machine Learning Queue Monitoring (slow load)); but this does not seem to be the issue:

Current Queue Status

  • Wildbook Image Analysis (WBIA) Machine Learning Server
    • There are currently 0 detection jobs waiting to complete in WBIA.
    • There are currently 0 ID jobs waiting to complete in WBIA.
  • Queuing in line for WBIA
    • There are currently 0 slow lane ID jobs waiting to go to WBIA in the slow lane.
    • There are currently 2 detection and ID jobs waiting to go to WBIA in the fast lane.

Tasks Completed in the Last 24 Hours

  • Detection: 11
  • ID: 218

cheers
Ingo

2

Hi @ingomiller

This is a known issue in Sharkbook. Selecting more than the original location ID causes an IA error:

The current workaround is just to send to identification for the location ID on the encounter since that has been returning results normally.

3

Thank you. This is what we have done - matching against Local ID (East Australia). But we will need to match against the global, or at least Pacific/Indo-Pacific too, considering the migratory nature of our species (whales shark).
Is there a better work around, or bug fix in progress? Need this for a manuscript to be submitted very soon …
Cheers

4

I don’t currently have a timeline for resolution. There is no current workaround for getting results from multiple location IDs.

5

Quick update: We’ve discovered that the single-digit location ID names in Sharkbook (like 2, 7, etc.) are what’s causing the matching issues you reported. We’ll be working on fixing the location ID names in Sharkbook as part of the Wildbook 10.7.0 release and this will fix the matching errors when checking for matches with multiple location IDs.

6

Good news!

Any idea when the new release is coming out?
Just to get an idea if I should continue checking against single location IDs, or wait for the release…

Thanks

7

10.6 is likely coming by the end of the month and 10.7 could be roughly 1-2 months after that.

8

Roger. I’ll keep matching then.

Cheers

1 Like
9

Good news! We were able to get the location ID updates in today. Do you mind trying a match with multiple locations and letting me know if you can see matches now?

10

Good news, indeed!

I can confirm it works.

Thanks for the quick fix!

1 Like