IoT Matching process, result, incorrect data selection issues

In which Wildbook did the issue occur? IoT

What operating system were you using? (eg. MacOS 10.15.3)
Windows 10
What web browser were you using? (eg. Chrome 79)
Chrome Version 91.0.4472.124,
What is your role on the site? (admin, researcher, etc)
Researcher, Rest, Machinelearning
What happened?

  1. Matching process (again unfortunately, with or without hotspotter) is very slow or not working. Stuck on ‘attempting to fetch results’. This happens after uploading a new encounter, as well as after trying to ‘start another match’ on old entries
  2. Match results will display results from same event. (comparing images from same encounter)
    Internet of Turtles
  3. Sometimes it will try to match against encounters from outside ‘my data’
    Internet of Turtles
  4. results for known turtles, turtles that we have multiple encounters from, will not be matched up or listed in results. In these instances I have to assign the correct ID manually. But even after running another match it will still not match up with images of different encounters of that individual.

What did you expect to happen?
For the correct matches from my data to be listed
What are some steps we could take to reproduce the issue?

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

Hi, @noaahawaii !
These issues sound eerily similar to some that we have solved recently on other platforms. I’ll plan on updating IoT this week, and then can we see whether that fixes your issues?
Cheers,
Mark

Hi @MarkF! Just checking on the status of the fixes/ updates.
Do I need to re-run all of my last uploads?
Thank you for your help!

Hi, @noaahawaii !
Still no the docket! There’s been a lot of activity on community lately, so the backlog has been growing. But I have not forgotten you, and you’re definitely on the queue!
-Mark

Hi, @noaahawaii !

I fully updated IOT today. It looks like your issues are persisting. I created a ticket for us to track this issue internally: WB-1731.

Thanks for bringing it to our attention.
-Mark

@MarkF

Thank you for your effort.

Should I keep uploading or pauze until there is a proper fix since issues are persisting?
If there is no properly functioning matching process and I only assign (temporary) ID’s to individuals would that still work, or am I then only creating a lot more extra work for myself because I would have to go back in later once there is a fix and run the matching process again to properly compare individuals?

Is there also a way for me to track the internal issue or would I be notified of the progress once ready?

Thank you for your help!

Hi, @noaahawaii !

My responses below:

Should I keep uploading or pauze until there is a proper fix since issues are persisting?

Yes. Adding media/encounters to the system will not be affected, so carry on with this.

If there is no proper functioning matching process and I only assign (temporary) ID’s to individuals would that still work, or am I then only creating a lot more extra work for myself because I would have to go back in later once there is a fix and run the matching process again to properly compare individuals?

I’m not super clear what you mean here. If you are able to find and confirm a match with PIE or hotspotter using the manual annotation tool, you can go ahead and assign the ID (perhaps for an individual that already exists in the database, for instance) that way. If you find yourself assigning “temporary” IDs (this is the part of your response that I’m a little confused by), I’d say just hold off on doing that until matching the way you’re used to is fully restored. If you haven’t used the manual annotation tool before, it might be worth reading about and trying! I’d love for @tanyastere to weigh in on this one if her opinion is different from mine.

Is there also a way for me to track the internal issue or would I be notified of the progress once ready?

Unfortunately, not yet. But it’s part of the protocol for us to loop back around when the task is completed and let you know here!

Cheers,
-Mark