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

NuScenes Evaluation #4

Closed
codyreading opened this issue Jun 28, 2021 · 3 comments
Closed

NuScenes Evaluation #4

codyreading opened this issue Jun 28, 2021 · 3 comments

Comments

@codyreading
Copy link

Hello and thanks for the release of this code!

I would like to evaluate the tracking results using the NuScenes evaluation. I noticed that this code currently only evaluates one sequence at a time, and produces a single JSON file for each sequence. Would you recommend I just evaluate all sequences and combine them in a single JSON file for evaluation?

@aleksandrkim61
Copy link
Owner

Hi, thanks for checking out our work!

The code outputs sequence-level evaluations for KITTI, but for NuScenes it produces only one final JSON file after processing the whole data split - you can trace the call of this function. The final result's format should be perfect for NuScenes Devkit evaluation. I am not aware of an easy way to do sequence-level evaluations.

When running on NuScenes script does produce .txt files for each sequence, but they are empty. This functionality is a by-product of KITTI-specific code that I wrote, which I did not remove because it was useful to see how far the run has gone without ssh-ing into the session :). I also attempted to use those .txt files to save progress for each sequence by it became too cumbersome.
Perhaps this led you to this confusion, but those files are completely empty, so you can remove them if you'd like.

@codyreading
Copy link
Author

Hello!

So currently the code only produces one JSON file for one sequence, I believe what was happening was due to the break here, which would exit the loop after processing a single sequence. I was able to remove this break and get the functionality that I needed.

Thanks for the help!

@aleksandrkim61
Copy link
Owner

Oops, I must have left it there after a recent test run.

Thanks for the flag! Fixed it and gave you a shoutout in the commit message :)

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

2 participants