-
Notifications
You must be signed in to change notification settings - Fork 45
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
0 parents
commit 4822df5
Showing
136 changed files
with
17,231 additions
and
0 deletions.
There are no files selected for viewing
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,15 @@ | ||
**__pycache__** | ||
**build** | ||
**egg-info** | ||
**dist** | ||
data/ | ||
*.pyc | ||
venv/ | ||
*.idea/ | ||
*.so | ||
*.yaml | ||
*.sh | ||
*.pth | ||
*.pkl | ||
*.zip | ||
*.bin |
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,201 @@ | ||
Apache License | ||
Version 2.0, January 2004 | ||
http://www.apache.org/licenses/ | ||
|
||
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION | ||
|
||
1. Definitions. | ||
|
||
"License" shall mean the terms and conditions for use, reproduction, | ||
and distribution as defined by Sections 1 through 9 of this document. | ||
|
||
"Licensor" shall mean the copyright owner or entity authorized by | ||
the copyright owner that is granting the License. | ||
|
||
"Legal Entity" shall mean the union of the acting entity and all | ||
other entities that control, are controlled by, or are under common | ||
control with that entity. For the purposes of this definition, | ||
"control" means (i) the power, direct or indirect, to cause the | ||
direction or management of such entity, whether by contract or | ||
otherwise, or (ii) ownership of fifty percent (50%) or more of the | ||
outstanding shares, or (iii) beneficial ownership of such entity. | ||
|
||
"You" (or "Your") shall mean an individual or Legal Entity | ||
exercising permissions granted by this License. | ||
|
||
"Source" form shall mean the preferred form for making modifications, | ||
including but not limited to software source code, documentation | ||
source, and configuration files. | ||
|
||
"Object" form shall mean any form resulting from mechanical | ||
transformation or translation of a Source form, including but | ||
not limited to compiled object code, generated documentation, | ||
and conversions to other media types. | ||
|
||
"Work" shall mean the work of authorship, whether in Source or | ||
Object form, made available under the License, as indicated by a | ||
copyright notice that is included in or attached to the work | ||
(an example is provided in the Appendix below). | ||
|
||
"Derivative Works" shall mean any work, whether in Source or Object | ||
form, that is based on (or derived from) the Work and for which the | ||
editorial revisions, annotations, elaborations, or other modifications | ||
represent, as a whole, an original work of authorship. For the purposes | ||
of this License, Derivative Works shall not include works that remain | ||
separable from, or merely link (or bind by name) to the interfaces of, | ||
the Work and Derivative Works thereof. | ||
|
||
"Contribution" shall mean any work of authorship, including | ||
the original version of the Work and any modifications or additions | ||
to that Work or Derivative Works thereof, that is intentionally | ||
submitted to Licensor for inclusion in the Work by the copyright owner | ||
or by an individual or Legal Entity authorized to submit on behalf of | ||
the copyright owner. For the purposes of this definition, "submitted" | ||
means any form of electronic, verbal, or written communication sent | ||
to the Licensor or its representatives, including but not limited to | ||
communication on electronic mailing lists, source code control systems, | ||
and issue tracking systems that are managed by, or on behalf of, the | ||
Licensor for the purpose of discussing and improving the Work, but | ||
excluding communication that is conspicuously marked or otherwise | ||
designated in writing by the copyright owner as "Not a Contribution." | ||
|
||
"Contributor" shall mean Licensor and any individual or Legal Entity | ||
on behalf of whom a Contribution has been received by Licensor and | ||
subsequently incorporated within the Work. | ||
|
||
2. Grant of Copyright License. Subject to the terms and conditions of | ||
this License, each Contributor hereby grants to You a perpetual, | ||
worldwide, non-exclusive, no-charge, royalty-free, irrevocable | ||
copyright license to reproduce, prepare Derivative Works of, | ||
publicly display, publicly perform, sublicense, and distribute the | ||
Work and such Derivative Works in Source or Object form. | ||
|
||
3. Grant of Patent License. Subject to the terms and conditions of | ||
this License, each Contributor hereby grants to You a perpetual, | ||
worldwide, non-exclusive, no-charge, royalty-free, irrevocable | ||
(except as stated in this section) patent license to make, have made, | ||
use, offer to sell, sell, import, and otherwise transfer the Work, | ||
where such license applies only to those patent claims licensable | ||
by such Contributor that are necessarily infringed by their | ||
Contribution(s) alone or by combination of their Contribution(s) | ||
with the Work to which such Contribution(s) was submitted. If You | ||
institute patent litigation against any entity (including a | ||
cross-claim or counterclaim in a lawsuit) alleging that the Work | ||
or a Contribution incorporated within the Work constitutes direct | ||
or contributory patent infringement, then any patent licenses | ||
granted to You under this License for that Work shall terminate | ||
as of the date such litigation is filed. | ||
|
||
4. Redistribution. You may reproduce and distribute copies of the | ||
Work or Derivative Works thereof in any medium, with or without | ||
modifications, and in Source or Object form, provided that You | ||
meet the following conditions: | ||
|
||
(a) You must give any other recipients of the Work or | ||
Derivative Works a copy of this License; and | ||
|
||
(b) You must cause any modified files to carry prominent notices | ||
stating that You changed the files; and | ||
|
||
(c) You must retain, in the Source form of any Derivative Works | ||
that You distribute, all copyright, patent, trademark, and | ||
attribution notices from the Source form of the Work, | ||
excluding those notices that do not pertain to any part of | ||
the Derivative Works; and | ||
|
||
(d) If the Work includes a "NOTICE" text file as part of its | ||
distribution, then any Derivative Works that You distribute must | ||
include a readable copy of the attribution notices contained | ||
within such NOTICE file, excluding those notices that do not | ||
pertain to any part of the Derivative Works, in at least one | ||
of the following places: within a NOTICE text file distributed | ||
as part of the Derivative Works; within the Source form or | ||
documentation, if provided along with the Derivative Works; or, | ||
within a display generated by the Derivative Works, if and | ||
wherever such third-party notices normally appear. The contents | ||
of the NOTICE file are for informational purposes only and | ||
do not modify the License. You may add Your own attribution | ||
notices within Derivative Works that You distribute, alongside | ||
or as an addendum to the NOTICE text from the Work, provided | ||
that such additional attribution notices cannot be construed | ||
as modifying the License. | ||
|
||
You may add Your own copyright statement to Your modifications and | ||
may provide additional or different license terms and conditions | ||
for use, reproduction, or distribution of Your modifications, or | ||
for any such Derivative Works as a whole, provided Your use, | ||
reproduction, and distribution of the Work otherwise complies with | ||
the conditions stated in this License. | ||
|
||
5. Submission of Contributions. Unless You explicitly state otherwise, | ||
any Contribution intentionally submitted for inclusion in the Work | ||
by You to the Licensor shall be under the terms and conditions of | ||
this License, without any additional terms or conditions. | ||
Notwithstanding the above, nothing herein shall supersede or modify | ||
the terms of any separate license agreement you may have executed | ||
with Licensor regarding such Contributions. | ||
|
||
6. Trademarks. This License does not grant permission to use the trade | ||
names, trademarks, service marks, or product names of the Licensor, | ||
except as required for reasonable and customary use in describing the | ||
origin of the Work and reproducing the content of the NOTICE file. | ||
|
||
7. Disclaimer of Warranty. Unless required by applicable law or | ||
agreed to in writing, Licensor provides the Work (and each | ||
Contributor provides its Contributions) on an "AS IS" BASIS, | ||
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or | ||
implied, including, without limitation, any warranties or conditions | ||
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A | ||
PARTICULAR PURPOSE. You are solely responsible for determining the | ||
appropriateness of using or redistributing the Work and assume any | ||
risks associated with Your exercise of permissions under this License. | ||
|
||
8. Limitation of Liability. In no event and under no legal theory, | ||
whether in tort (including negligence), contract, or otherwise, | ||
unless required by applicable law (such as deliberate and grossly | ||
negligent acts) or agreed to in writing, shall any Contributor be | ||
liable to You for damages, including any direct, indirect, special, | ||
incidental, or consequential damages of any character arising as a | ||
result of this License or out of the use or inability to use the | ||
Work (including but not limited to damages for loss of goodwill, | ||
work stoppage, computer failure or malfunction, or any and all | ||
other commercial damages or losses), even if such Contributor | ||
has been advised of the possibility of such damages. | ||
|
||
9. Accepting Warranty or Additional Liability. While redistributing | ||
the Work or Derivative Works thereof, You may choose to offer, | ||
and charge a fee for, acceptance of support, warranty, indemnity, | ||
or other liability obligations and/or rights consistent with this | ||
License. However, in accepting such obligations, You may act only | ||
on Your own behalf and on Your sole responsibility, not on behalf | ||
of any other Contributor, and only if You agree to indemnify, | ||
defend, and hold each Contributor harmless for any liability | ||
incurred by, or claims asserted against, such Contributor by reason | ||
of your accepting any such warranty or additional liability. | ||
|
||
END OF TERMS AND CONDITIONS | ||
|
||
APPENDIX: How to apply the Apache License to your work. | ||
|
||
To apply the Apache License to your work, attach the following | ||
boilerplate notice, with the fields enclosed by brackets "[]" | ||
replaced with your own identifying information. (Don't include | ||
the brackets!) The text should be enclosed in the appropriate | ||
comment syntax for the file format. We also recommend that a | ||
file or class name and description of purpose be included on the | ||
same "printed page" as the copyright notice for easier | ||
identification within third-party archives. | ||
|
||
Copyright [yyyy] [name of copyright owner] | ||
|
||
Licensed under the Apache License, Version 2.0 (the "License"); | ||
you may not use this file except in compliance with the License. | ||
You may obtain a copy of the License at | ||
|
||
http://www.apache.org/licenses/LICENSE-2.0 | ||
|
||
Unless required by applicable law or agreed to in writing, software | ||
distributed under the License is distributed on an "AS IS" BASIS, | ||
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. | ||
See the License for the specific language governing permissions and | ||
limitations under the License. |
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,7 @@ | ||
# CenterPoint | ||
|
||
This repo is an reimplementation of CenterPoint on the KITTI dataset. For nuScenes and Waymo, please refer to the [original repo](https://github.com/tianweiy/CenterPoint). We provide two configs, [centerpoint.yaml](tools/cfgs/kitti_models/centerpoint.yaml) for the vanilla centerpoint model and [centerpoint_rcnn.yaml](tools/cfgs/kitti_models/centerpoint_rcnn.yaml) which combines centerpoint with PVRCNN. | ||
|
||
## Acknowledgement | ||
|
||
Our code is based on [OpenPCDet](https://github.com/open-mmlab/OpenPCDet). Some util files are copied from [mmdetection](https://github.com/open-mmlab/mmdetection) and [mmdetection3d](https://github.com/open-mmlab/mmdetection3d). Thanks OpenMMLab Development Team for their awesome codebases. |
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,48 @@ | ||
# Quick Demo | ||
|
||
Here we provide a quick demo to test a pretrained model on the custom point cloud data and visualize the predicted results. | ||
|
||
We suppose you already followed the [INSTALL.md](INSTALL.md) to install the `OpenPCDet` repo successfully. | ||
|
||
1. Download the provided pretrained models as shown in the [README.md](../README.md). | ||
|
||
2. Make sure you have already installed the `mayavi` visualization tools. If not, you could install it as follows: | ||
``` | ||
pip install mayavi | ||
``` | ||
|
||
3. Prepare you custom point cloud data (skip this step if you use the original KITTI data). | ||
* You need to transform the coordinate of your custom point cloud to | ||
the unified normative coordinate of `OpenPCDet`, that is, x-axis points towards to front direction, | ||
y-axis points towards to the left direction, and z-axis points towards to the top direction. | ||
* (Optional) the z-axis origin of your point cloud coordinate should be about 1.6m above the ground surface, | ||
since currently the provided models are trained on the KITTI dataset. | ||
* Set the intensity information, and save your transformed custom data to `numpy file`: | ||
```python | ||
# Transform your point cloud data | ||
... | ||
|
||
# Save it to the file. | ||
# The shape of points should be (num_points, 4), that is [x, y, z, intensity], | ||
# If you doesn't have the intensity information, just set them to zeros. | ||
# If you have the intensity information, you should normalize them to [0, 1]. | ||
points[:, 3] = 0 | ||
np.save(`my_data.npy`, points) | ||
``` | ||
|
||
4. Run the demo with a pretrained model (e.g. PV-RCNN) and your custom point cloud data as follows: | ||
```shell | ||
python demo.py --cfg_file cfgs/kitti_models/pv_rcnn.yaml \ | ||
--ckpt pv_rcnn_8369.pth \ | ||
--data_path ${POINT_CLOUD_DATA} | ||
``` | ||
Here `${POINT_CLOUD_DATA}` could be the following format: | ||
* Your transformed custom data with a single numpy file like `my_data.npy`. | ||
* Your transformed custom data with a directory to test with multiple point cloud data. | ||
* The original KITTI `.bin` data within `data/kitti`, like `data/kitti/training/velodyne/000008.bin`. | ||
|
||
Then you could see the predicted results with visualized point cloud as follows: | ||
|
||
<p align="center"> | ||
<img src="demo.png" width="99%"> | ||
</p> |
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,102 @@ | ||
# Getting Started | ||
The dataset configs are located within [tools/cfgs/dataset_configs](../tools/cfgs/dataset_configs), | ||
and the model configs are located within [tools/cfgs](../tools/cfgs) for different datasets. | ||
|
||
|
||
## Dataset Preparation | ||
|
||
Currently we provide the dataloader of KITTI dataset and NuScenes dataset, and the supporting of more datasets are on the way. | ||
|
||
### KITTI Dataset | ||
* Please download the official [KITTI 3D object detection](http://www.cvlibs.net/datasets/kitti/eval_object.php?obj_benchmark=3d) dataset and organize the downloaded files as follows (the road planes could be downloaded from [[road plane]](https://drive.google.com/file/d/1d5mq0RXRnvHPVeKx6Q612z0YRO1t2wAp/view?usp=sharing), which are optional for data augmentation in the training): | ||
* NOTE: if you already have the data infos from `pcdet v0.1`, you can choose to use the old infos and set the DATABASE_WITH_FAKELIDAR option in tools/cfgs/dataset_configs/kitti_dataset.yaml as True. The second choice is that you can create the infos and gt database again and leave the config unchanged. | ||
|
||
``` | ||
OpenPCDet | ||
├── data | ||
│ ├── kitti | ||
│ │ │── ImageSets | ||
│ │ │── training | ||
│ │ │ ├──calib & velodyne & label_2 & image_2 & (optional: planes) | ||
│ │ │── testing | ||
│ │ │ ├──calib & velodyne & image_2 | ||
├── pcdet | ||
├── tools | ||
``` | ||
|
||
* Generate the data infos by running the following command: | ||
```python | ||
python -m pcdet.datasets.kitti.kitti_dataset create_kitti_infos tools/cfgs/dataset_configs/kitti_dataset.yaml | ||
``` | ||
|
||
### NuScenes Dataset | ||
* Please download the official [NuScenes 3D object detection dataset](https://www.nuscenes.org/download) and | ||
organize the downloaded files as follows: | ||
``` | ||
OpenPCDet | ||
├── data | ||
│ ├── nuscenes | ||
│ │ │── v1.0-trainval (or v1.0-mini if you use mini) | ||
│ │ │ │── samples | ||
│ │ │ │── sweeps | ||
│ │ │ │── maps | ||
│ │ │ │── v1.0-trainval | ||
├── pcdet | ||
├── tools | ||
``` | ||
|
||
* Install the `nuscenes-devkit` with version `1.0.5` by running the following command: | ||
```shell script | ||
pip install nuscenes-devkit==1.0.5 | ||
``` | ||
|
||
* Generate the data infos by running the following command (it may take several hours): | ||
```python | ||
python -m pcdet.datasets.nuscenes.nuscenes_dataset --func create_nuscenes_infos \ | ||
--cfg_file tools/cfgs/dataset_configs/nuscenes_dataset.yaml \ | ||
--version v1.0-trainval | ||
``` | ||
|
||
## Training & Testing | ||
|
||
|
||
### Test and evaluate the pretrained models | ||
* Test with a pretrained model: | ||
```shell script | ||
python test.py --cfg_file ${CONFIG_FILE} --batch_size ${BATCH_SIZE} --ckpt ${CKPT} | ||
``` | ||
|
||
* To test all the saved checkpoints of a specific training setting and draw the performance curve on the Tensorboard, add the `--eval_all` argument: | ||
```shell script | ||
python test.py --cfg_file ${CONFIG_FILE} --batch_size ${BATCH_SIZE} --eval_all | ||
``` | ||
|
||
* To test with multiple GPUs: | ||
```shell script | ||
sh scripts/dist_test.sh ${NUM_GPUS} \ | ||
--cfg_file ${CONFIG_FILE} --batch_size ${BATCH_SIZE} | ||
|
||
# or | ||
|
||
sh scripts/slurm_test_mgpu.sh ${PARTITION} ${NUM_GPUS} \ | ||
--cfg_file ${CONFIG_FILE} --batch_size ${BATCH_SIZE} | ||
``` | ||
|
||
|
||
### Train a model | ||
You could optionally add extra command line parameters `--batch_size ${BATCH_SIZE}` and `--epochs ${EPOCHS}` to specify your preferred parameters. | ||
|
||
|
||
* Train with multiple GPUs or multiple machines | ||
```shell script | ||
sh scripts/dist_train.sh ${NUM_GPUS} --cfg_file ${CONFIG_FILE} | ||
|
||
# or | ||
|
||
sh scripts/slurm_train.sh ${PARTITION} ${JOB_NAME} ${NUM_GPUS} --cfg_file ${CONFIG_FILE} | ||
``` | ||
|
||
* Train with a single GPU: | ||
```shell script | ||
python train.py --cfg_file ${CONFIG_FILE} | ||
``` |
Oops, something went wrong.