Skip to content

Tracking eval - Fix motmetrics version - #300

Merged
holger-motional merged 1 commit into
masterfrom
fix_motmetrics_version
Feb 18, 2020
Merged

holger-motional merged 1 commit into
masterfrom
fix_motmetrics_version

Conversation

@holger-motional

@holger-motional holger-motional commented Feb 18, 2020 •

Copy link
Copy Markdown
Contributor

Addresses #299. Major changes in the new motmetrics version 1.2.0 break our tracking eval code. To ensure that the results of our tracking challenge do not change, we fix the version number to be <= 1.1.3.

@tobiasfshr

Copy link
Copy Markdown

Will the code be updated to motmetrics 1.2.0?

@holger-motional

Copy link
Copy Markdown
Contributor Author

@tobiasfshr We don't intend to. Apparently motmetrics was completely rewritten and is not backward compatible. Is there a strong reason to switch to 1.2.0 ?

@tobiasfshr

Copy link
Copy Markdown

@holger-nutonomy In my case, I'm using a codebase that requires motmetrics 1.2.0, so i cannot run the nuscenes eval code inside of it. In general, the release log of v1.2.0 indicates that it would be way faster and, more importantly, they seem to have fixed a number of edge cases where the current evaluation results could be invalid. I'm not super similar with the repo though, so I can't say for sure if it makes a difference :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

3 participants