Can you describe what the issue is youāre experiencing?
Iām noticing that the detection of multiple animals into separate encounters seems to have degraded. I did a batch of bulk imports recently and Iām finding that where there are multiple animals of the target species in a media asset, only 1 gets annotated.
Also, often, where thereās more than one animal in the media asset, Iām seeing the annotation placed around multiple individuals instead of just one.
Where thereās only 1 individual in the media asset, the detector is working GREAT - one dog, one tail.
But there are instances where I see only a tail annotated and no body and nothing else detected (see examples in sighting links above)
Iām seeing a high percentage of this in the sightings that Iām reviewing. Not sure if the most recent update, the tail to body assigner, has impacted detection???
Hi, thanks for sharing this bug. This does seem related to the new assigner, specifically the assigner in conjunction with the bulk uploader. We are investigating this now and will keep you updated.
Awesome, thanks Drew! Iāll keep reviewing the uploads and will let you know if I see anything else that doesnāt look right. So far, this is the only problem Iāve seen. Iāll try to run more matches too; havenāt done many of those yet.
Received, thank you. One last question for now: are you pressing the āsend to detection (no identification)ā or the āsend to identificationā button at the end of your bulk upload process?
I just also ran a match from 1 annotation in 1 encounter record and got this interesting result (link to results: Wildbook for Carnivores) - multiple duplicate encounter records; i.e. exact duplicate encounter IDs listed as distinct duplicate encounters, if that makes sense:
Iāve been making progress on this but am not done yet. The issue in your original comment should be resolved but I am still looking into those described in your second longer comment, so no need to do further testing until Iāve addressed that as well. Thanks for all the information and links, and you can expect another update tomorrow.
good morning @Drew. Thanks so much for figuring out and fixing the original issue. Thatās a huge relief!!! Regarding the 2nd issue, Iām wondering if it might be related to or similar to a problem @colin worked on before the holidays? - https://community.wildbook.org/t/missing-occurrence-id-in-encounter-records/438/12?u=acwadmin1
Because of that issue, Iāve been VERY careful about making sure Iām only running detection once for each import - I open each import task in a new window, click on the ādetection onlyā button then wait until I see it completed after a few minutes of refreshing the original list of imports. So I donāt believe this latest issue is caused by me accidentally running detection twice on a given batch, as Colin suggested would be the only way it could happen after he fixed the original issue.
So maybe not related to that earlier issue but I thought Iād mention it bec of the same symptom - many duplicate encounters being generated.
Thanks Maureen! That does sound super similar, whether itās just the same symptom or the same cause I am not sure. I did wonder if you had pressed the button twice, so itās good to hear thatās not the case. Iāll keep you updated as I deduplicate the data today, and hopefully prevent this from happening again.
These data issues should now be fixed and you should proceed with more using/testing of the platform! Keep your ear to the ground though, and Iāll keep this ticket open because thereās still one issue we donāt understand.
The only-one annotation-per-image issue in your original comment was, I believe, just an error in how we had rerun detection+assigner on your old images. Correct me if Iām wrong, but we never saw this specific issue on new data uploaded + detected after the assigner was added. Regardless, I cleaned that data and reran it through the assigner, and looking at your Sightings above I see the annotations and encounters weād expect. If you have old Import Tasks that are still corrupted in a unique rather than systematic way, consider if you can re-upload that data, as the compatibility between old imports and the new assigner isā¦ complicated. But let me know if you see widespread problems still unaddressed.
The second big issue, seeing duplicate annotations and duplicate encounters is the one thatās still a bit of a mystery. It is a nondeterministic issue, meaning I cannot replicate it myself by copying what you did, but I can see in the logs when the error(s) happened for you. The problem is that sometimes detection is called 2 or 3 times instead of just once when you send detection for a bulk import, though we donāt know why. This leads to 2 or 3 copies of all the annotations (and in the right scenarios, encounters) being created as a result. I have deleted these duplicates, and the links youāve shared are now clean. There were a total of 17 import tasks where this duplication had occurred. Let us know if you see it again.
So we will be monitoring this issue. Iāve built scripts to clean up these scenarios and can clean your data more quickly if we see either again. Meanwhile we are tracking the detection-duplications and will work on preventing those in the future.
Thank you SO much for your patience and detailed notes!
-Drew
@Drew - you just MADE MY WEEK!!! This is awesome. It seemed crazy complicated to me and I really didnāt expect a fix as quick as this. My lack of faith is NOT a reflection on you, just that technology sometimes hates me so I expect things like this to be weird and hard to resolve. Although Iām sure it wasnāt a cake walk.
Weāll keep our eyes peeled for any other signs of problems and keep you posted.
thank you again SO MUCH! And have a wonderful weekend.
