Updated Some MarkDown Files According to the Latest Release Version 1.4.0 of MMDetection3D #2922
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Update "submission_prefix" to "test_evaluator.submission_prefix". Update the waymo links, because the original link is 404.
Update the config file's name, because the actual name is changed but the instruction isn't updated
Because the initial args of `mmdetection3d/mmdet3d/evaluation/metrics/waymo_metric.py` have been updated, but this demo instruction is not updated
|
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
Make it easy to read for myself. And update some MarkDown files that some instructions are not suit to the latest MMDetection3D.
Modification
Some shell instructions and some super links that are 404.
BC-breaking (Optional)
Yes the modifications on instructions will break the back-compatibility of the downstream repos。
However, the breaking is not caused by these changes, rather, it stems from changes in the source codes.
Checklist
Yes