# The limitation of log

**URL:** <https://community.drivendata.org/t/the-limitation-of-log/8581>\
**Category:** Video Similarity Challenge\
**Created:** [February 3, 2023, 2:57pm UTC](https://community.drivendata.org/t/the-limitation-of-log/8581 "2023-02-03T14:57:57Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![wenhaowang](https://avatars.discourse-cdn.com/v4/letter/w/b2d939/32.png) [@wenhaowang](https://community.drivendata.org/u/wenhaowang)\
**Post date:** [February 3, 2023, 2:57pm UTC](https://community.drivendata.org/t/the-limitation-of-log/8581/1 "2023-02-03T14:57:58Z")

</div>

When I submit code, I find

```auto
< ... WARNING: logs capped at 1,000 lines; dropping 77 more >

```

Therefore, I cannot find what errors occur after 1,000 lines. Could you change the limitation from 1,000 to 10,000? Currently, I cannot figure out the bug. Thanks,

---

<div class="post-metadata">

**Author:** ![chrisk-dd](https://avatars.discourse-cdn.com/v4/letter/c/b5ac83/32.png) [@chrisk-dd](https://community.drivendata.org/u/chrisk-dd)\
**Post date:** [February 3, 2023, 4:07pm UTC](https://community.drivendata.org/t/the-limitation-of-log/8581/2 "2023-02-03T16:07:38Z")

</div>

@wenhaowang I’ve updated the limit, let me know if you hit the limit again and I can increase further!

---

<div class="post-metadata">

**Author:** ![wenhaowang](https://avatars.discourse-cdn.com/v4/letter/w/b2d939/32.png) [@wenhaowang](https://community.drivendata.org/u/wenhaowang)\
**Post date:** [February 3, 2023, 7:57pm UTC](https://community.drivendata.org/t/the-limitation-of-log/8581/3 "2023-02-03T19:57:00Z")

</div>

Great, many thanks to this

---

<div class="post-metadata">

**Author:** ![wenhaowang](https://avatars.discourse-cdn.com/v4/letter/w/b2d939/32.png) [@wenhaowang](https://community.drivendata.org/u/wenhaowang)\
**Post date:** [February 3, 2023, 10:12pm UTC](https://community.drivendata.org/t/the-limitation-of-log/8581/4 "2023-02-03T22:12:11Z")

</div>

It seems I have successfully run the code, but the muAP of the subset is about 0.06 (please refer to my latest submission). Is that normal? I am not sure whether this submission is valid for phase 2?

---

<div class="post-metadata">

**Author:** ![chrisk-dd](https://avatars.discourse-cdn.com/v4/letter/c/b5ac83/32.png) [@chrisk-dd](https://community.drivendata.org/u/chrisk-dd)\
**Post date:** [February 3, 2023, 11:46pm UTC](https://community.drivendata.org/t/the-limitation-of-log/8581/5 "2023-02-03T23:46:10Z")

</div>

I would expect them to be comparable if inference is running identically. One thing to check locally is whether, in your local container, the subset descriptors you generate (can be on any random subset) are identical to those you generate on the full query set. I will investigate whether there’s an issue on our end contributing to a score difference.

---

<div class="post-metadata">

**Author:** ![wenhaowang](https://avatars.discourse-cdn.com/v4/letter/w/b2d939/32.png) [@wenhaowang](https://community.drivendata.org/u/wenhaowang)\
**Post date:** [February 4, 2023, 12:06am UTC](https://community.drivendata.org/t/the-limitation-of-log/8581/6 "2023-02-04T00:06:20Z")

</div>

Thanks. In my local container, I find the descriptors of any subset are same (regardless of the sequence of video frame because in descriptor track time frames are generated randomly.) I think the difference in score may because whether you use the same ground truths for both full and subset. In this way, the muAP will be low for subset because there are only about 1/10 videos.

---

<div class="post-metadata">

**Author:** ![chrisk-dd](https://avatars.discourse-cdn.com/v4/letter/c/b5ac83/32.png) [@chrisk-dd](https://community.drivendata.org/u/chrisk-dd)\
**Post date:** [February 4, 2023, 12:08am UTC](https://community.drivendata.org/t/the-limitation-of-log/8581/7 "2023-02-04T00:08:46Z")

</div>

I believe we should be subsetting the ground truth to only the portion of the ground truth that contains videos relevant to the query subset, but it’s possible there’s an error in the processing there, that’s a good callout.

---

<div class="post-metadata">

**Author:** ![chrisk-dd](https://avatars.discourse-cdn.com/v4/letter/c/b5ac83/32.png) [@chrisk-dd](https://community.drivendata.org/u/chrisk-dd)\
**Post date:** [February 4, 2023, 12:14am UTC](https://community.drivendata.org/t/the-limitation-of-log/8581/8 "2023-02-04T00:14:38Z")

</div>

This was, in fact, the problem! The subset file on our platform was out-of-date and has now been corrected. On your next submission, I believe the uAP should be comparable.

Thank you again @wenhaowang for your help in identifying and debugging these issues! I’m very grateful to you for promptly calling them out and communicating frequently with us.

---

<div class="post-metadata">

**Author:** ![wenhaowang](https://avatars.discourse-cdn.com/v4/letter/w/b2d939/32.png) [@wenhaowang](https://community.drivendata.org/u/wenhaowang)\
**Post date:** [February 4, 2023, 12:37am UTC](https://community.drivendata.org/t/the-limitation-of-log/8581/9 "2023-02-04T00:37:23Z")

</div>

Thanks a lot about your effort

---

<div class="post-metadata">

**Author:** ![wenhaowang](https://avatars.discourse-cdn.com/v4/letter/w/b2d939/32.png) [@wenhaowang](https://community.drivendata.org/u/wenhaowang)\
**Post date:** [February 5, 2023, 1:57pm UTC](https://community.drivendata.org/t/the-limitation-of-log/8581/10 "2023-02-05T13:57:05Z")

</div>

Thanks, the scores are comparable now.
