What is the entire URL out of the browser, exactly where the error occurred?
Can you describe what the issue is you’re experiencing?
In our data we have 58 seals and many individuals with 20+ encounters, some with 2-300 photos. We are still having issues when running matches on these popular individuals to have then show up in the “top 12” matches.
Additionally, there has been the case with a few individuals - where one individual who has only been encountered once(or 3 times max), and has 1-3 distinct photos shows up as a suggested and sometimes the only match incredible frequently (even when we are trying to run a routine match with one of our “key players” – BUG_EYEZ is a rare seal, but is recommended almost every match, sometimes the only recommendation
Can you provide steps on how to reproduce what you’re experiencing?
submit new encounter, fill out necessary data
on new encounter page remove any annotations besides the heads where they are above water
on the best photo that shows the most key features create a new annotation and run a match on that
Choose Criteria to match against window:
----------location: US Pacific
----------select only “my data”, use hotspotter and MiewID
Press match
On match page: project selector - select “Howe Sound”
If this is a bulk import report, send the spreadsheet to services@wildme.org with the email subject line matching your bug report
I don’t see a Seal Wildbook account with your name, so I assume you’re using Ania’s account to sign in? If that’s the case, your specific filters may be what’s causing such a limited display of match candidates.
By default, Wildbook looks for match candidates that match your selected location ID, species, IA classes (harbour_seal for bodies or seal+head for just the head annotation), and annotation viewpoint (front with other fronts like frontright and frontleft, etc.). When you limit that filtering to My Data, it will only show you candidates that were uploaded to the account you’re signed into. Then when you filter down to the project, it will only show you match candidates whose encounters have been added to the Howe Sound project.
Looking at the match page you linked, even though Ania has 311 total encounters, only 47 match candidates in total were considered based on your filters and of those 47, it’s only displaying the ones with a match score high enough to be considered valid candidates. For additional context, Hotspotter only displays match candidates with a score above 0, regardless of how how you adjust the Num results field on the match page.
If you’re deleting annotations that include the seal bodies, that’s further reducing your candidate image pool.
Also, if there are specific individuals you expected to see in the match results but didn’t, let me know their IDs so I can take a look at why they may have been excluded.
Yes I am using Ania’s account, she has handed over her responsibilities to me for now and so we are working exact same site. We are very interested in the individuals that are exclusively in the area - that is why we limit it to My Data on the filter.
When I create my own annotations, I am have definitly been including the annotation view point, the classes it only gives me (harbour_seal) as an option on the drop down, I did not even think to type in seal_head.
Would you suggest going back through our data and changing this if it is feasible time wise? Additionally would it be benificial to manually annotate the back catalogue to include the view point on photos that were done automatically.
I should clarify, I have been deleting annotations that have included the seal bodies below the water, 99% of our seal photos are taken while they are milling or swimming and automatically a dark shape with many ripples and reflections is annotated and I remove those.
In terms of specific individuals that very often are not identified correctly is RHS3 in particular(that comes off memory) I have started making a more detailed accunt of this and tracking this but I will wait longer to give you a better more comprehensive list.
Thank you so much for the quick support and getting back to me so quickly!
I just realized that while it can label seal+head for automatic annotations, it’s not displaying as an option in the manual annotation workflow for harbor seals. Let me work on this and get back to you.
There isn’t currently a way to edit IA classes or viewpoints on annotations that are already saved. The workaround is to delete and add a new manual annotation (which we’ve just established is missing the needed IA class). I need to talk to the devs about what next steps would look like here.
Makes perfect sense, thanks!
This is interesting. I spot-checked a handful of RHS3’s encounters and although they’re all of the head above water, the automatic IA class assignments vary. I suspect this is the primary reason other annotations are missing from certain match results (since IA classes are only matched against the same IA classes):
IA classes are seal+head and harbour_seal: Seals Wildbook
Thanks for flagging this. My guess is that the head above water photos were either missing or not well-represented in the original training data for harbor seals, which explains why it can label the viewpoint just fine, but gets confused about whether it’s labeling just the face or the seal’s body when it’s partially visible through the water. I’ll discuss with the team and let you know what I find out.
Thanks for your patience! We’ve fixed the annotation IA class labeling on your existing encounters so that all heads should just have the seal+head label. If any heads are labeled seal, you can manually draw a new annotation and delete the old one. Now when you restart matches on those annotations, you should see more match candidates than you previously did. We’ve also added the seal+head IA class in the manual annotation workflow.
We’re still trying to remove the vitulina IA class from the manual annotation drop-down menu. Make sure to select seal+head for heads and seal for annotating harbor seal bodies.
Thank you so much for catching this!
I’ll let you know when the IA class menu gets fixed.
Thank you very much Anastasia! I will keep you updated on how it goes
I’m always happy to help, and will giving feedback on how things progress its great to be a part of the community!
