-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
[Feature]Support NeRF-Det #2732
Conversation
Good |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We can pack the code for nerfdet into the projects directory.
configs/nerfdet/README.md
Outdated
<!-- [ALGORITHM] --> | ||
|
||
## Abstract | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should update readme.
Here is the training result of resnet50 and with depth information.
The mAP is lower than the testing result. |
@@ -678,6 +678,90 @@ def update_scannet_infos(pkl_path, out_dir): | |||
mmengine.dump(converted_data_info, out_path, 'pkl') | |||
|
|||
|
|||
def update_scannet_infos_nerfdet(pkl_path, out_dir): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Don't change this script out of projects
Thanks for your contribution and we appreciate it a lot. The following instructions would make your pull request more healthy and more easily get feedback. If you do not understand some items, don't worry, just make the pull request and seek help from maintainers.
Motivation
Support the MultiViewPipeline and ScanNetMultiViewDataset used in NeRF-Det
Modification
BC-breaking (Optional)
Does the modification introduce changes that break the back-compatibility of the downstream repos?
If so, please describe how it breaks the compatibility and how the downstream projects should modify their code to keep compatibility with this PR.
Use cases (Optional)
If this PR introduces a new feature, it is better to list some use cases here, and update the documentation.
Checklist