Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ap_array is empty #5

Closed
aries-young opened this issue May 26, 2022 · 7 comments
Closed

ap_array is empty #5

aries-young opened this issue May 26, 2022 · 7 comments

Comments

@aries-young
Copy link

aries-young commented May 26, 2022

I got this error during evaluating. I found sometimes ap_array was empty. Could you kind give some advice to adjust it?

  File "/Explore-and-Match/lib/evaluate/eval.py", line 75, in compute_ap
    iou_thd2ap = dict(zip([str(e) for e in iou_thds], ap_thds))
TypeError: 'numpy.float64' object is not iterable
@aries-young
Copy link
Author

aries-young commented Jun 6, 2022

Hello, as for this problem, do you have some solution for me to reproduce this work ?

@sangminwoo
Copy link
Owner

Since there is no error in my case, It seems that modification of the code is causing the issue.
Please take a look at the code you have modified!

And if you need further help, as the error message is too general, could you perhaps elaborate?

@aries-young
Copy link
Author

Since there is no error in my case, It seems that modification of the code is causing the issue. Please take a look at the code you have modified!

And if you need further help, as the error message is too general, could you perhaps elaborate?

Thank you so much. I'll check my code carefully. So sorry to bother you.

@sangminwoo
Copy link
Owner

No problem :)

@sunanhe
Copy link

sunanhe commented Jun 18, 2022

I had the same problem. I found that this is due to the fact that there are not moments in "Long" length.

https://github.com/sangminwoo/Explore-and-Match/blob/c07381affbad334e39793c4ca1563b45510e890e/lib/evaluate/eval.py#L135-L156

@aries-young
Copy link
Author

I had the same problem. I found that this is due to the fact that there are not moments in "Long" length.

https://github.com/sangminwoo/Explore-and-Match/blob/c07381affbad334e39793c4ca1563b45510e890e/lib/evaluate/eval.py#L135-L156

Have you solved this problem?

@sangminwoo
Copy link
Owner

If you do not need to specify the length of time segments, maybe you can consider removing all the "range-related" codes and just run!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants