Same annotations in different places depending on view (related to odd media asset size possibly?)

Related issue while logged in to ACW as researcher.

Encounters > My Submissions > After list populates, select “Matching Images/Videos”. This appears to bring up all of my submissions in a gallery format with annotations displayed. This is GREAT bec the hamburger allows for Add/delete annotations.

This researcher has been running into many multi-animal images where the annotation(s) need to be fixed. Unfortunately, because her focus right now is to run matching for all ID’d individuals, she’s only seeing the annotation issues when she’s on the match results page. And since it’s not possible to go to the proposed match encounter in a different window, when she goes to view and/or fix any annotation issues, she leaves the match results page. To get back to where she was with matching after sometimes a long process of adding and deleting annotations, is difficult and frustrating.

So she’d like to use this “Matching Images/Videos” page for “My submissions” to review all annotations and fix there, when/if needed BEFORE she starts any matching. She has found a large proportion of the multi-animal images of this species to have poorly placed annotations + missed annotations. So she now wants to be able to review and fix all annotations as her first step with a new dataset. There isn’t much point in doing that with her current census data but when we load the next census ('14-15), she’d like to proceed that way.

To that end, how accurately displayed are the annotations on this gallery page (“My Submissions” > “Matching Images/Video” tab)? Would it be recommended to always click through to the Add annotations view to see the most accurate reflection of the position of the annotation? If not, where is the most reliable view of the annotation placement?

thanks
Maureen

Hi Maureen,

The Encounter page and the Matching Images/Video pages use exactly the same code underneath, so they should be relatively identical representations of exactly where the annotations appear.

I can definitely see the bug you indicate with the manual annotation tool. While it is displaying the other annotations incorrectly, it should still allow correct mapping of a new annotation as a workaround while we fix this bug: WB-1392.

Thanks for reporting this.

-Jason

That’s all I needed to know. Thanks Jason!

Thanks! Adding this information to the ticket, and we’ve got the work to fix this in progress (not that that means anything timeline wise :sweat_smile: )

Tanya

Hello, @ACWadmin1 !

I believe that there are at least two separate issues here. One is with manualAnnotation.jsp.
The problem there was (at least) that the new height/old height =scale ratio was also being applied to width, when that should have been its own widthScale.

I believe that I have fixed that. The bounding boxes here:

resemble those here:

quite well now. Could I trouble you or the researcher to confirm that those are working better now?

As for:

“we have seen several instances where the annotation on the image in the encounter gallery is also skewed. It’s always where the image appears to be an irregular shape - either portrait-like or landscape. I just found another one so thought I’d pass the link and info along:
https://africancarnivore.wildbook.org/encounters/encounter.jsp?number=6881a092-66ec-49d0-8790-3ae7f538ed31

I’ve been unable to reproduce any “skew” here, and the bounding box around the cheetah here looks pretty accurate. The only thing that seems weird to me about this media asset is how far away the hamburger menu is from the bottom right-hand corner of the image.

Along those lines, that particular image is very small (smaller than the image sizes we recommend for media asset upload), so that is very likely why it’s giving you “wonky” vibes on the encounter page?

Am I understanding your second problem accurately here, or is there something I’m missing?

Thank you for working with us on this!
-Mark

@ACWadmin1 , can you review the above?

Hi, Maureen!
Thank you for providing the additional examples. I plan on looking at these on Thurs/Fri. of this week.

I’ll definitely report back when I find out more about the new examples.

-Mark

1 Like

Hi, Maureen!
This issue is being tracked internally as WB-1392 subtask WB-1518.
Thanks,
Mark

1 Like

Hi, Maureen!

Phew. I think it’s possible that I’ve finally fixed this issue, although it hasn’t yet gone through the whole code review and QA process. I ended up having to test some behavior on the production server, so the fixes are live on ACW currently. If you delete any old, problematic annotations on those wonkier images and re-draw manually, they should look better now. Can you confirm that this fixes the issues that you and your team were experiencing?

Incidentally, if you can find any examples of “portrait” style images that are still giving you trouble, I’d love to hear about those!

Thank you,
Mark

Hi, Maureen!
It’s possible that you guys were doing that right as I was in the process of troubleshooting, for which I apologize if that’s the case.
Could I ask you to try to reproduce that problem again currently?

And regarding the screenshot you sent above, one of those annotations represents me deleting and re-drawing an annotation, and the other has not yet been deleted and re-drawn. What happens when you delete and re-draw?

Thanks for continuing to work with me on this,
Mark

Re: It’s possible that you guys were doing that right as I was in the process of troubleshooting, for which I apologize if that’s the case.
→ What specifically are you referring to here? I’m not sure what you want me to recheck. Also, we didn’t work on this encounter record after we posted the issue.

Re: screenshot of double annotation. First, I can’t add a new annotation bec that functionality isn’t working properly per note above. Also, I’m not sure why we’re re-drawing, especially as a virtual duplicate of the problematically placed annotation? The issue was in where the annotation was displaying - what I reported was that it displayed properly after your first round of fixes, I believe, but then when the researcher ran matching, the annotations then displayed offset.

So are you asking me to do the following? Delete one (or both) of these 2 encounters with the smaller than required/duplicated annotation and then go back and add a new one and then run matching and see if the problem reproduces of offset annotations post matching recurs?

Sorry, I’m confused by your note.

Hi, Maureen!
I made a quick video that I hope answers all of your questions from above. Please let me know if it does not.

-Mark

@ACWadmin1 let me know if the above video satisfactorily answered any lingering questions.
Cheers,
Mark

Hi, Marueen!

Thank you for the response.
I’m afraid that I am to blame for both the duplicate manual annotation you’ve pointed out and the encounter missing a media asset, which I also suspect resulted from deleting a manual annotation.

Going forward, I will notify you and your team when I have to test things in the production server (it was too difficult to reproduce your cheetah image behavior in a test environment) with sufficient advance notice.

I had not realized that your team was not in the practice of removing manual annotations. Let me stew on the issue you’ve raised here and chat with the team members and see if I can help in any way. The way you describe it makes it seem like it’s currently an un-useable feature for you.

This coming Thursday/Friday (my main support days), are you comfortable if I chase down which of those two manual annotations on the bottom left of the image was “mine” and remove it? Alternatively, you’re welcome to delete both of the erroneous ones, as you mentioned.

I will also try to address the missing media asset issue.

In the spirit of resolving this together,
Mark